RFC 8402: Segment Routing Architecture
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. A segment can have a semantic local to an SR node or global within an SR domain. SR provides a mechanism that allows a flow to be restricted to a specific topological path, while maintaining per-flow state only at the ingress node(s) to the SR domain. SR can be directly applied to the MPLS architecture with no change to the forwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as a stack of labels. The segment to process is on the top of the stack. Upon completion of a segment, the related label is popped from the stack. SR can be applied to the IPv6 architecture, with a new type of routing header. A segment is encoded as an IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses in the routing header. The active segment is indicated by the Destination Address (DA) of the packet. The next active segment is indicated by a pointer in the new routing header.
Document record
- Document ID
- RFC8402
- Published
- July 2018
- Authors
- C. Filsfils; S. Previdi; L. Ginsberg; B. Decraene; S. Litkowski; R. Shakir
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
- Updated by:
- RFC 9256
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8401Bit Index Explicit Replication (BIER) Support via IS-ISUpdated
June 2018
- RFC 8403A Scalable and Topology-Aware MPLS Data-Plane Monitoring SystemCurrent
July 2018
- RFC 8400Extensions to RSVP-TE for Label Switched Path (LSP) Egress ProtectionCurrent
June 2018
- RFC 8405Shortest Path First (SPF) Back-Off Delay Algorithm for Link-State IGPsCurrent
June 2018
- RFC 8397Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique NicknamesCurrent
May 2018
- RFC 8408Conveying Path Setup Type in PCE Communication Protocol (PCEP) MessagesUpdated
July 2018
- RFC 8395Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport LabelsCurrent
June 2018
- RFC 8394Split Network Virtualization Edge (Split-NVE) Control-Plane RequirementsCurrent
May 2018
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?