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

[John Scudder <[e-mail]>]

See my replies to Alvaro’s reviews in the threads "AD Review of draft-ietf-idr-tunnel-encaps-17” and "AD Review of draft-ietf-idr-tunnel-encaps-15” for a full discussion of the changes in version 18. Do note there are a few normative changes, which I’ve called out in those messages.

—John

On Sep 11, 2020, at 11:23 AM, [e-mail]<mailto:[e-mail]> wrote:

[External Email. Be cautious of content]


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://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-idr-tunnel-encaps/__;!!NEt6yMaO-gk!QlvBso1hytbLX9WjZt4Mc0nZCdylZ4asB18Aguv4PAQ8UOjwlLuJ7X9hGXaCjA$

There are also htmlized versions available at:
https://urldefense.com/v3/__https://tools.ietf.org/html/draft-ietf-idr-tunnel-encaps-18__;!!NEt6yMaO-gk!QlvBso1hytbLX9WjZt4Mc0nZCdylZ4asB18Aguv4PAQ8UOjwlLuJ7X9kFoZZ7w$
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-idr-tunnel-encaps-18__;!!NEt6yMaO-gk!QlvBso1hytbLX9WjZt4Mc0nZCdylZ4asB18Aguv4PAQ8UOjwlLuJ7X8icljyqw$

A diff from the previous version is available at:
https://urldefense.com/v3/__https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-tunnel-encaps-18__;!!NEt6yMaO-gk!QlvBso1hytbLX9WjZt4Mc0nZCdylZ4asB18Aguv4PAQ8UOjwlLuJ7X-8jaZjwQ$


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:
https://urldefense.com/v3/__ftp://ftp.ietf.org/internet-drafts/__;!!NEt6yMaO-gk!QlvBso1hytbLX9WjZt4Mc0nZCdylZ4asB18Aguv4PAQ8UOjwlLuJ7X8QbvPsPw$


_______________________________________________
Idr mailing list
[e-mail]
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/idr__;!!NEt6yMaO-gk!QlvBso1hytbLX9WjZt4Mc0nZCdylZ4asB18Aguv4PAQ8UOjwlLuJ7X_7qbm2YA$