%% You should probably cite draft-ietf-idr-multinexthop-attribute-04 instead of this revision.
@techreport{ietf-idr-multinexthop-attribute-03,
    number =    {draft-ietf-idr-multinexthop-attribute-03},
    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-multinexthop-attribute/03/},
    author =    {Kaliraj Vairavakkalai and Jeyananth Minto Jeganathan and Mohan Nanduri and Avinash Reddy Lingala},
    title =     {{BGP MultiNexthop Attribute}},
    pagetotal = 56,
    year =      2024,
    month =     sep,
    day =       22,
    abstract =  {Today, a BGP speaker can advertise one nexthop for a set of NLRIs in an Update message. This nexthop can be encoded in either the top- level BGP-Nexthop attribute (code 3), or inside the MP\_REACH\_NLRI attribute (code 14). Forwarding information related to the nexthop is scattered across various attributes, extended communities or the NLRI field. This document defines a new optional non-transitive BGP attribute called "MultiNexthop (MNH)" with IANA code TBD. The MNH provides two things: it allows carrying the Nexthop and related forwarding information in one BGP attribute. The MNH also enables carrying an ordered set of multiple Nexthops in the same attribute, with forwarding information scoped on a per Nexthop basis.},
}