Skip to main content

References from RFC 9863

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-spring-sr-policy-yang YANG Data Model for Segment Routing Policy
References Referenced by
Proposed Standard informatively references
draft-ietf-teas-yang-te A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths, and Interfaces
References Referenced by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 3063 MPLS Loop Prevention Mechanism
References Referenced by
Experimental informatively references
RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels
References Referenced by
Proposed Standard informatively references
RFC 3630 Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by
Proposed Standard informatively references
RFC 5305 IS-IS Extensions for Traffic Engineering
References Referenced by
Proposed Standard informatively references
RFC 5329 Traffic Engineering Extensions to OSPF Version 3
References Referenced by
Proposed Standard informatively references
RFC 5440 Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by
Proposed Standard normatively references
RFC 5886 A Set of Monitoring Tools for Path Computation Element (PCE)-Based Architecture
References Referenced by
Proposed Standard informatively references
RFC 6123 Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group Drafts
References Referenced by
Historic informatively references
RFC 7308 Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)
References Referenced by
Proposed Standard 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 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 8408 Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages
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 8745 Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCE
References Referenced by
Proposed Standard normatively references
RFC 9012 The BGP Tunnel Encapsulation Attribute
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
RFC 9862 Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths
References Referenced by
Proposed Standard normatively references