%% You should probably cite draft-ietf-pce-binding-label-sid instead of this I-D. @techreport{sivabalan-pce-binding-label-sid-06, number = {draft-sivabalan-pce-binding-label-sid-06}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-sivabalan-pce-binding-label-sid/06/}, author = {Siva Sivabalan and Clarence Filsfils and Jeff Tantsura and Jonathan Hardwick and Stefano Previdi and Cheng Li}, title = {{Carrying Binding Label/Segment-ID in PCE-based Networks.}}, pagetotal = 13, year = ** No value found for 'doc.pub_date.year' **, month = ** No value found for 'doc.pub_date' **, day = ** No value found for 'doc.pub_date.day' **, abstract = {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.}, }