[Pce] RFC 9604 on Carrying Binding Label/SID in PCE-Based Networks

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

        RFC 9604

        Title:      Carrying Binding Label/SID in PCE-Based Networks 
        Author:     S. Sivabalan,
                    C. Filsfils,
                    J. Tantsura,
                    S. Previdi,
                    C. Li, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2024
        Mailbox:    msiva282@gmail.com,
                    cfilsfil@cisco.com,
                    jefftant.ietf@gmail.com,
                    stefano@previdi.net,
                    c.l@huawei.com
        Pages:      19
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-binding-label-sid-16.txt

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

        DOI:        10.17487/RFC9604

In order to provide greater scalability, network confidentiality, and
service independence, Segment Routing (SR) utilizes a Binding Segment
Identifier (BSID), as described in RFC 8402. It is possible to
associate a BSID to an RSVP-TE-signaled Traffic Engineering (TE)
Label Switched Path (LSP) or an SR TE path. The BSID can be used by
an upstream node for steering traffic into the appropriate TE path to
enforce SR policies. This document specifies the concept of binding
value, which can be either an MPLS label or a Segment Identifier
(SID). It further specifies an extension to Path Computation Element
Communication Protocol (PCEP) for reporting the binding value by a
Path Computation Client (PCC) to the Path Computation Element (PCE)
to support PCE-based TE policies.

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
Association Management Solutions, LLC