Skip to main content

References from draft-ietf-pce-binding-label-sid

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
draft-ietf-pce-pcep-yang A YANG Data Model for Path Computation Element Communications Protocol (PCEP)
References Referenced by
informatively references
draft-ietf-pce-segment-routing-ipv6 Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing leveraging the IPv6 dataplane
References Referenced by
Proposed Standard normatively references
draft-ietf-pce-sr-path-segment Path Computation Element Communication Protocol (PCEP) Extension for Path Segment in Segment Routing (SR)
References Referenced by
informatively references
draft-li-pce-controlled-id-space Path Computation Element Communication Protocol (PCEP) extension to advertise the PCE Controlled Identifier Space
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 3032 MPLS Label Stack Encoding
References Referenced by
Proposed Standard 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 5462 Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
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 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 normatively references
RFC 8664 Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing
References Referenced by
Proposed Standard normatively references
RFC 8754 IPv6 Segment Routing Header (SRH)
References Referenced by
Proposed Standard informatively references
RFC 8986 Segment Routing over IPv6 (SRv6) Network Programming
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 9256 Segment Routing Policy Architecture
References Referenced by
Proposed Standard informatively 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