RFC 9256: Segment Routing Policy Architecture
In plain English — editorial summary, not part of the RFC
Segment Routing (SR) allows a node to steer a packet flow along any path. Intermediate per-path states are eliminated thanks to source routing. SR Policy is an ordered list of segments (i.e., instructions) that represent a source-routed policy. Packet flows are steered into an SR Policy on a node where it is instantiated called a headend node. The packets steered into an SR Policy carry an ordered list of segments associated with that SR Policy. This document updates RFC 8402 as it details the concepts of SR Policy and steering into an SR Policy.
Document record
- Document ID
- RFC9256
- Published
- July 2022
- Authors
- C. Filsfils; K. Talaulikar; D. Voyer; A. Bogdanov; P. Mattes
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 35
- Also known as
- —
- Updates:
- RFC 8402
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9857Advertisement of Segment Routing Policies Using BGP - Link StateCurrent
October 2025
- RFC 9513OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)Current
December 2023
- RFC 9514Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6)Current
December 2023
- RFC 8986Segment Routing over IPv6 (SRv6) Network ProgrammingCurrent
February 2021
- RFC 9801Private Line Emulation over Packet Switched NetworksCurrent
July 2025
- RFC 9860Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast RerouteCurrent
October 2025
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 9259Operations, Administration, and Maintenance (OAM) in Segment Routing over IPv6 (SRv6)Current
June 2022
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?