%% You should probably cite draft-ietf-idr-elc or draft-ietf-idr-nhc instead of this I-D.
@techreport{ietf-idr-entropy-label-13,
    number =    {draft-ietf-idr-entropy-label-13},
    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-entropy-label/13/},
    author =    {Bruno Decraene and John Scudder and Wim Henderickx and Kireeti Kompella and SATYA R MOHANTY and Jim Uttaro and Bin Wen},
    title =     {{BGP Next Hop Dependent Capabilities Attribute}},
    pagetotal = 17,
    year =      2023,
    month =     oct,
    day =       9,
    abstract =  {RFC 5492 allows a BGP speaker to advertise its capabilities to its peer. When a route is propagated beyond the immediate peer, it is useful to allow certain capabilities to be conveyed further. In particular, it is useful to advertise forwarding plane features. This specification defines a BGP transitive attribute to carry such capability information, the "Next Hop Dependent Capabilities Attribute," or NHC. Unlike the capabilities defined by RFC 5492, those conveyed in the NHC apply solely to the routes advertised by the BGP UPDATE that contains the particular NHC. This specification also defines an NHC capability that can be used to advertise the ability to process the MPLS Entropy Label as an egress LSR for all NLRI advertised in the BGP UPDATE. It updates RFC 6790 and RFC 7447 concerning this BGP signaling.},
}