Re: [tsvwg] Status of ECN encapsulation drafts (i.e., stuck)

"Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net> Tue, 17 March 2020 05:21 UTC

Return-Path: <ietf@gndrsh.dnsmgr.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 592503A1816 for <tsvwg@ietfa.amsl.com>; Mon, 16 Mar 2020 22:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.623
X-Spam-Level:
X-Spam-Status: No, score=-1.623 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.274, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 tYmWrCcepoVQ for <tsvwg@ietfa.amsl.com>; Mon, 16 Mar 2020 22:21:43 -0700 (PDT)
Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2ED83A1815 for <tsvwg@ietf.org>; Mon, 16 Mar 2020 22:21:42 -0700 (PDT)
Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 02H5LfTk096141; Mon, 16 Mar 2020 22:21:41 -0700 (PDT) (envelope-from ietf@gndrsh.dnsmgr.net)
Received: (from ietf@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 02H5LfC4096140; Mon, 16 Mar 2020 22:21:41 -0700 (PDT) (envelope-from ietf)
From: "Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>
Message-Id: <202003170521.02H5LfC4096140@gndrsh.dnsmgr.net>
In-Reply-To: <E350CC13-73CD-40ED-B1F5-C79EA7E41490@strayalpha.com>
To: Joseph Touch <touch@strayalpha.com>
Date: Mon, 16 Mar 2020 22:21:41 -0700 (PDT)
CC: "Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-Mailer: ELM [version 2.4ME+ PL121h (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/vIL2SAP5BBOt0QOJvLT2SB78SZU>
Subject: Re: [tsvwg] Status of ECN encapsulation drafts (i.e., stuck)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2020 05:21:45 -0000

> > On Mar 16, 2020, at 8:09 PM, Rodney W. Grimes <ietf@gndrsh.dnsmgr.net> wrote:
> > 
> >> 
> >> 
> >>> On Mar 16, 2020, at 2:42 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
> >>> 
> >>>> On 16 Mar, 2020, at 11:38 pm, Joseph Touch <touch@strayalpha.com> wrote:
> >>>> 
> >>>> That?s not always possible. If the net runs over minimal IPv6 links, there?s no way to ensure a traffic can support 1280B packets over 1280B tunnels.
> > 
> > True, not always possible, but very often practical and done as minimal IPv6 links generally only exist inside of tunneled tunnels :-)  ((Ie, GRE -> IPSec -> PPPoE))
> > 
> >>> 
> >>> I think the 1280B minimum was intended to allow for the possibility of running through tunnels on conventional 1500B physical networks.
> >> 
> >> Actually, the 1280B is the path min; the receiver min is 1500B exactly to allow for this sort of frag/reassembly (where a tunnel egress *is* such a receiver). The 1500B comes from Ethernet; the 1280B is smaller deliberately.
> > 
> > receiver min?  I am not familiar with that term.
> 
> EMTU_R as defined in RFC 1122. See also draft-ietf-intarea-tunnels

EMTU_R as defined in RFC 1122 is greater than or equal to 576, not 1500 as you stated.

> 
> > And as you state 1500B no doubt comes from the Ethernet specification.
> > 
> > I shall endorse Jonathans position with this:
> > 	The 1280 IPv6 minMTU originated from a November 14, 1997 mailing
> > 	from Steve Deering to the IPng mailing list, which stated:
> > 	"In the ipngwg meeting in Munich, I proposed increasing the IPv6
> >        minimum MTU from 576 bytes to something closer to the Ethernet MTU
> >        of 1500 bytes, (i.e., 1500 minus room for a couple layers of
> >        encapsulating headers, so that min- MTU-size packets that are
> >        tunneled across 1500-byte-MTU paths won't be subject to
> >        fragmentation/reassembly on ingress/egress from the tunnels, in most
> >        cases).
> > 
> > So infact this is all meant to MINIMIZE fragmentation.
> 
> Except that it doesn?t unless you KNOW that the path supports 1500B. But there?s no rule in IPv6 that the EMTU_S min is 1280B *AND* the links MUST support 1500B.
> 
> I.e., that?s why the EMTU_S min is 1500B - so you can reassemble when you don?t know otherwise. But even when IPv6 was created there were problems with PMTUD.

EMTU_S min is not 1500B, and infact 1122 says:
	It is generally desirable to avoid local fragmentation and to
	choose EMTU_S low enough to avoid fragmentation in any gateway
	along the path.  In the absence of actual knowledge of the
	minimum MTU along the path, the IP layer SHOULD use
	EMTU_S <= 576 whenever the destination address is not on a
	connected network, and otherwise use the connected network's

Again the intent here appears to be to avoid framentation along the path,
and iirc is what lead the the path MTU being cached by the BSD kernels
route table code, which is one mechansim used by people to deal with
the path MTU problem and tunnels.

> Joe
-- 
Rod Grimes                                                 rgrimes@freebsd.org