<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.kaliraj-idr-multinexthop-attribute" target="https://datatracker.ietf.org/doc/html/draft-kaliraj-idr-multinexthop-attribute-09">
   <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>
      <date month="July" day="23" year="2023" />
      <abstract>
	 <t>   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 &quot;MultiNexthop (MNH)&quot; 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.


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