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

Bob Hinden <bob.hinden@gmail.com> Tue, 03 September 2019 16:10 UTC

Return-Path: <bob.hinden@gmail.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 6CDFC12013C; Tue, 3 Sep 2019 09:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 pcT-U5rd6Yjo; Tue, 3 Sep 2019 09:10:04 -0700 (PDT)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 BCB881208DF; Tue, 3 Sep 2019 09:10:03 -0700 (PDT)
Received: by mail-wr1-x42e.google.com with SMTP id g7so18158508wrx.2; Tue, 03 Sep 2019 09:10:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=EqhnQZuAAnam8F48QwrFJjYaYr4F/SkIqpcbne5k5us=; b=AWKWTS3RJNw4iVJfGsuA051hbkaHX1Zg+pXOEswXLB09AaBQb9OLxLAUiC8k++Ixrz fMtDl4Zcj0YOxDI7fKRfUoLzCffzVP7zmg+kXMwjlxp60SmChzMwu4R8+J0yTWv41nLA u4mdhE+JWyXk/mDCzBxOHFSVunwL1mseF8jCld4H9OQNJ/sFW4rc4Ql6kcUev9O7leky ueU8ATjRUjda/CcTONy5GFkR/ukWt41rEV2mq94MV6OTKME5KA8HDCdJ1TKFqPWYgOrm AfzG8EDWRGFfrk78W3O3G4VQYZCauU4+Lu3KyaiGB2XWcQjlHgL2b4jMHqVgtDz7Fn/d 6GCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=EqhnQZuAAnam8F48QwrFJjYaYr4F/SkIqpcbne5k5us=; b=pj600I1R2Ia/d4zofx7vNjvkJOwku+8yR8lHYVu8YjYuXk/1Vr3V//1GE2NczQeDE2 2oK1jmfB5FRr7KvVJibME73WrsYGFhfhpYyPUE7S9AZJFCTgz1+Fm60GcyitAIBm7/fs rWCmMouoVhMqJUCpbkhnWI+XEuZKSWdduyUPKmOZ9AxOjEptFeo54A47/bgzjGlKH0rw scBfcAodVQzLOoeWCR8oak4TBsq1Es9HpijMJb5Y/TWhHRC9OtB29E15uEcQBlEBa5xM 3blAoNalFTld9edah67vKDhFCRUuTrXn3884Zyvla9/UB5NYPvcQklP90Sc3MJjI+mEH N6XQ==
X-Gm-Message-State: APjAAAWZMdRYutFNAIy1a1733flcEe39nNZSMXIPIa2TuQ9WRsItDtQI /NGTsl8cIxdgNr1EqOJ33FA=
X-Google-Smtp-Source: APXvYqwrzFn2uucd7GwXMvyt4EWh25BE7iTw9DP9I+G43w9ucIWCXvrfoXabBPR3Jiv/rAJPwCO2rA==
X-Received: by 2002:a05:6000:1187:: with SMTP id g7mr3103737wrx.192.1567527002130; Tue, 03 Sep 2019 09:10:02 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:2937:9917:7066:3310? ([2601:647:5a00:ef0b:2937:9917:7066:3310]) by smtp.gmail.com with ESMTPSA id f6sm34368615wrh.30.2019.09.03.09.09.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Sep 2019 09:10:00 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <9331E721-F7F8-4C22-9BE4-E266726B3702@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_981CD165-1A55-4FE2-9152-5C0B104D1E9C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 3 Sep 2019 09:09:55 -0700
In-Reply-To: <efabc7c9f72c4cd9a31f56de24669640@boeing.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Joe Touch <touch@strayalpha.com>, Alissa Cooper <alissa@cooperw.in>, Joel Halpern <joel.halpern@ericsson.com>, "draft-ietf-intarea-frag-fragile@ietf.org" <draft-ietf-intarea-frag-fragile@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, IESG <iesg@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
References: <156751558566.9632.10416223948753711891.idtracker@ietfa.amsl.com> <B7C5DF29-92B2-477B-9C30-F47E338038EE@strayalpha.com> <efabc7c9f72c4cd9a31f56de24669640@boeing.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/Wi2Te0xC1W7LO3yYn5WoKlI8Ld4>
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: Tue, 03 Sep 2019 16:10:14 -0000

Fred,

> On Sep 3, 2019, at 7:33 AM, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> 
> Why was this section taken out:
> 
>> 1.1.  IP-in-IP Tunnels
>> 
>>   This document acknowledges that in some cases, packets must be
>>   fragmented within IP-in-IP tunnels [I-D.ietf-intarea-tunnels].
>>   Therefore, this document makes no additional recommendations
>>   regarding IP-in-IP tunnels.

This text in the Introduction was removed because, as noted in Warren Kumari
Comment (2019-08-07 for -15), this didn’t need to be in the introduction, and it didn’t say very much that isn’t described later in the document.

The normative text in Section 5.3. "Packet-in-Packet Encapsulations” is unchanged.  I think Section 5.3 covers the topic.  It includes the reference to [I-D.ietf-intarea-tunnels].

Bob


> 
> Tunnels always inflate the size of packets to the point that they may exceed
> the path MTU even if the original packet is no larger than the path MTU. And,
> for IPv6 the only guarantee is 1280. Therefore, in order to robustly support
> the minimum IPv6 MTU tunnels MUST employ fragmentation.
> 
> Please put this section of text back in the document where it belongs.
> 
> Thanks - Fred
> 
>> -----Original Message-----
>> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Joe Touch
>> Sent: Tuesday, September 03, 2019 7:06 AM
>> To: Alissa Cooper <alissa@cooperw.in>
>> Cc: Joel Halpern <joel.halpern@ericsson.com>om>; draft-ietf-intarea-frag-fragile@ietf.org; int-area@ietf.org; The IESG <iesg@ietf.org>rg>;
>> intarea-chairs@ietf.org
>> Subject: Re: [Int-area] Alissa Cooper's No Objection on draft-ietf-intarea-frag-fragile-16: (with COMMENT)
>> 
>> Hi, all,
>> 
>> So let me see if I understand:
>> 
>> Alissa issues a comment.
>> 
>> We discuss this on the list and come to a rare consensus on a way forward.
>> 
>> The new draft is issued that:
>> 
>> a) ignores the list consensus
>> b) removes a paragraph not under the DISCUSS (1.1)
>> c) now refers to vague “other documents” without citation
>> d) most importantly:
>> 
>> 	REMOVES a key recommendation that we MAY use frag where it works
>> 
>> 	Asserts the false claim that IP fragmentation “will fail” in the Internet,
>> 	despite citing evidence that the *majority of the time* it does work
>> 		e.g., for IPv6, sec 3.9
>> 
>> What happened? Why is a change this substantial not reflecting the *list consensus*?
>> 
>> Joe
>> 
>>> On Sep 3, 2019, at 5:59 AM, Alissa Cooper via Datatracker <noreply@ietf.org> wrote:
>>> 
>>> Alissa Cooper has entered the following ballot position for
>>> draft-ietf-intarea-frag-fragile-16: No Objection
>>> 
>>> When responding, please keep the subject line intact and reply to all
>>> email addresses included in the To and CC lines. (Feel free to cut this
>>> introductory paragraph, however.)
>>> 
>>> 
>>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>>> for more information about IESG DISCUSS and COMMENT positions.
>>> 
>>> 
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-intarea-frag-fragile/
>>> 
>>> 
>>> 
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>> 
>>> Thanks for addressing my DISCUSS.
>>> 
>>> 
>>> _______________________________________________
>>> 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