References from draft-ietf-pce-association-diversity
This is an experimental product. 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 | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively references | |
| draft-dhody-pce-stateful-pce-optional |
Extension for Stateful PCE to allow Optional Processing of PCEP Objects References Referenced by |
informatively references | ||
| draft-ietf-pce-association-group |
Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs) References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-pce-pcep-yang |
A YANG Data Model for Path Computation Element Communications Protocol (PCEP) 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 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 5541 |
Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP) References Referenced by |
Proposed Standard | normatively references | |
| RFC 6007 |
Use of the Synchronization VECtor (SVEC) List for Synchronized Dependent Path Computations References Referenced by |
Informational | informatively references | |
| RFC 7470 |
Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol References Referenced by |
Proposed Standard | normatively 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 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively 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 | informatively references |