%% You should probably cite rfc9085 instead of this I-D.
@techreport{ietf-idr-bgp-ls-segment-routing-ext-18,
    number =    {draft-ietf-idr-bgp-ls-segment-routing-ext-18},
    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-bgp-ls-segment-routing-ext/18/},
    author =    {Stefano Previdi and Ketan Talaulikar and Clarence Filsfils and Hannes Gredler and Mach Chen},
    title =     {{Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing}},
    pagetotal = 27,
    year =      2021,
    month =     apr,
    day =       15,
    abstract =  {Segment Routing (SR) allows for a flexible definition of end-to-end paths by encoding paths as sequences of topological subpaths, called "segments". These segments are advertised by routing protocols, e.g., by the link-state routing protocols (IS-IS, OSPFv2, and OSPFv3) within IGP topologies. This document defines extensions to the Border Gateway Protocol - Link State (BGP-LS) address family in order to carry SR information via BGP.},
}