References from draft-zhao-pce-pcep-extension-pce-controller-sr

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.

Reference type help

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 normatively references
BCP 205 Improving Awareness of Running Code: The Implementation Status Section
References Referenced by
Best Current Practice normatively references
BCP 26 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
draft-dhodylee-pce-pcep-ls PCEP extensions for Distribution of Link-State and TE Information
References Referenced by
informatively references
draft-ietf-pce-binding-label-sid Carrying Binding Label/Segment-ID in PCE-based Networks.
References Referenced by
informatively references
draft-ietf-pce-pcep-extension-for-pce-controller PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of LSPs
References Referenced by
normatively references
draft-ietf-pce-pcep-yang A YANG Data Model for Path Computation Element Communications Protocol (PCEP)
References Referenced by
informatively references
draft-ietf-teas-pcecc-use-cases The Use Cases for Path Computation Element (PCE) as a Central Controller (PCECC).
References Referenced by
informatively references
draft-litkowski-pce-state-sync Inter Stateful Path Computation Element (PCE) Communication Procedures.
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 3031 Multiprotocol Label Switching Architecture
References Referenced by
Proposed Standard informatively references
RFC 3630 Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by
Proposed Standard normatively references
RFC 4203 OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
References Referenced by
Proposed Standard normatively references
RFC 4655 A Path Computation Element (PCE)-Based Architecture
References Referenced by
Informational informatively references
RFC 4915 Multi-Topology (MT) Routing in OSPF
References Referenced by
Proposed Standard normatively references
RFC 5305 IS-IS Extensions for Traffic Engineering
References Referenced by
Proposed Standard normatively references
RFC 5307 IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
References Referenced by
Proposed Standard normatively references
RFC 5440 Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by
Proposed Standard normatively 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 normatively references
RFC 7491 A PCE-Based Architecture for Application-Based Network Operations
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 normatively references
RFC 7752 North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
References Referenced by
Proposed Standard normatively references
RFC 7942 Improving Awareness of Running Code: The Implementation Status Section
References Referenced by
Best Current Practice normatively 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 8232 Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCE
References Referenced by
Proposed Standard informatively 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 8402 Segment Routing Architecture
References Referenced by
Proposed Standard informatively references
RFC 8408 Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages
References Referenced by
Proposed Standard normatively references
RFC 8660 Segment Routing with the MPLS Data Plane
References Referenced by
Proposed Standard informatively references
RFC 8664 Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing
References Referenced by
Proposed Standard normatively references
RFC 8665 OSPF Extensions for Segment Routing
References Referenced by
Proposed Standard informatively references
RFC 8667 IS-IS Extensions for Segment Routing
References Referenced by
Proposed Standard informatively references