Using the BGP Tunnel Encapsulation Attribute without the BGP Encapsulation SAFI
draft-rosen-idr-tunnel-encaps-03

Document Type Replaced Internet-Draft (idr WG)
Last updated 2015-10-14 (latest revision 2015-08-06)
Replaced by draft-ietf-idr-tunnel-encaps
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-idr-tunnel-encaps
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rosen-idr-tunnel-encaps-03.txt

Abstract

RFC 5512 defines a BGP Path Attribute known as the "Tunnel Encapsulation Attribute". This attribute allows one to specify a set of tunnels. For each such tunnel, the attribute can provide additional information used to create a tunnel and the corresponding encapsulation header, and can also provide information that aids in choosing whether a particular packet is to be sent through a particular tunnel. RFC 5512 states that the attribute is only carried in BGP UPDATEs that have the "Encapsulation Subsequent Address Family (Encapsulation SAFI)". This document updates RFC 5512 by deprecating the Encapsulation SAFI (which has never been used),and by specifying semantics for the attribute when it is carried in UPDATEs of certain other SAFIs. This document also extends the attribute by enabling it to carry additional information needed to create the encapsulation headers additional tunnel types not mentioned in RFC 5512. Finally, this document also extends the attribute by allowing it to specify a remote tunnel endpoint address for each tunnel.

Authors

Eric Rosen (erosen@juniper.net)
Keyur Patel (keyupate@cisco.com)
Gunter Van de Velde (gunter.van_de_velde@alcatel-lucent.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)