Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard

Joe Touch <touch@isi.edu> Tue, 07 February 2017 20:19 UTC

Return-Path: <touch@isi.edu>
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 B37A6129E9B; Tue, 7 Feb 2017 12:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 DlnGh4kQ3RFE; Tue, 7 Feb 2017 12:19:03 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 30A39129579; Tue, 7 Feb 2017 12:19:03 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17KIEFX013871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 12:18:15 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: otroan@employees.org
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu>
Date: Tue, 7 Feb 2017 12:18:16 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/rN87xLnIiU6apQu0kTN_PAzLO7w>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "Eggert, Lars" <lars@netapp.com>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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, 07 Feb 2017 20:19:05 -0000


On 2/7/2017 12:06 PM, otroan@employees.org wrote:
> Joe,
...
>>> I'm very much in favour of working on better ways of doing Path MTU discovery.
>>> A blanket statement of "use "PLMTUD" seems very premature though.
>>>
>> The point is that this document fails to indicate the current state of PMTUD. It correctly notes that:
>>    An extension to Path MTU Discovery defined in this document can be
>>    found in [
>> RFC4821
>> ].  It defines a method for Packetization Layer Path
>>    MTU Discovery (PLPMTUD) designed for use over paths where delivery of
>>    ICMP messages to a host is not assured.
>>
>>
>>
>> IMO, it fails to note that this case - where ICMP messages are assured along a path - is effectively a unicorn except within systems maintained by a single entity.
>>
>>> RFC1981 has 70 citations:
>>>
>>> http://www.arkko.com/tools/allstats/citations-rfc1981.html
>>>
>>>
>>> Could you expand on your view of how this pertains to advancing RFC1981?
>>>
>> It's called last call input. My input is that this document needs to be more realistic in noting that, for all intents, ICMP-based MTU discovery isn't viable and that other methods need to be *expected*, not just that they're available.
> Right, but if you are correct that ICMP-based MTU discovery is not viable then this document should not be advanced.
Not necessarily. It's fine to update a protocol that works inside an
enterprise or other controlled environment.

> At the same time for many protocols we have nothing else. An operator can break any protocol if that's their policy. And that's the breakage we're talking about here, not any issues with the protocol specification.

Well, it's a problem with the protocol spec that it's susceptible to
operator interference.

> There is a philosophical aspect of this. (Which I'm not the best person to represent as I skipped my University studies in philosophy and used the student loan to buy a motorcycle... (and only read the art of motorcycle maintenance years later) )
> This is a tussle. The IETF specifies protocols under the assumption that operators treat those protocols largely as specified. The 5-10% failure of PMTUD messages may be caused by misconfiguration, misunderstanding or mis-intent... Many of our protocols are suffering from the same fate. Should the IETF adjust all its protocols to be as middlebox friendly as possible? You can make this argument about IPv6 fragments, any packet with IPv6 extension headers, IPv4 fragments. Or anything but TCP port 443/80 and UDP port 53 for that matter. Are we as the IETF going to continue standardising protocols to work as best as they possible can, ignoring protocol abuse, or are we going to bend over and do whatever it takes to make it work for those 5-10% who've actively broken the protocol? What about the 90-90% where the protocols work as expected?

What I'm suggesting is a lot simpler - just text that makes it clear
what the current state of deployment of support (or interference) for
this protocol is.

I appreciate that you want to not point at PLPMTUD because it's not
widely supported, but **for the same reason** this doc should not hold
up this solution without pointing out very clearly that it basically
isn't going to be work.

Joe