Segment Routing Policy Architecture
RFC 9256, “Segment Routing Policy Architecture”, is a Proposed Standard document published in July 2022 by C. Filsfils, K. Talaulikar, D. Voyer, A. Bogdanov, P. Mattes. It updates RFC 8402. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9256 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9255 The 'I' in RPKI Does Not Stand for Identity
- RFC 9257 Guidance for External Pre-Shared Key Usage in TLS
- RFC 9254 Encoding of Data Modeled with YANG in the Concise Binary Object Representation
- RFC 9258 Importing External Pre-Shared Keys for TLS 1.3
- RFC 9253 Support for iCalendar Relationships
- RFC 9259 Operations, Administration, and Maintenance in Segment Routing over IPv6
- RFC 9252 BGP Overlay Services Based on Segment Routing over IPv6
- RFC 9260 Stream Control Transmission Protocol