<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-multinexthop-attribute" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-multinexthop-attribute-03">
   <front>
      <title>BGP MultiNexthop Attribute</title>
      <author initials="K." surname="Vairavakkalai" fullname="Kaliraj Vairavakkalai">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <author initials="J. M." surname="Jeganathan" fullname="Jeyananth Minto Jeganathan">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <author initials="M." surname="Nanduri" fullname="Mohan Nanduri">
         <organization>Microsoft</organization>
      </author>
      <author initials="A. R." surname="Lingala" fullname="Avinash Reddy Lingala">
         <organization>AT&amp;T</organization>
      </author>
      <date month="September" day="21" year="2024" />
      <abstract>
	 <t>   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 &quot;MultiNexthop (MNH)&quot; 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.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-multinexthop-attribute-03" />
   
</reference>
