RFC 9256
Segment Routing Policy Architecture, July 2022
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 8402
- Authors:
- C. Filsfils
K. Talaulikar, Ed.
D. Voyer
A. Bogdanov
P. Mattes - Stream:
- IETF
- Source:
- spring (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9256
Discuss this RFC: Send questions or comments to the mailing list spring@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9256
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.