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 18:14 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 46990120ADE; Wed, 4 Sep 2019 11:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.218
X-Spam-Level:
X-Spam-Status: No, score=-1.218 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, URIBL_BLOCKED=0.001] 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 SDiOIGbTE7sk; Wed, 4 Sep 2019 11:14:00 -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 9C8FA120271; Wed, 4 Sep 2019 11:14:00 -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=wZx4J/V6zyXsBhiac3o22oHGKqZWXOhN/WRDWUpR5EQ=; b=hJJ56haJNLxVZEII3jp3HGU35 IYqoGCKJmHrxG4oXjCvctZbrm6QcE4Bp1Hpyl0B51k/AHGz8of953LMdTUhOmR2k9lmYvpUYJsCI9 Om2b/bshq++Bs3LxQJ/6F6mB9zNz8R8PNM/HeH/k2dclIs3XdgBpWENY0s3MPaJnvD9VREyX1a4jN 9E5iY7krZvziQTYbvub6hPAvST+dBkpSa17ogT2jWEL1d/FwuhVlWAU86V0n5N9IoVkvzxCJPD2PA jyUUMph0YDwwAHsL6Yd0/LBQi2KkvknEn8hmMzzwpdbo/QwbdJQMk0mur8/WYcGRarZPCGBVMA/UJ tJJ/vJxCA==;
Received: from [::1] (port=54848 helo=server217.web-hosting.com) by server217.web-hosting.com with esmtpa (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1i5Zn1-003UfI-Q8; Wed, 04 Sep 2019 14:14:00 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_96e926d19725d694b89aa4aff5266d5c"
Date: Wed, 04 Sep 2019 11:13:55 -0700
From: Joe Touch <touch@strayalpha.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, Alissa Cooper <alissa@cooperw.in>, Joel Halpern <joel.halpern@ericsson.com>, draft-ietf-intarea-frag-fragile@ietf.org, int-area@ietf.org, The IESG <iesg@ietf.org>, intarea-chairs@ietf.org
In-Reply-To: <2EB90A57-9BBD-417C-AEDB-AFBFBB906956@gmail.com>
References: <efabc7c9f72c4cd9a31f56de24669640@boeing.com> <2EB90A57-9BBD-417C-AEDB-AFBFBB906956@gmail.com>
Message-ID: <a70a00af8afff8ec75ce4137d65e816d@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/ehbOu-srwUsmbwtuIQFFhivn2fQ>
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 18:14:03 -0000

IMO, it belongs back with a forward reference to the detail. 

To do otherwise buries at least part of the lead here - as you note in
another response - to not mistake this document for a step towards
deprecation. 

Joe 

On 2019-09-04 10:57, Fred Baker wrote:

> 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