%% You should probably cite draft-ietf-idr-bgp-sr-segtypes-ext or draft-ietf-idr-sr-policy-safi instead of this I-D.
@techreport{ietf-idr-segment-routing-te-policy-19,
    number =    {draft-ietf-idr-segment-routing-te-policy-19},
    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-idr-segment-routing-te-policy/19/},
    author =    {Stefano Previdi and Clarence Filsfils and Ketan Talaulikar and Paul Mattes and Dhanendra Jain and Steven Lin},
    title =     {{Advertising Segment Routing Policies in BGP}},
    pagetotal = 50,
    year =      2022,
    month =     jul,
    day =       24,
    abstract =  {This document introduces a BGP SAFI with two NLRIs to advertise a candidate path of a Segment Routing (SR) Policy. An SR Policy is an ordered list of segments (i.e., instructions) that represent a source-routed policy. An SR Policy consists of one or more candidate paths, each consisting of one or more segment lists. A headend may be provisioned with candidate paths for an SR Policy via several different mechanisms, e.g., CLI, NETCONF, PCEP, or BGP. This document specifies how BGP may be used to distribute SR Policy candidate paths. It defines sub-TLVs for the Tunnel Encapsulation Attribute for signaling information about these candidate paths. This documents updates RFC9012 with extensions to the Color Extended Community to support additional steering modes over SR Policy.},
}