%% You should probably cite draft-ietf-idr-entropy-label-14 instead of this revision.
@techreport{ietf-idr-entropy-label-01,
    number =    {draft-ietf-idr-entropy-label-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-ietf-idr-entropy-label/01/},
    author =    {Bruno Decraene and John Scudder and Wim Henderickx and Kireeti Kompella and Satya Mohanty and Jim Uttaro and Bin Wen},
    title =     {{BGP Router Capabilities Attribute}},
    pagetotal = 13,
    year =      2022,
    month =     oct,
    day =       10,
    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 may be useful to advertise forwarding plane features. This specification defines a new BGP transitive attribute to carry such capability information, the "Router Capabilities Attribute," or RCA. This specification also defines an RCA 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.},
}