References from RFC 8356
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 100 |
References Referenced by |
informatively references | ||
| BCP 26 |
References Referenced by |
normatively references | ||
| BCP 82 |
References Referenced by |
normatively references | ||
| RFC 3692 |
Assigning Experimental and Testing Numbers Considered Useful
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6709 |
Design Considerations for Protocol Extensions
References Referenced by |
Informational | informatively references | |
| RFC 7120 |
Early IANA Allocation of Standards Track Code Points
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 | normatively references | |
| RFC 8231 |
Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8281 |
Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model
References Referenced by |
Proposed Standard | normatively references |