References from draft-beeram-pce-pcep-mpted
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 195 | References Referenced by | normatively references | ||
| draft-kompella-teas-mpte | Multipath Traffic Engineering References Referenced by | normatively references | ||
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels 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 6123 | Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group Drafts References Referenced by | Historic | informatively references | |
| RFC 8174 | Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words 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 8253 | PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP) 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 | |
| RFC 9325 | Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) References Referenced by | Best Current Practice | normatively references |