References from draft-litkowski-pce-state-sync
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 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| BCP 195 |
Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) References Referenced by |
Best Current Practice | informatively references | |
| draft-knodel-terminology |
Terminology, Power, and Inclusive Language in Internet-Drafts and RFCs References Referenced by |
Informational | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| RFC 4655 |
A Path Computation Element (PCE)-Based Architecture References Referenced by |
Informational | informatively references | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP) References Referenced by |
Proposed Standard | normatively references | |
| RFC 6805 |
The Application of the Path Computation Element Architecture to the Determination of a Sequence of Domains in MPLS and GMPLS References Referenced by |
Informational | informatively references | |
| RFC 7399 |
Unanswered Questions in the Path Computation Element Architecture References Referenced by |
Informational | informatively references | |
| RFC 7525 |
Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) References Referenced by |
Best Current Practice | informatively references | |
| RFC 7752 |
North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP References Referenced by |
Proposed Standard | informatively references | |
| RFC 8051 |
Applicability of a Stateful Path Computation Element (PCE) References Referenced by |
Informational | 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 8232 |
Optimizations of Label Switched Path State Synchronization Procedures for a 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 | informatively references | |
| RFC 8751 |
Hierarchical Stateful Path Computation Element (PCE) References Referenced by |
Informational | informatively references | |
| RFC 8800 |
Path Computation Element Communication Protocol (PCEP) Extension for Label Switched Path (LSP) Diversity Constraint Signaling References Referenced by |
Proposed Standard | informatively references |