@misc{rfc9604,
    series =    {Request for Comments},
    number =    9604,
    howpublished =  {RFC 9604},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC9604},
    url =       {https://www.rfc-editor.org/info/rfc9604},
    author =    {Siva Sivabalan and Clarence Filsfils and Jeff Tantsura and Stefano Previdi and Cheng Li},
    title =     {{Carrying Binding Label/SID in PCE-Based Networks}},
    pagetotal = 19,
    year =      2024,
    month =     aug,
    abstract =  {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.},
}