Re: [Int-area] Alissa Cooper's No Objection on draft-ietf-intarea-frag-fragile-16: (with COMMENT)

Joe Touch <touch@strayalpha.com> Wed, 04 September 2019 15:43 UTC

Return-Path: <touch@strayalpha.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 7689912013F; Wed, 4 Sep 2019 08:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
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 kdfThL82GDvo; Wed, 4 Sep 2019 08:43:18 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 1BE8612023E; Wed, 4 Sep 2019 08:43:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Message-ID:References:In-Reply-To:Subject:Cc: To:From:Date:Content-Type:MIME-Version:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=J7zV2wSsORN2p7HIOFjeqgS0goBC3kd5XqB+n0vtAlo=; b=fHJOJ+bDuDViVf3lqQ9uDVwYd a1V/VK72eixiewk6/3oNKSaGfYXNX0mh5cfa/3OsHeIYlRcwCsSgsjQmyfgtpqS75PkgkrrwSJO45 A8qjLRiRKXAZ46wQVFUzRm5ckb1N4GlRsccHTGLem5pfHzgtoTVEiswXJ+O5mn2p4SCbMegJG7gUe ngGSWPrKfOEBXWz2oSf3BmHkLrI18bm2wb6tZjlFVj7OsxHgkLwEa9LHqEp/88xNluGug/49ilqIV HXSCJ6gcqu4jZQl3qk1ZlH51wL4U4U3vlIvNi9hZ1nMBx6wrsgMzTEx4FFa46yO17kvzk8iehelx7 szd/6T6Bw==;
Received: from [::1] (port=44182 helo=server217.web-hosting.com) by server217.web-hosting.com with esmtpa (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1i5XR5-001QQw-09; Wed, 04 Sep 2019 11:43:11 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_a0804c7bc33be091d04dc9aee34d304c"
Date: Wed, 04 Sep 2019 08:43:06 -0700
From: Joe Touch <touch@strayalpha.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, int-area@ietf.org, IESG <iesg@ietf.org>, Joel Halpern <joel.halpern@ericsson.com>, draft-ietf-intarea-frag-fragile@ietf.org, intarea-chairs@ietf.org
In-Reply-To: <25c7130ecf734692a4f6746141d96038@boeing.com>
References: <156751558566.9632.10416223948753711891.idtracker@ietfa.amsl.com> <B7C5DF29-92B2-477B-9C30-F47E338038EE@strayalpha.com> <efabc7c9f72c4cd9a31f56de24669640@boeing.com> <9331E721-F7F8-4C22-9BE4-E266726B3702@gmail.com> <7bfbaf5fa12c4a9bac3e46ece5dfdcde@boeing.com> <0BF34BFA-5F30-4EE1-9F5E-18D9ECA8D424@gmail.com> <CALx6S37xhhS5ezhJu6-HQmftwY9cBzuCxeaW9thTbKBa2hizcw@mail.gmail.com> <A8A10E03-6EEC-4F60-A213-7D66084BA754@gmail.com> <09d0dc428430407f8154f40d47a417dc@boeing.com> <3AF76A3A-E18D-4CC2-8FA8-6A465FD06E28@gmail.com> <25c7130ecf734692a4f6746141d96038@boeing.com>
Message-ID: <217867cd58757f18b812be57c2c35eaa@strayalpha.com>
X-Sender: touch@strayalpha.com
User-Agent: Roundcube Webmail/1.3.7
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/M_5zz95uiQM1-YnWrOc2d2o0p0M>
Subject: Re: [Int-area] Alissa Cooper's No Objection on draft-ietf-intarea-frag-fragile-16: (with COMMENT)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 04 Sep 2019 15:43:20 -0000

On 2019-09-04 07:23, Templin (US), Fred L wrote:

> Bob, 
> ...
> Paragraph #1 beginning "This document acknowledges" looks good, but then
> why include paragraphs #2 and #3 since 'intarea-tunnels' is the place to discuss
> IP-in-IP encapsulation. So, why not shorten Section 5.3 and have it as simply:
> 
> 5.3.  Packet-in-Packet Encapsulations
> 
> This document acknowledges that in some cases, packets must be
> fragmented within IP-in-IP tunnels.  Therefore, this document makes no
> additional recommendations regarding IP-in-IP tunnels.
> See [I-D.ietf-intarea-tunnels] for further discussion.

There was a reason this text was included up front - despite the
implications of this draft, IP-IP tunnels are not going anywhere anytime
soon. IPsec tunnel mode has not been deprecated. 

To Bob's other point, this was approved by the WG and the IETF last call
as up front. 

Why are we changing it now? 

Joe