Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

S. Previdi
C. Filsfils
A. Lindem, Ed.
A. Sreekantiah
H. Gredler

Stream:

IETF

Source:

idr (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8669

Discuss this RFC: Send questions or comments to the mailing listidr@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8669

Abstract

Segment Routing (SR) leverages the source-routing paradigm. A nodesteers a packet through an ordered list of instructions called"segments". A segment can represent any instruction, topological orservice based. The ingress node prepends an SR header to a packetcontaining a set of segment identifiers (SIDs). Each SID represents atopological or service-based instruction. Per-flow state ismaintained only on the ingress node of the SR domain. An "SR domain"is defined as a single administrative domain for global SIDassignment.

This document defines an optional, transitive BGP attribute forannouncing information about BGP Prefix Segment Identifiers (BGPPrefix-SIDs) and the specification for SR-MPLS SIDs.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.