References from draft-li-pce-sr-bidir-path

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.

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 205 Improving Awareness of Running Code: The Implementation Status Section
References Referenced by
Best Current Practice informatively references
draft-ietf-mpls-bfd-directed Bidirectional Forwarding Detection (BFD) Directed Return Path
References Referenced by
Proposed Standard informatively references
draft-ietf-pce-association-bidir PCEP Extensions for Associated Bidirectional Label Switched Paths (LSPs)
References Referenced by
normatively 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-stateful-pce-gmpls Path Computation Element (PCE) Protocol Extensions for Stateful PCE Usage in GMPLS-controlled Networks
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-pce-segment-routing Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing
References Referenced by
Proposed Standard informatively references
draft-ietf-spring-mpls-path-segment Path Segment in MPLS Based Segment Routing Network
References Referenced by
informatively references
draft-li-pce-sr-path-segment Path Computation Element Communication Protocol (PCEP) Extension for Path Segment in Segment Routing (SR)
References Referenced by
normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 4657 Path Computation Element (PCE) Communication Protocol Generic Requirements
References Referenced by
Informational informatively references
RFC 5440 Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by
Proposed Standard normatively references
RFC 7420 Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) Module
References Referenced by
Proposed Standard informatively references
RFC 7942 Improving Awareness of Running Code: The Implementation Status Section
References Referenced by
Best Current Practice 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 informatively 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 8402 Segment Routing Architecture
References Referenced by
Proposed Standard informatively references