Skip to main content

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

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-mpls-bfd-directed Bidirectional Forwarding Detection (BFD) Directed Return Path for MPLS Label Switched Paths (LSPs)
References Referenced by
Experimental informatively references
draft-ietf-pce-multipath PCEP Extensions for Signaling Multipath Information
References Referenced by
informatively references
draft-ietf-pce-pcep-stateful-pce-gmpls Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE Usage in GMPLS-Controlled Networks
References Referenced by
Proposed Standard informatively 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-sr-path-segment Path Computation Element Communication Protocol (PCEP) Extension for Path Segment in Segment Routing (SR)
References Referenced by
informatively references
draft-ietf-spring-mpls-path-segment Path Segment Identifier in MPLS Based Segment Routing Network
References Referenced by
Proposed Standard informatively references
draft-ietf-spring-srv6-path-segment Path Segment for SRv6 (Segment Routing in IPv6)
References Referenced by
informatively references
draft-ietf-spring-stamp-srpm Performance Measurement Using Simple Two-Way Active Measurement Protocol (STAMP) for Segment Routing Networks
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 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
RFC 8408 Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages
References Referenced by
Proposed Standard informatively references
RFC 8697 Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)
References Referenced by
Proposed Standard normatively references
RFC 9059 Path Computation Element Communication Protocol (PCEP) Extensions for Associated Bidirectional Label Switched Paths (LSPs)
References Referenced by
Proposed Standard normatively references
RFC 9256 Segment Routing Policy Architecture
References Referenced by
Proposed Standard informatively references