[Idr] I-D Action: draft-ietf-idr-multinexthop-attribute-00.txt

internet-drafts@ietf.org Sun, 17 March 2024 05:29 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: idr@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: idr@ietf.org
Message-ID: <171065337866.30156.13615885700404916165@ietfa.amsl.com>
Date: Sat, 16 Mar 2024 22:29:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/P4ITwmPIPx_GzMjUDMUPV3_v6h8>
Subject: [Idr] I-D Action: draft-ietf-idr-multinexthop-attribute-00.txt

Internet-Draft draft-ietf-idr-multinexthop-attribute-00.txt is now available.
It is a work item of the Inter-Domain Routing (IDR) WG of the IETF.

   Title:   BGP MultiNexthop Attribute
   Authors: Kaliraj Vairavakkalai
            Minto Jeyananth
            Mohan Nanduri
            Avinash Reddy
   Name:    draft-ietf-idr-multinexthop-attribute-00.txt
   Pages:   52
   Dates:   2024-03-16

Abstract:

   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 "MultiNexthop (MNH)" 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.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-multinexthop-attribute/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-multinexthop-attribute-00

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

[Idr] I-D Action: draft-ietf-idr-multinexthop-att… internet-drafts