Skip to main content

The BGP Tunnel Encapsulation Attribute

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 9012.
Expired & archived
Authors Eric C. Rosen , Keyur Patel , Gunter Van de Velde
Last updated 2019-02-21 (Latest revision 2018-08-20)
Replaces draft-rosen-idr-tunnel-encaps, draft-vandevelde-idr-remote-next-hop
RFC stream Internet Engineering Task Force (IETF)
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd John Scudder
IESG IESG state Expired
Consensus boilerplate Yes
Telechat date (None)
Responsible AD (None)
Send notices to John Scudder <>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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 the information needed to create the tunnel and the corresponding encapsulation header. The attribute 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 deprecates the Encapsulation SAFI (which has never been used in production), and specifies semantics for the attribute when it is carried in UPDATEs of certain other SAFIs. This document adds support for additional tunnel types, and allows a remote tunnel endpoint address to be specified for each tunnel. This document also provides support for specifying fields of any inner or outer encapsulations that may be used by a particular tunnel. This document obsoletes RFC 5512.


Eric C. Rosen
Keyur Patel
Gunter Van de Velde

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