[Idr] I-D Action: draft-ietf-idr-tunnel-encaps-18.txt

internet-drafts@ietf.org Fri, 11 September 2020 15:23 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: idr@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: idr@ietf.org
Message-ID: <159983781158.14049.7665844659811444301@ietfa.amsl.com>
Date: Fri, 11 Sep 2020 08:23:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/KeVujkFnwKrKahKcC36fJckDHv0>
Subject: [Idr] I-D Action: draft-ietf-idr-tunnel-encaps-18.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing WG of the IETF.

        Title           : The BGP Tunnel Encapsulation Attribute
        Authors         : Keyur Patel
                          Gunter Van de Velde
                          Srihari R. Sangli
                          John Scudder
	Filename        : draft-ietf-idr-tunnel-encaps-18.txt
	Pages           : 45
	Date            : 2020-09-11

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 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 use 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.  Since RFCs 5566 and 5640 rely on
   RFC 5512, they are likewise obsoleted.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-tunnel-encaps/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-idr-tunnel-encaps-18
https://datatracker.ietf.org/doc/html/draft-ietf-idr-tunnel-encaps-18

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-tunnel-encaps-18


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[Idr] I-D Action: draft-ietf-idr-tunnel-encaps-18… internet-drafts
Re: [Idr] I-D Action: draft-ietf-idr-tunnel-encap… John Scudder