Re: [Int-area] I-D Action: draft-ietf-intarea-tunnels-03.txt

Joe Touch <touch@isi.edu> Thu, 07 July 2016 15:29 UTC

Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1054B12D11E for <int-area@ietfa.amsl.com>; Thu, 7 Jul 2016 08:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EODAuL7oWjnC for <int-area@ietfa.amsl.com>; Thu, 7 Jul 2016 08:29:44 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F158212D0AF for <int-area@ietf.org>; Thu, 7 Jul 2016 08:29:43 -0700 (PDT)
Received: from [192.168.1.190] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id u67FTFdG005111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 7 Jul 2016 08:29:16 -0700 (PDT)
References: <20160707062805.26768.34892.idtracker@ietfa.amsl.com>
From: Joe Touch <touch@isi.edu>
To: int-area@ietf.org
Message-ID: <577E7549.9020000@isi.edu>
Date: Thu, 07 Jul 2016 08:29:13 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160707062805.26768.34892.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: u67FTFdG005111
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/zuGpFzWsgzlfTORHZ74wWiee5Ww>
Subject: Re: [Int-area] I-D Action: draft-ietf-intarea-tunnels-03.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2016 15:29:46 -0000

Hi, all,

This update incorporates all pending changes, notably from detailed
reviews and discussions with Fred Templin, Lucy Yong, Toerless Eckert,
and Tom Herbert.

There's still a bit to do - notably to wrangle out what we want to say
regarding other RFCs in Section 5. This, and the doc's evolution,
suggest that it might be useful to consider shifting the intended track
from Informational to BCP or beyond, depending on whether we need to be
higher than BCP to "update" some of the problems outlined with
standards-track docs (most notably RFC2003).

NOTE: A brief summary will be presented by the chairs in Berlin, but I
will not be attending. Please use the list as the primary venue for
discussion.

I am currently hoping we can decide how to proceed on this doc in the
next few months so we can either remove or complete any "pending"
sections and get to WGLC early this fall.

Joe

---------

Summary of changes:
- now "updates" 4459 (informational too)
- revised MTU terminology based on list discussions (all MTUs indicate
"link" payload sizes)
- revised figures to indicate proximity of ingress/egress "interfaces"
to nodes
- moved Appendix A to new Section 3.6, as outer/inner fragmentation
issue is core
- revised Sec 4.2 (was 4.1) to explain why two different frag algs are
presented
    - one is implicit in all hosts/forwarders, irrespective of link
technology
    - one is contained "within" the link technology of a tunnel
- updated recommendations throughout section 5

Summary of additions:
- Sec 4.1 on the variety of MTU values
- Sec 4.12 on multipoint tunnels
- Sec 5.4 on diagnostics- Sec 5.5.1 on GUE
- Sec 5.5.15 on RTGWG-DT-ENCAP
- Security Considerations text on inner/outer tunnel vulnerabilities
- Recommendation text for Sec 5.5.3 on RFC2003 (IPv4 in IPv4)

----

On 7/6/2016 11:28 PM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Internet Area Working Group of the IETF.
>
>         Title           : IP Tunnels in the Internet Architecture
>         Authors         : Joe Touch
>                           Mark Townsley
> 	Filename        : draft-ietf-intarea-tunnels-03.txt
> 	Pages           : 47
> 	Date            : 2016-07-06
>
> Abstract:
>    This document discusses the role of IP tunnels in the Internet
>    architecture, in which IP datagrams are carried as payloads in non-
>    link layer protocols. It explains their relationship to existing
>    protocol layers and the challenges in supporting IP tunneling based
>    on the equivalence of tunnels to links.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-intarea-tunnels/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-intarea-tunnels-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-intarea-tunnels-03
>
>
> 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/
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area