<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sivabalan-pce-binding-label-sid" target="https://datatracker.ietf.org/doc/html/draft-sivabalan-pce-binding-label-sid-05">
   <front>
      <title>Carrying Binding Label/Segment-ID in PCE-based Networks.</title>
      <author initials="S." surname="Sivabalan" fullname="Siva Sivabalan">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Apstra, Inc.</organization>
      </author>
      <author initials="J." surname="Hardwick" fullname="Jonathan Hardwick">
         <organization>Metaswitch Networks</organization>
      </author>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="D." surname="Dhody" fullname="Dhruv Dhody">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="October" day="19" year="2018" />
      <abstract>
	 <t>   In order to provide greater scalability, network opacity, and service
   independence, SR utilizes a Binding Segment Identifier (BSID).  It is
   possible to associate a BSID to RSVP-TE signaled Traffic Engineering
   Label Switching Path or binding Segment-ID (SID) to Segment Routed
   (SR) Traffic Engineering path.  Such a binding label/SID can be used
   by an upstream node for steering traffic into the appropriate TE path
   to enforce SR policies.  This document proposes an approach for
   reporting binding label/SID to Path Computation Element (PCE) for
   supporting PCE-based Traffic Engineering policies.


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