%% You should probably cite draft-ietf-pce-binding-label-sid-16 instead of this revision.
@techreport{ietf-pce-binding-label-sid-00,
    number =    {draft-ietf-pce-binding-label-sid-00},
    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/00/},
    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 = 16,
    year =      ,
    month =     ,
    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.},
}