@techreport{ietf-idr-next-next-hop-nodes-01,
    number =    {draft-ietf-idr-next-next-hop-nodes-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-next-next-hop-nodes/01/},
    author =    {Kevin Wang and Jeff Haas and Changwang Lin and Jeff Tantsura},
    title =     {{BGP Next-next Hop Nodes}},
    pagetotal = 8,
    year =      2026,
    month =     may,
    day =       26,
    abstract =  {BGP speakers learn their next hop addresses for NLRI in RFC 4271 in the NEXT\_HOP field and in RFC 4760 in the "Network Address of Next Hop" field. Under certain circumstances, it might be desirable for a BGP speaker to know both the next hops and the next-next hops of NLRI to make optimal forwarding decisions. One such example is global load balancing (GLB) in a Clos network. Draft-ietf-idr-nhc defines the "Next Hop Dependent Characteristics Attribute" (NHC) which allows a BGP speaker to signal the forwarding characteristics associated with a given next hop. This document defines a new NHC characteristic, the Next-next Hop Nodes (NNHN) characteristic, which can be used to advertise the next- next hop nodes associated with a given next hop.},
}