%% You should probably cite draft-ietf-pce-binding-label-sid-16 instead of this revision. @techreport{ietf-pce-binding-label-sid-09, number = {draft-ietf-pce-binding-label-sid-09}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-pce-binding-label-sid/09/}, author = {Siva Sivabalan and Clarence Filsfils and Jeff Tantsura and Stefano Previdi and Cheng Li}, title = {{Carrying Binding Label/Segment Identifier in PCE-based Networks.}}, pagetotal = 21, 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 confidentiality, and service independence, Segment Routing (SR) utilizes a Binding Segment Identifier (BSID). It is possible to associate a BSID to an RSVP-TE- signaled Traffic Engineering Label Switched Path or an SR Traffic Engineering 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 binding value as an MPLS label or Segment Identifier. It further specify an approach for reporting binding label/SID by a Path Computation Client (PCC) to the Path Computation Element (PCE) to support PCE-based Traffic Engineering policies.}, }