Segment Routing Prefix Segment Identifier Extensions for BGP
RFC 8669, “Segment Routing Prefix Segment Identifier Extensions for BGP”, is a Proposed Standard document published in December 2019 by S. Previdi, C. Filsfils, A. Lindem, A. Sreekantiah, H. Gredler. The canonical text is published by the RFC Editor.
Abstract
Segment Routing (SR) leverages the source-routing paradigm. A node steers a packet through an ordered list of instructions called "segments". A segment can represent any instruction, topological or service based. The ingress node prepends an SR header to a packet containing a set of segment identifiers (SIDs). Each SID represents a topological or service-based instruction. Per-flow state is maintained only on the ingress node of the SR domain. An "SR domain" is defined as a single administrative domain for global SID assignment.
This document defines an optional, transitive BGP attribute for announcing information about BGP Prefix Segment Identifiers (BGP Prefix-SIDs) and the specification for SR-MPLS SIDs.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8669 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8668 Advertising Layer 2 Bundle Member Link Attributes in IS-IS
- RFC 8670 BGP Prefix Segment in Large-Scale Data Centers
- RFC 8667 IS-IS Extensions for Segment Routing
- RFC 8671 Support for Adj-RIB-Out in the BGP Monitoring Protocol
- RFC 8666 OSPFv3 Extensions for Segment Routing
- RFC 8672 TLS Server Identity Pinning with Tickets
- RFC 8665 OSPF Extensions for Segment Routing
- RFC 8673 HTTP Random Access and Live Content