[Pce] RFC 9862 on Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate Paths

A new Request for Comments is now available in online RFC libraries.

        RFC 9862

        Title:      Path Computation Element Communication Protocol 
                    (PCEP) Extensions for Segment Routing (SR) 
                    Policy Candidate Paths 
        Author:     M. Koldychev,
                    S. Sivabalan,
                    S. Sidor,
                    C. Barth,
                    S. Peng,
                    H. Bidgoli
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2025
        Mailbox:    mkoldych@proton.me,
                    ssivabal@ciena.com,
                    ssidor@cisco.com,
                    cbarth@juniper.net,
                    pengshuping@huawei.com,
                    hooman.bidgoli@nokia.com
        Pages:      26
        Updates:    RFC 8231

        I-D Tag:    draft-ietf-pce-segment-routing-policy-cp-27.txt

        URL:        https://www.rfc-editor.org/info/rfc9862

        DOI:        10.17487/RFC9862

A Segment Routing (SR) Policy is an ordered list of instructions
called "segments" that represent a source-routed policy. Packet flows
are steered into an SR Policy on a node where it is instantiated.  An
SR Policy is made of one or more Candidate Paths. 

This document specifies the Path Computation Element Communication
Protocol (PCEP) extension to signal Candidate Paths of an SR Policy. 
Additionally, this document updates RFC 8231 to allow delegation and
setup of an SR Label Switched Path (LSP) without using the path
computation request and reply messages.  This document is applicable
to both Segment Routing over MPLS (SR-MPLS) and Segment Routing over
IPv6 (SRv6).

This document is a product of the Path Computation Element Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team