Re: Confirm consensus to adopt draft-hinden-6man-mtu-option

Ole Troan <otroan@employees.org> Tue, 06 August 2019 07:10 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D092B120137; Tue, 6 Aug 2019 00:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-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 qhjVw1E5PtfC; Tue, 6 Aug 2019 00:10:41 -0700 (PDT)
Received: from clarinet.employees.org (unknown [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85FE8120018; Tue, 6 Aug 2019 00:10:41 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 25FA24E11A26; Tue, 6 Aug 2019 07:10:40 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id D23D919F57FF; Tue, 6 Aug 2019 09:10:37 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Confirm consensus to adopt draft-hinden-6man-mtu-option
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAN-Dau0nkQK5bqqGRU_Lfx7dTHSzOEjcujZSnWKxuthm9szJSg@mail.gmail.com>
Date: Tue, 06 Aug 2019 09:10:37 +0200
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, 6man Chairs <6man-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5C266D1-2C5C-4654-97D7-DEFA3FF759FD@employees.org>
References: <2268E842-37F5-4439-8711-573D23055073@employees.org> <CAN-Dau2X2RFrKCRpSKRYV3kGzyshALb+RzZ90w6DdWF6s9f1og@mail.gmail.com> <B87A6C08-34E4-4838-97B0-341971751BEE@gmail.com> <CAN-Dau0nkQK5bqqGRU_Lfx7dTHSzOEjcujZSnWKxuthm9szJSg@mail.gmail.com>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ELGUoHUUghy9LHxzyvOCKaoYFcg>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2019 07:10:44 -0000

David,

> I agree that the general state of PMTUD on the Internet is poor, but there are limited domains where the state of PMTUD as currently specified is mostly functional, the R&E world is one of those domains, and with the scope defined for this draft it is quite possible to implement such a domain with functional PMTUD as currently specified. So, part of the experiment needs to compare this new solution to the current solution in limited domains where the current solution is functional, especially if this solution is to ever go beyond the experimental stage.
> 
> Furthermore, the end-to-end use of larger MTUs is an end-to-end problem and focusing on PMTUD to the exclusion of the first and last hop LAN problems is doomed to failure. The point is even if all routers between two hosts implement this HBH EH perfectly if large MTUs (>1500) on the LANs at each end are not specified and interoperable how is this going to work? I'm not aware of BCPs for Large MTU LANs and I don't know of IPv6 test suites that test the interoperability of hosts on Large MTU LANs.
> 
> So if you want to do 9k MTUs between Data Centers we need a definition for 9K MTU on LANs between hosts that is consistently interoperable, which I don't think exists.

As a side-note it might be worth looking at https://tools.ietf.org/html/draft-van-beijnum-multi-mtu-05
One could imagine using the HBH MTU option in NS/NA exchanges between directly connected nodes too.
But that would still only be a hint, probing would be necessary.

Cheers,
Ole