%% You should probably cite draft-li-ldr-bgp-request-cp-sr-te-policy-07 instead of this revision.
@techreport{li-ldr-bgp-request-cp-sr-te-policy-00,
    number =    {draft-li-ldr-bgp-request-cp-sr-te-policy-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-li-ldr-bgp-request-cp-sr-te-policy/00/},
    author =    {Zhenbin Li and Lei Li},
    title =     {{BGP Request for Advertising Candidate Path of Segment Routing TE Policies}},
    pagetotal = 13,
    year =      2019,
    month =     jul,
    day =       8,
    abstract =  {An SR Policy is a set of candidate paths. The headend of an SR Policy may learn multiple candidate paths for an SR Policy via a number of different mechanisms, e.g., CLI, NetConf, PCEP, or BGP. BGP distribute candidate paths has been defined in {[}I-D.ietf-idr-segment-routing-te-policy{]}. This document defines an extension of BGP to request BGP speaker(controller) advertise the candidate paths. The goal is to unify the protocol when the candidate path of SR Policy provision is via BGP to reduce the network complexity and potential bugs cause by different protocol interactions.},
}