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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 08 July 2016 20:00 UTC

Return-Path: <Fred.L.Templin@boeing.com>
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 0193012D128 for <int-area@ietfa.amsl.com>; Fri, 8 Jul 2016 13:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 eiqrDDel_eAY for <int-area@ietfa.amsl.com>; Fri, 8 Jul 2016 13:00:05 -0700 (PDT)
Received: from ewa-mbsout-02.mbs.boeing.net (ewa-mbsout-02.mbs.boeing.net [130.76.20.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4C0812B019 for <int-area@ietf.org>; Fri, 8 Jul 2016 13:00:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u68K05qx032300; Fri, 8 Jul 2016 13:00:05 -0700
Received: from XCH15-05-04.nw.nos.boeing.com (xch15-05-04.nw.nos.boeing.com [137.137.100.67]) by ewa-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u68K04LO032268 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 8 Jul 2016 13:00:04 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) by XCH15-05-04.nw.nos.boeing.com (2002:8989:6443::8989:6443) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 8 Jul 2016 13:00:03 -0700
Received: from XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) by XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) with mapi id 15.00.1178.000; Fri, 8 Jul 2016 13:00:03 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] I-D Action: draft-ietf-intarea-tunnels-03.txt
Thread-Index: AQHR2GRt4KMsEiq3UE+L137uMsNVnaAO8uMQ
Date: Fri, 08 Jul 2016 20:00:03 +0000
Message-ID: <77275dc8e3214bb6a0139818394437f9@XCH15-05-05.nw.nos.boeing.com>
References: <20160707062805.26768.34892.idtracker@ietfa.amsl.com> <577E7549.9020000@isi.edu>
In-Reply-To: <577E7549.9020000@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.137.12.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/kZ_f_Xjk1JYdKjEkKSVbB4hGRrE>
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: Fri, 08 Jul 2016 20:00:11 -0000

Hi Joe,

Sorry to say, but I still disagree with most aspects of the text on fragmentation
and MTU, which are largely the same as what appeared in the previous draft
version. I will say that we agree on one fact, however, in that fragmentation
is ultimately unavoidable.

When we discussed this last year, I thought we had established some things
that got reflected in Section 3.13 of 'draft-templin-aerolink'. I'd like to invite
you and the working group to review that text which IMHO presents a
better MTU and fragmentation consideration for tunnels.

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Joe Touch
> Sent: Thursday, July 07, 2016 8:29 AM
> To: int-area@ietf.org
> Subject: Re: [Int-area] I-D Action: draft-ietf-intarea-tunnels-03.txt
> 
> 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
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area