References from draft-ietf-idr-segment-routing-te-policy
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.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
draft-ietf-idr-bgp-model |
YANG Model for Border Gateway Protocol (BGP-4)
References Referenced by |
Proposed Standard | Possible Reference | |
draft-ietf-idr-bgp-sr-segtypes-ext |
Segment Routing Segment Types Extensions for BGP SR Policy
References Referenced by |
Experimental | Possible Reference | Possible Downref |
draft-ietf-spring-sr-policy-yang |
YANG Data Model for Segment Routing Policy
References Referenced by |
Possible Reference | Possible Downref | |
RFC 1997 |
BGP Communities Attribute
References Referenced by |
Proposed Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2545 |
Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
References Referenced by |
Proposed Standard | normatively references | |
RFC 3032 |
MPLS Label Stack Encoding
References Referenced by |
Proposed Standard | normatively references | |
RFC 4271 |
A Border Gateway Protocol 4 (BGP-4)
References Referenced by |
Draft Standard | normatively references | |
RFC 4272 |
BGP Security Vulnerabilities Analysis
References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 4360 |
BGP Extended Communities Attribute
References Referenced by |
Proposed Standard | normatively references | |
RFC 4456 |
BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
References Referenced by |
Draft Standard | Possible Reference | |
RFC 4760 |
Multiprotocol Extensions for BGP-4
References Referenced by |
Draft Standard | normatively references | |
RFC 5462 |
Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
References Referenced by |
Proposed Standard | normatively references | |
RFC 6952 |
Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide
References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 7606 |
Revised Error Handling for BGP UPDATE Messages
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 8402 |
Segment Routing Architecture
References Referenced by |
Proposed Standard | normatively references | |
RFC 8660 |
Segment Routing with the MPLS Data Plane
References Referenced by |
Proposed Standard | normatively references | |
RFC 8754 |
IPv6 Segment Routing Header (SRH)
References Referenced by |
Proposed Standard | normatively 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 9256 |
Segment Routing Policy Architecture
References Referenced by |
Proposed Standard | normatively references |