metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8669: Segment Routing Prefix Segment Identifier Extensions for BGP

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8669
Published
December 2019
Authors
S. Previdi; C. Filsfils; A. Lindem; A. Sreekantiah; H. Gredler
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
15
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8669-segment-routing-prefix-segment-identifier-extensions-for-bgp