%% You should probably cite draft-ietf-idr-next-next-hop-nodes instead of this I-D.
@techreport{wang-idr-next-next-hop-nodes-00,
    number =    {draft-wang-idr-next-next-hop-nodes-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-wang-idr-next-next-hop-nodes/00/},
    author =    {Kevin Wang and Jeffrey Haas},
    title =     {{BGP Next-next Hop Nodes}},
    pagetotal = 7,
    year =      2023,
    month =     dec,
    day =       15,
    abstract =  {BGP speakers learn their next hop addresse for NLRI in {[}RFC4271{]} in the NEXT\_HOP field and in {[}RFC4760{]} 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. {[}I-D.ietf-idr-entropy-label{]} defines the "Next Hop Dependent Capabilities Attribute" (NHC) which allows a BGP speaker to signal the forwarding capabilities associated with a given next hop. This document defines a new NHC capability, the Next-next Hop Nodes (NNHN) capability, which can be used to advertise the next-next hop nodes associated with a given next hop.},
}