<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-next-next-hop-nodes" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-next-next-hop-nodes-01">
   <front>
      <title>BGP Next-next Hop Nodes</title>
      <author initials="K." surname="Wang" fullname="Kevin Wang">
         <organization>HPE</organization>
      </author>
      <author initials="J." surname="Haas" fullname="Jeff Haas">
         <organization>HPE</organization>
      </author>
      <author initials="C." surname="Lin" fullname="Changwang Lin">
         <organization>New H3C Technologies</organization>
      </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Nvidia</organization>
      </author>
      <date month="May" day="26" year="2026" />
      <abstract>
	 <t>   BGP speakers learn their next hop addresses for NLRI in RFC 4271 in
   the NEXT_HOP field and in RFC 4760 in the &quot;Network Address of Next
   Hop&quot; 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 &quot;Next Hop Dependent Characteristics
   Attribute&quot; (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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-next-next-hop-nodes-01" />
   
</reference>
