%% You should probably cite draft-ietf-idr-multinexthop-attribute instead of this I-D.
@techreport{kaliraj-idr-multinexthop-attribute-11,
    number =    {draft-kaliraj-idr-multinexthop-attribute-11},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kaliraj-idr-multinexthop-attribute/11/},
    author =    {Kaliraj Vairavakkalai and Jeyananth Minto Jeganathan and Mohan Nanduri and Avinash Reddy Lingala},
    title =     {{BGP MultiNexthop Attribute}},
    pagetotal = 52,
    year =      2023,
    month =     nov,
    day =       18,
    abstract =  {Today, a BGP speaker can advertise one nexthop for a set of NLRIs in an Update. This nexthop can be encoded in either the top-level BGP- Nexthop attribute (code 3), or inside the MP\_REACH\_NLRI attribute (code 14). This document defines a new optional non-transitive BGP attribute called "MultiNexthop (MNH)" with IANA BGP attribute type code TBD, that can be used to carry an ordered set of one or more Nexthops in the same route, with forwaring information scoped on a per nexthop basis.},
}