<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-tunnel-encaps" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-tunnel-encaps-00">
   <front>
      <title>Using the BGP Tunnel Encapsulation Attribute without the BGP Encapsulation SAFI</title>
      <author initials="E. C." surname="Rosen" fullname="Eric C. Rosen">
         </author>
      <author initials="K." surname="Patel" fullname="Keyur Patel">
         </author>
      <author initials="G." surname="Van de Velde" fullname="Gunter Van de Velde">
         </author>
      <date month="August" day="19" year="2015" />
      <abstract>
	 <t>   RFC 5512 defines a BGP Path Attribute known as the &quot;Tunnel
   Encapsulation Attribute&quot;.  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 &quot;Encapsulation Subsequent
   Address Family (Encapsulation SAFI)&quot;.  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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-tunnel-encaps-00" />
   
</reference>
