RFC 9933: Carrying SR-Algorithm in Path Computation Element Communication Protocol (PCEP)
In plain English — editorial summary, not part of the RFC
This document specifies extensions to the Path Computation Element Communication Protocol (PCEP) to enhance support for Segment Routing (SR) with a focus on the use of Segment Identifiers (SIDs) and SR-Algorithms in Traffic Engineering (TE). The SR-Algorithm associated with a SID defines the path computation algorithm used by Interior Gateway Protocols (IGPs). It introduces mechanisms for PCEP peers to signal the SR-Algorithm associated with SIDs by encoding this information in Explicit Route Object (ERO) and Record Route Object (RRO) subobjects, enables SR-Algorithm constraints for path computation, and defines new metric types for the METRIC object. This document updates RFC 8664 and RFC 9603 to allow such extensions.
Document record
- Document ID
- RFC9933
- Published
- July 2026
- Authors
- S. Sidor; Z. Rose; S. Peng; S. Peng; A. Stone
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9929IGP Unreachable Prefix AnnouncementCurrent
February 2026
- RFC 9938A Framework for the Deterministic Networking (DetNet) Controller PlaneCurrent
March 2026
- RFC 9917IGP Flexible Algorithms Reverse Affinity ConstraintCurrent
January 2026
- RFC 9916Updates to the Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)Current
July 2026
- RFC 9914Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
April 2026
- RFC 9913Reliable and Available Wireless (RAW) TechnologiesCurrent
April 2026
- RFC 9912Reliable and Available Wireless (RAW) ArchitectureCurrent
April 2026
- RFC 9960Segment Routing Point-to-Multipoint PolicyCurrent
April 2026
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?