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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 18 May 2017 02:10 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 57B99129484 for <int-area@ietfa.amsl.com>; Wed, 17 May 2017 19:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.82
X-Spam-Level:
X-Spam-Status: No, score=-2.82 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 25p1D7M4OU5m for <int-area@ietfa.amsl.com>; Wed, 17 May 2017 19:10:22 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 56D9F129470 for <int-area@ietf.org>; Wed, 17 May 2017 19:10:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v4I2AHER019693; Wed, 17 May 2017 19:10:18 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v4I2ABe3019679 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Wed, 17 May 2017 19:10:12 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 17 May 2017 19:10:11 -0700
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Wed, 17 May 2017 19:10:11 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
CC: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] I-D Action: draft-ietf-intarea-tunnels-05.txt
Thread-Index: AQHSpxB0dZTEVAB270esoqM4xp8NZaGqcslggACqEoCAASy6sIBNWwmAgAADDUA=
Date: Thu, 18 May 2017 02:10:11 +0000
Message-ID: <50bf8e85647c400b9d17a6fe46954512@XCH15-06-08.nw.nos.boeing.com>
References: <149062888196.30638.8369941985115982808@ietfa.amsl.com> <f5ab0422-fd49-9082-147b-8312e974de7e@isi.edu> <4d2a86f4948c4dc49ab3b0729743d028@XCH15-06-08.nw.nos.boeing.com> <583e59d2-f846-6cd6-8e15-f3a0888889ac@isi.edu> <6ede932f07ca4b8ebd17f82e17eb4cf4@XCH15-06-08.nw.nos.boeing.com> <1688a61c-7bba-1b61-c16d-ab4620346578@isi.edu>
In-Reply-To: <1688a61c-7bba-1b61-c16d-ab4620346578@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.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/08GOZYaQ6y8qYGf970KhobOcWvw>
Subject: Re: [Int-area] I-D Action: draft-ietf-intarea-tunnels-05.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
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, 18 May 2017 02:10:23 -0000

Hi Joe,

Can't get to it just now, but I promise I will respond to these as early as possible.
About this particular question, you may know that I hold Bob B. in the highest
esteem and took his word on this subject as I would a voice from the heavens.

I know Bob probably pulls his pants on one leg at a time in the morning just
like we all do, but his long tenure as RFC Editor and authorship of bedrock
docs like RFC1122 have held me in awe of him. That is not to say that I do
not have high regards for you (I do) but to me Bob has always been "the
man". I know - I need to get over that and move on...

Thanks - Fred 

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Wednesday, May 17, 2017 11:52 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: int-area@ietf.org
> Subject: Re: [Int-area] I-D Action: draft-ietf-intarea-tunnels-05.txt
> 
> Hi, Fred,
> 
> Circling back to this item:
> 
> 
> On 3/29/2017 2:18 PM, Templin, Fred L wrote:
> > One other comment. I agree with figures 12 and 13 but (and I think this is
> > a crucial point) I think they need a supporting sentence or two explaining
> > why the procedure is "fragment then encapsulate" and not "encapsulate
> > then fragment".
> Will do.
> 
> > This is the difference between tunnel fragmentation
> > and ordinary outer fragmentation, where your document is correctly
> > advocating tunnel fragmentation.
> Yeah, but I was unable to find definitive and RFC citations for those
> terms ("inner fragmentation" and "outer fragmentation"). 4459 mentions
> fragmentation of 'inner' and 'outer', but those terms go back to 2003
> and before, and I'm not sure warrant a citation.
> 
> > To the best of my knowledge, this was
> > first documented in Section 3.1.7 of RFC2764 and should be cited as such.
> > At least, that is what Bob B. suggested to me about 10yrs ago.
> The idea of differentiating inner and outer fragmentation goes back to
> RFC2003 at least, AFAICT.
> 
> That section of RFC2764 mentions that outer fragmentation avoids
> fragmentation inside the tunnel, but doesn't recommend it (it just says
> "alternative"). Further, it claims that none of the existing tunneling
> protocols support this (even though RFC2003 does).
> 
> I'm not convinced this is worth tracking down for its origins. Let me
> know if you feel otherwise, but we'd need stronger evidence AFAICT.
> 
> Joe