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

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
BCP 14	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
BCP 195	Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Refs Ref'd by	Best Current Practice	normatively references
BCP 205	Improving Awareness of Running Code: The Implementation Status Section Refs Ref'd by	Best Current Practice	informatively references
BCP 26	Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by	Best Current Practice	normatively references
draft-ietf-pce-pcep-extension-for-pce-controller	PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of LSPs Refs Ref'd by		normatively references
draft-ietf-pce-pcep-yang	A YANG Data Model for Path Computation Element Communications Protocol (PCEP) Refs Ref'd by		informatively references
draft-ietf-pce-segment-routing	PCEP Extensions for Segment Routing Refs Ref'd by	Proposed Standard	normatively references
draft-ietf-pce-segment-routing-ipv6	PCEP Extensions for Segment Routing leveraging the IPv6 data plane Refs Ref'd by		normatively references
draft-ietf-spring-mpls-path-segment	Path Segment in MPLS Based Segment Routing Network Refs Ref'd by		informatively references
draft-li-pce-controlled-id-space	PCE Controlled ID Space Refs Ref'd by		informatively references
draft-li-spring-srv6-path-segment	Path Segment for SRv6 (Segment Routing in IPv6) Refs Ref'd by		normatively references
draft-zhao-pce-pcep-extension-pce-controller-sr	PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of SR-LSPs Refs Ref'd by		normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
RFC 4655	A Path Computation Element (PCE)-Based Architecture Refs Ref'd by	Informational	informatively references
RFC 4657	Path Computation Element (PCE) Communication Protocol Generic Requirements Refs Ref'd by	Informational	informatively references
RFC 5440	Path Computation Element (PCE) Communication Protocol (PCEP) Refs Ref'd by	Proposed Standard	normatively references
RFC 7525	Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Refs Ref'd by	Best Current Practice	normatively references
RFC 7942	Improving Awareness of Running Code: The Implementation Status Section Refs Ref'd by	Best Current Practice	informatively references
RFC 8126	Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by	Best Current Practice	normatively references
RFC 8174	Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by	Best Current Practice	normatively references
RFC 8231	Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE Refs Ref'd by	Proposed Standard	normatively references
RFC 8232	Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCE Refs Ref'd by	Proposed Standard	normatively references
RFC 8253	PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP) Refs Ref'd by	Proposed Standard	normatively references
RFC 8281	Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model Refs Ref'd by	Proposed Standard	normatively references
RFC 8402	Segment Routing Architecture Refs Ref'd by	Proposed Standard	informatively references