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

Fred Baker <fredbaker.ietf@gmail.com> Wed, 04 September 2019 17:57 UTC

Return-Path: <fredbaker.ietf@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 D32E4120B78; Wed, 4 Sep 2019 10:57:36 -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 0zlUHIaBxPpw; Wed, 4 Sep 2019 10:57:34 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 EE88B120B4B; Wed, 4 Sep 2019 10:57:33 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id y135so3081095wmc.1; Wed, 04 Sep 2019 10:57:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=plpZ11tmBtjOgiPQG//DCOlOz7p9ce3w89orhDFVif4=; b=hes5Qc7VAyj90KNg9/tbLlIl8SHpMAB48x7aO/f76mZv2LLEtzww/c5b+UhDAuorsk vSReps9o26OqvzKSboEO8t01tcqrJWRd/3x26VH137EhbI4YgqzB9htktnc0kOsfEpTd yZrFfmhQUFZpHjziSMp3Zibp3SEcxL9+aS8VLxP+njrPrC9e3QI9ZzBR2kp85s1GqyrQ WqC6zjivJs2Qe2vOTWPhFJLm7pMlsVVBfl5086z3vrqwP6IKgHVcPOYnryFhQkeUkezM c2n8gaMN2EKhUQcDX0Ulj1M0irQIE4mvWVnbtx/cO0EgZ5OAOYzPxK94oFwW98DHCY6S A9gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=plpZ11tmBtjOgiPQG//DCOlOz7p9ce3w89orhDFVif4=; b=mEGFLyyTOqX7Fwsrlg2c7UecGht8pXzvyXB2WxJ0kSS9WOW68819tm0lME/Gh5IGEL Zn8Nw6VP1ItkBPzRQEUxstvX6uylVYH5O1M7D86QcMItDCydw4681N99FV9uQ01DDMdA Vxu4x5Sqi8sdl98FpuVscVzNal4ZNTByflkBF6eUfhXqLzZkHfVWTE53nW605W3UZV8u eehpBcWzRlJlnnwkGmiTFCsS1psV/tNd0Tn+kORRJAUUz/5Mu0H8ICLQWXeNVg7RxsiU IIYjCp0W+hEL0aA9xarGjf3evjc4FC4JX1UDD3sKHnzcLmr0IUNKJzHiexXgQ8JHVaZT 0XhQ==
X-Gm-Message-State: APjAAAXqlNWPUoAA5QEvb6vrtAydcW+PWaV8qKgjx6shh/VY7mAA4RCI hlOObwwGYNIC2+7R/4sZxMI=
X-Google-Smtp-Source: APXvYqwbipgZHVkg5FUoI2YVU7fr3b6jcyhBxsFfahnabotzpd8ww5yanZwyFX3uTYTx8uhH3oCWkw==
X-Received: by 2002:a7b:c3d4:: with SMTP id t20mr652411wmj.136.1567619852508; Wed, 04 Sep 2019 10:57:32 -0700 (PDT)
Received: from [192.168.1.28] ([82.222.102.151]) by smtp.gmail.com with ESMTPSA id 207sm6636084wme.17.2019.09.04.10.57.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 04 Sep 2019 10:57:31 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <efabc7c9f72c4cd9a31f56de24669640@boeing.com>
Date: Wed, 4 Sep 2019 20:57:30 +0300
Cc: 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>, The IESG <iesg@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Message-Id: <2EB90A57-9BBD-417C-AEDB-AFBFBB906956@gmail.com>
References: <efabc7c9f72c4cd9a31f56de24669640@boeing.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: iPhone Mail (17A5821e)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/m8-TL8Q9CYGPQeIMay27GtuL6Nk>
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 17:57:42 -0000


Sent using a machine that autocorrects in interesting ways...

It was taken out in response to Warren Kumari’s comment that it was out of place and already covered in a section later in the document. If it is added back in, it probably belongs in that section, not the introduction.

> On Sep 3, 2019, at 5:33 PM, 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.
> 
> 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