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 list idr@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 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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.