Re: [tcpm] PLPMTUD for all protocols

William Herrin <bill@herrin.us> Wed, 28 March 2018 15:26 UTC

Return-Path: <bill@herrin.us>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C4FD127419 for <tcpm@ietfa.amsl.com>; Wed, 28 Mar 2018 08:26:45 -0700 (PDT)
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 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 JjH8PBLQxuFk for <tcpm@ietfa.amsl.com>; Wed, 28 Mar 2018 08:26:43 -0700 (PDT)
Received: from magic.dirtside.com (magics.dirtside.com [199.33.225.25]) by ietfa.amsl.com (Postfix) with ESMTP id 3EDFF1273B1 for <tcpm@ietf.org>; Wed, 28 Mar 2018 08:26:42 -0700 (PDT)
Received: from minoc.dirtside.com (minoc.dirtside.com [70.184.240.82]) by magic.dirtside.com (8.14.3/) with ESMTP id w2SFQX60020501 for <tcpm@ietf.org>; Wed, 28 Mar 2018 11:26:33 -0400
X-Really-To: <tcpm@ietf.org>
Received: from mail-pl0-f52.google.com (mail-pl0-f52.google.com [209.85.160.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by minoc.dirtside.com (Postfix) with ESMTPSA id 51934EBF92 for <tcpm@ietf.org>; Wed, 28 Mar 2018 11:26:33 -0400 (EDT)
Received: by mail-pl0-f52.google.com with SMTP id f5-v6so1778493plj.13 for <tcpm@ietf.org>; Wed, 28 Mar 2018 08:26:33 -0700 (PDT)
X-Gm-Message-State: AElRT7HFEU/B7WsCbN2Lr/2OHFSVTzo7HcQ3zp/ETMc10n/JIs1NmlF4 xC0eE/wFP3xauCxWFblF6dWHIcQzZx3nKZs4YBg=
X-Google-Smtp-Source: AIpwx48B+tOSts7qcTB4CgnxZTRHNMir6/UbP1/szI60yeYcmOCLKdJKk2tIhIoGAXosO860njWyvIF0ZV8ca3+5DnU=
X-Received: by 2002:a17:902:8602:: with SMTP id f2-v6mr4185170plo.73.1522250792334; Wed, 28 Mar 2018 08:26:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.183.67 with HTTP; Wed, 28 Mar 2018 08:26:11 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.20.1803281034310.20609@uplift.swm.pp.se>
References: <alpine.DEB.2.20.1803281034310.20609@uplift.swm.pp.se>
From: William Herrin <bill@herrin.us>
Date: Wed, 28 Mar 2018 11:26:11 -0400
X-Gmail-Original-Message-ID: <CAP-guGVEcnk09yi8sz+fmghpeb91Y8tQb+LsEmSF+0e+f6oGhw@mail.gmail.com>
Message-ID: <CAP-guGVEcnk09yi8sz+fmghpeb91Y8tQb+LsEmSF+0e+f6oGhw@mail.gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: tcpm@ietf.org
Content-Type: text/plain; charset="UTF-8"
X-Spam-Checker: magic.dirtside.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/wq1RYGte9CH-8OF0ufzQJ1im55s>
Subject: Re: [tcpm] PLPMTUD for all protocols
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2018 15:26:46 -0000

On Wed, Mar 28, 2018 at 4:43 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> In trying to advocate for all protocols implementing PLPMTUD (RFC4821) and
> shipping with it default on, I received pushback when I suggested/asked why
> modern TCP stacks don't come with PMTU blackhole detect turned on.

Hi Mikael,

My knee-jerk response reading the RFC is that the up-probe process
seems very brittle with layer violations all over the place.


> What's wrong with it, and how do we fix it?

Don't attempt a layer-3 general purpose solution that boils down to a
large set of dirty hacks? Spitballing here, but in TCP you could
create an option for the remote to respond with the largest received
fragment size when a fragmented packet is received and if the option
is negotiated then send the up-probes with the DF bit cleared. If the
remote doesn't support it, shrink the MSS but don't try to grow it
again. If the remote does respond with the largest fragment size then
you get the exact path MTU as a result of one probe without disrupting
the communication flow.

Sacrilege to suggest sending anything without the DF bit set, but if
the router's return has a black hole, maybe the answer is to let the
router communicate forward instead.

Regards,
Bill Herrin


-- 
William Herrin ................ herrin@dirtside.com  bill@herrin.us
Dirtside Systems ......... Web: <http://www.dirtside.com/>