%% You should probably cite draft-ietf-lsr-rfc8919bis instead of this I-D.
@techreport{ginsberg-lsr-rfc8919bis-01,
    number =    {draft-ginsberg-lsr-rfc8919bis-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ginsberg-lsr-rfc8919bis/01/},
    author =    {Les Ginsberg and Peter Psenak and Stefano Previdi and Wim Henderickx and John Drake},
    title =     {{IS-IS Application-Specific Link Attributes}},
    pagetotal = 25,
    year =      2022,
    month =     jun,
    day =       21,
    abstract =  {Existing traffic-engineering-related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case was defined, additional applications (e.g., Segment Routing Policy and Loop-Free Alternates) that also make use of the link attribute advertisements have been defined. In cases where multiple applications wish to make use of these link attributes, the current advertisements do not support application- specific values for a given attribute, nor do they support indication of which applications are using the advertised value for a given link. This document introduces new link attribute advertisements that address both of these shortcomings. This document obsoletes RFC 8919.},
}