BGP MultiNexthop Attribute
draft-kaliraj-idr-multinexthop-attribute-11
Document | Type |
Replaced Internet-Draft
(idr WG)
Expired & archived
|
|
---|---|---|---|
Authors | Kaliraj Vairavakkalai , Jeyananth Minto Jeganathan , Mohan Nanduri , Avinash Reddy Lingala | ||
Last updated | 2024-02-16 (Latest revision 2023-11-18) | ||
Replaced by | draft-ietf-idr-multinexthop-attribute | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-idr-multinexthop-attribute | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Kaliraj Vairavakkalai
Jeyananth Minto Jeganathan
Mohan Nanduri
Avinash Reddy Lingala
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)