[LAC-TF] RFC1981 to standard (Fwd: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard9

[Fernando Gont]

#FacePalm


-------- Forwarded Message --------
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU
Discovery for IP version 6) to Internet Standard
Date: Wed, 08 Feb 2017 14:05:14 +0900
From: Randy Bush <randy at psg.com>
To: Brian E Carpenter <brian.e.carpenter at gmail.com>
CC: ietf at ietf.org

>> 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