Path Computation Element Communication Protocol Extensions for IPv6 Segment Routing
RFC 9603, “Path Computation Element Communication Protocol Extensions for IPv6 Segment Routing”, is a Proposed Standard document published in July 2024 by C. Li, P. Kaladharan, S. Sivabalan, M. Koldychev, Y. Zhu. It has since been updated by RFC 9756. The canonical text is published by the RFC Editor.
Abstract
Segment Routing (SR) can be used to steer packets through a network using the IPv6 or MPLS data plane, employing the source routing paradigm.
An SR Path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), explicit configuration, or a Path Computation Element (PCE).
Since SR can be applied to both MPLS and IPv6 data planes, a PCE should be able to compute an SR Path for both MPLS and IPv6 data planes. The Path Computation Element Communication Protocol (PCEP) extension and mechanisms to support SR-MPLS have been defined. This document outlines the necessary extensions to support SR for the IPv6 data plane within PCEP.
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 9603 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9602 Segment Routing over IPv6 Segment Identifiers in the IPv6 Addressing Architecture
- RFC 9604 Carrying Binding Label/SID in PCE-Based Networks
- RFC 9601 Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim
- RFC 9605 Secure Frame : Lightweight Authenticated Encryption for Real-Time Media
- RFC 9600 TRansparent Interconnection of Lots of Links : Explicit Congestion Notification Support
- RFC 9606 DNS Resolver Information
- RFC 9599 Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
- RFC 9607 RTP Payload Format for the Secure Communication Interoperability Protocol Codec