Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

References from RFC 9256

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
draft-ali-spring-sr-traffic-accounting	Traffic Accounting in Segment Routing Networks References Referenced by		informatively references
draft-anand-spring-poi-sr	Packet-Optical Integration in Segment Routing References Referenced by		informatively references
draft-filsfils-spring-sr-policy-considerations	SR Policy Implementation and Deployment Considerations References Referenced by		informatively references
draft-filsfils-spring-sr-traffic-counters	Segment Routing Traffic Accounting Counters References Referenced by		informatively references
draft-ietf-idr-segment-routing-te-policy	Advertising Segment Routing Policies in BGP References Referenced by	Proposed Standard	informatively references
draft-ietf-idr-te-lsp-distribution	Distribution of Traffic Engineering (TE) Policies and State using BGP-LS References Referenced by	Proposed Standard	informatively references
draft-ietf-lsr-flex-algo	IGP Flexible Algorithm References Referenced by	Proposed Standard	informatively references
draft-ietf-pce-binding-label-sid	Carrying Binding Label/Segment Identifier (SID) in PCE-based Networks. References Referenced by	Proposed Standard	informatively references
draft-ietf-pce-segment-routing-policy-cp	Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths References Referenced by	Proposed Standard	informatively references
draft-ietf-rtgwg-segment-routing-ti-lfa	Topology Independent Fast Reroute using Segment Routing References Referenced by	Proposed Standard	informatively references
draft-ietf-spring-sr-policy-yang	YANG Data Model for Segment Routing Policy References Referenced by	Proposed Standard	informatively references
RFC 1195	Use of OSI IS-IS for routing in TCP/IP and dual environments References Referenced by	Proposed Standard	informatively references
RFC 20	ASCII format for network interchange References Referenced by	Internet Standard	informatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
RFC 2328	OSPF Version 2 References Referenced by	Internet Standard	informatively references
RFC 3630	Traffic Engineering (TE) Extensions to OSPF Version 2 References Referenced by	Proposed Standard	informatively references
RFC 4760	Multiprotocol Extensions for BGP-4 References Referenced by	Draft Standard	informatively references
RFC 5305	IS-IS Extensions for Traffic Engineering References Referenced by	Proposed Standard	informatively references
RFC 5307	IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) References Referenced by	Proposed Standard	informatively references
RFC 5329	Traffic Engineering Extensions to OSPF Version 3 References Referenced by	Proposed Standard	informatively references
RFC 5340	OSPF for IPv6 References Referenced by	Proposed Standard	informatively references
RFC 5462	Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field References Referenced by	Proposed Standard	informatively references
RFC 6830	The Locator/ID Separation Protocol (LISP) References Referenced by	Experimental	informatively references
RFC 7471	OSPF Traffic Engineering (TE) Metric Extensions References Referenced by	Proposed Standard	informatively references
RFC 7752	North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP References Referenced by	Proposed Standard	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	informatively references
RFC 8402	Segment Routing Architecture References Referenced by	Proposed Standard	normatively references
RFC 8476	Signaling Maximum SID Depth (MSD) Using OSPF References Referenced by	Proposed Standard	informatively references
RFC 8491	Signaling Maximum SID Depth (MSD) Using IS-IS References Referenced by	Proposed Standard	informatively references
RFC 8570	IS-IS Traffic Engineering (TE) Metric Extensions References Referenced by	Proposed Standard	informatively references
RFC 8660	Segment Routing with the MPLS Data Plane References Referenced by	Proposed Standard	normatively references
RFC 8664	Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing References Referenced by	Proposed Standard	informatively references
RFC 8754	IPv6 Segment Routing Header (SRH) References Referenced by	Proposed Standard	normatively references
RFC 8814	Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link State References Referenced by	Proposed Standard	informatively references
RFC 8986	Segment Routing over IPv6 (SRv6) Network Programming References Referenced by	Proposed Standard	normatively references
RFC 9012	The BGP Tunnel Encapsulation Attribute References Referenced by	Proposed Standard	normatively references
RFC 9086	Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing BGP Egress Peer Engineering References Referenced by	Proposed Standard	informatively references