Skip to main content

References from draft-szarecki-idr-bgp-lcu-traffic-steering

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
BCP 14
References Referenced by
normatively references
draft-ietf-idr-bgp-prefix-sid Segment Routing Prefix Segment Identifier Extensions for BGP
References Referenced by
Proposed Standard normatively references
draft-ietf-idr-tunnel-encaps The BGP Tunnel Encapsulation Attribute
References Referenced by
Proposed Standard normatively references
draft-ietf-lsr-flex-algo IGP Flexible Algorithm
References Referenced by
Proposed Standard informatively references
draft-ietf-mpls-seamless-mpls Seamless MPLS Architecture
References Referenced by
Informational informatively references
draft-ietf-spring-segment-routing-policy Segment Routing Policy Architecture
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 2475 An Architecture for Differentiated Services
References Referenced by
Informational informatively 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 4760 Multiprotocol Extensions for BGP-4
References Referenced by
Draft Standard normatively references
RFC 5549 Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
References Referenced by
Proposed Standard normatively references
RFC 5575 Dissemination of Flow Specification Rules
References Referenced by
Proposed Standard informatively references
RFC 7606 Revised Error Handling for BGP UPDATE Messages
References Referenced by
Proposed Standard informatively references
RFC 7811 An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)
References Referenced by
Proposed Standard informatively references
RFC 7911 Advertisement of Multiple Paths in BGP
References Referenced by
Proposed Standard informatively references
RFC 8277 Using BGP to Bind MPLS Labels to Address Prefixes
References Referenced by
Proposed Standard normatively references
RFC 8402 Segment Routing Architecture
References Referenced by
Proposed Standard normatively references