BGP Remote-Next-Hop
draft-vandevelde-idr-remote-next-hop-04
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Gunter Van de Velde , Keyur Patel , Dhananjaya Rao , Robert Raszuk , Randy Bush | ||
Last updated | 2014-01-16 (Latest revision 2013-07-15) | ||
Replaced by | draft-ietf-idr-tunnel-encaps, RFC 9012 | ||
RFC stream | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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
The BGP Remote-Next-Hop is a new optional transitive attribute intended to facilitate automatic tunneling across an AS on a per address family basis. The attribute carries one or more tunnel end- points for a NLRI. Additionally, tunnel encapsulation information is communicated to successfully setup these tunnels.
Authors
Gunter Van de Velde
Keyur Patel
Dhananjaya Rao
Robert Raszuk
Randy Bush
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)