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

Randy Bush <randy@psg.com> Wed, 08 February 2017 05:05 UTC

Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9280129955 for <ietf@ietfa.amsl.com>; Tue, 7 Feb 2017 21:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 FBSyLkPyWahH for <ietf@ietfa.amsl.com>; Tue, 7 Feb 2017 21:05:18 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 620ED1298D2 for <ietf@ietf.org>; Tue, 7 Feb 2017 21:05:18 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cbKRQ-0004mD-DY; Wed, 08 Feb 2017 05:05:16 +0000
Date: Wed, 08 Feb 2017 14:05:14 +0900
Message-ID: <m2lgthw9v9.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
In-Reply-To: <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com>
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> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-jHuCQTlhZ8EaLic3QLhm8OKIsQ>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 05:05:19 -0000

>> Would something like this help?
>> (borrowed from https://en.wikipedia.org/wiki/Path_MTU_Discovery)
>> 
>> "Many network security devices block all ICMP messages for perceived
>>  security benefits, including the errors that are necessary for the proper
>>  operation of PMTUD. This can result in connections that complete the
>>  TCP three-way handshake correctly, but then hang when data is transferred.
>>  This state is referred to as a black hole connection."
> 
> Yes. What we are asked to do for Internet Standard is show that a protocol
> is widely deployed and is interoperable. That's undoubtedly true of RFC1981.
> The fact that it also has an important failure mode should certainly be
> documented, but I suspect that every Internet Standard has at least
> one important failure mode.

the problem is that this particular failure mode is essentially "does
not work on the real internet."  perhaps documenting that is useful.
but i guess this is ipv6.

randy