References from draft-ymbk-lsvr-lsoe

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
draft-ietf-idr-bgp-ls-segment-routing-ext	BGP Link-State extensions for Segment Routing Refs Ref'd by	Proposed Standard	normatively references
draft-ietf-idr-bgpls-segment-routing-epe	BGP-LS extensions for Segment Routing BGP Egress Peer Engineering Refs Ref'd by	Proposed Standard	normatively references
draft-ietf-lsvr-bgp-spf	Shortest Path Routing Extensions for BGP Protocol Refs Ref'd by		normatively references
RFC 1982	Serial Number Arithmetic Refs Ref'd by	Proposed Standard	normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
RFC 3032	MPLS Label Stack Encoding Refs Ref'd by	Proposed Standard	normatively references
RFC 4271	A Border Gateway Protocol 4 (BGP-4) Refs Ref'd by	Draft Standard	normatively references
RFC 5226	Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by	Best Current Practice	normatively references
RFC 5880	Bidirectional Forwarding Detection (BFD) Refs Ref'd by	Proposed Standard	normatively references
RFC 6286	Autonomous-System-Wide Unique BGP Identifier for BGP-4 Refs Ref'd by	Proposed Standard	normatively references
RFC 7752	North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP Refs Ref'd by	Proposed Standard	normatively references
RFC 8174	Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by	Best Current Practice	normatively references