References from draft-dhody-pce-pcep-extension-pce-controller-p2mp
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 |
---|---|---|---|---|
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 4857 |
Mobile IPv4 Regional Registration
References Referenced by |
Experimental | informatively references | |
RFC 4875 |
Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)
References Referenced by |
Proposed Standard | informatively references | |
RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 5671 |
Applicability of the Path Computation Element (PCE) to Point-to-Multipoint (P2MP) MPLS and GMPLS Traffic Engineering (TE)
References Referenced by |
Informational | informatively references | |
RFC 7025 |
Requirements for GMPLS Applications of PCE
References Referenced by |
Informational | informatively references | |
RFC 7399 |
Unanswered Questions in the Path Computation Element Architecture
References Referenced by |
Informational | informatively references | |
RFC 7420 |
Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) Module
References Referenced by |
Proposed Standard | informatively references | |
RFC 7491 |
A PCE-Based Architecture for Application-Based Network Operations
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 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 8283 |
An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control
References Referenced by |
Informational | informatively references | |
RFC 8306 |
Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
References Referenced by |
Proposed Standard | informatively references | |
RFC 8408 |
Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages
References Referenced by |
Proposed Standard | informatively references | |
RFC 8623 |
Stateful Path Computation Element (PCE) Protocol Extensions for Usage with Point-to-Multipoint TE Label Switched Paths (LSPs)
References Referenced by |
Proposed Standard | normatively references | |
RFC 9050 |
Path Computation Element Communication Protocol (PCEP) Procedures and Extensions for Using the PCE as a Central Controller (PCECC) of LSPs
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 | informatively references |