Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)

Fernando Gont <fgont@si6networks.com> Mon, 08 February 2016 23:52 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5BC1B3DB8 for <ipv6@ietfa.amsl.com>; Mon, 8 Feb 2016 15:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 AGv088TDJSrK for <ipv6@ietfa.amsl.com>; Mon, 8 Feb 2016 15:52:30 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AC0F1B3D9F for <ipv6@ietf.org>; Mon, 8 Feb 2016 15:51:59 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.164.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 9E058206AA8; Tue, 9 Feb 2016 00:51:55 +0100 (CET)
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: Michael Richardson <mcr+ietf@sandelman.ca>, Fernando Gont <fernando@gont.com.ar>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <7592.1454699773@obiwan.sandelman.ca> <56B50394.2010504@gont.com.ar> <14373.1454861717@obiwan.sandelman.ca>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B916EF.5080200@si6networks.com>
Date: Mon, 08 Feb 2016 19:30:07 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <14373.1454861717@obiwan.sandelman.ca>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WFqu3W9ZwsQsxS5H3P93Ig-pU7o>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker (fred)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 08 Feb 2016 23:52:34 -0000

On 02/07/2016 01:15 PM, Michael Richardson wrote:
> 
> Fernando Gont <fernando@gont.com.ar> wrote:
>     >> Templin, Fred L <Fred.L.Templin@boeing.com> wrote: > On the other
>     >> hand, paths that lead to Internet destinations cannot be > counted on
>     >> to deliver the necessary ICMPs. In that case, RFC4821 > provides a
>     >> mitigation.
>     >>
>     >> > But, if we do not believe that there are paths for which traditional
>     >> > PMTUD can still be used safely, then we should be working to
>     >> deprecate > RFC1981 instead of making it a standard.
>     >>
>     >> I think that the mitigation is far more reliable than 1981.  So, I'd
>     >> rather deprecate RFC1981.
>     >>
>     >> {I noticed that 4821 is not on by default in most Linux
>     >> distros/kernels, and I actually want to know if there is some reason
>     >> for it}
> 
>     > Yes: convergence time.
> 
> Yes, I've noticed that it takes a few re-transmissions on the first
> connection to a site in the case where the MTU is limited and the ICMPs are
> lost, but when the MTU is unblocked, there is no delay.

If you employ RFC4821 as icmp-less PMTUD, it doesn't matter whether the
ICMPs get blocked or not. If you implement RFC4821 for blackhole
detection, then I agree with you.




> An implementation that wanted to avoid even the re-transmissions in the
> blocked case could limit themselves to 1280 sized packets and send some 1500
> byte probes have gotten through.
> 
> If 4821 is turned off, then the connection is mysteriously blocked, and
> always fail.
> 
> So, your answer does not make sense to me.

"My" answer is actually what I recall from discussing this with Linux
kernel developers 10 years ago -- I guess that they were referring to
"RFC4821 as icmp-less PMTUD".

That said, if the toggle in Linux is to use RFC4821 as icmp-less PMTUD,
then my (relayed) response would apply. OTOH, if the toggle is simply to
employ RFC4821 for blackhole detection then I'd agree with you.

FWIW, I'd expect RFC4821 fo blackhole detection to be "on by default",
and, if anything, to be able to turn on RFC4821 as icmp-less PMTUD (but
this one *not* "on by default", for the reasons already stated).

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492