References from RFC 8281
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
References Referenced by |
normatively references | ||
| BCP 205 |
References Referenced by |
informatively references | ||
| BCP 26 |
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4657 |
Path Computation Element (PCE) Communication Protocol Generic Requirements
References Referenced by |
Informational | informatively references | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5511 |
Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7942 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Best Current Practice | informatively references | |
| RFC 8051 |
Applicability of a Stateful Path Computation Element (PCE)
References Referenced by |
Informational | informatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
| RFC 8231 |
Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8232 |
Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCE
References Referenced by |
Proposed Standard | normatively references |