BGP Remote-Next-Hop
draft-vandevelde-idr-remote-next-hop-04
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (individual) | |
| Last updated | 2014-01-16 (latest revision 2013-07-15) | ||
| Replaced by | draft-ietf-idr-tunnel-encaps | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-vandevelde-idr-remote-next-hop-04.txt
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
(gvandeve@cisco.com)
Keyur Patel
(keyupate@cisco.com)
Dhananjaya Rao
(dhrao@cisco.com)
Robert Raszuk
(robert@raszuk.net)
Randy Bush
(randy@psg.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)