%% You should probably cite rfc9830 instead of this I-D.
@techreport{ietf-idr-sr-policy-safi-11,
    number =    {draft-ietf-idr-sr-policy-safi-11},
    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-sr-policy-safi/11/},
    author =    {Stefano Previdi and Clarence Filsfils and Ketan Talaulikar and Paul Mattes and Dhanendra Jain},
    title =     {{Advertising Segment Routing Policies in BGP}},
    pagetotal = 41,
    year =      2025,
    month =     jan,
    day =       31,
    abstract =  {A Segment Routing (SR) Policy is an ordered list of segments (also referred to as instructions) that define a source-routed policy. An SR Policy consists of one or more candidate paths, each comprising one or more segment lists. A headend can be provisioned with these candidate paths using various mechanisms, such as CLI, NETCONF, PCEP, or BGP. This document specifies how BGP can be used to distribute SR Policy candidate paths. It introduces a BGP SAFI for advertising a candidate path of an SR Policy and defines sub-TLVs for the Tunnel Encapsulation Attribute to signal information related to these candidate paths. Furthermore, this document updates RFC9012 by extending the Color Extended Community to support additional steering modes over SR Policy.},
}