<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sidor-pce-binding-label-sid-extensions" target="https://datatracker.ietf.org/doc/html/draft-sidor-pce-binding-label-sid-extensions-02">
   <front>
      <title>Binding Label/Segment Identifier (SID) Extensions in Path Computation Element Communication Protocol (PCEP)</title>
      <author initials="S." surname="Sidor" fullname="Samuel Sidor">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="Z." surname="Ali" fullname="Zafar Ali">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="C." surname="Li" fullname="Cheng Li">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="M." surname="Koldychev" fullname="Mike Koldychev">
         <organization>Ciena Corporation</organization>
      </author>
      <date month="April" day="10" year="2026" />
      <abstract>
	 <t>   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to instantiate and
   manage Label Switched Paths (LSPs) on a Path Computation Client
   (PCC).  This includes the ability for a PCE to specify a Binding
   Segment Identifier (SID) for an LSP.

   A binding value specified by a PCE may not be available for use on
   the PCC.  This can lead to LSP instantiation failures or entire PCEP
   message being rejected.

   This document proposes extensions to PCEP to allow a PCC to fall back
   to allocating a Binding SID from its own dynamic range if the value
   specified by the PCE is unavailable.  It also defines a mechanism for
   the PCC to report both the requested and the allocated binding values
   back to the PCE.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-sidor-pce-binding-label-sid-extensions-02" />
   
</reference>
