Re: [Int-area] WG Adoption Call: IP Fragmentation Considered Fragile

Tom Herbert <tom@herbertland.com> Sun, 26 August 2018 17:08 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DFFA130DC9 for <int-area@ietfa.amsl.com>; Sun, 26 Aug 2018 10:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 c4miyWmNtogL for <int-area@ietfa.amsl.com>; Sun, 26 Aug 2018 10:08:09 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 F25EF130DC5 for <int-area@ietf.org>; Sun, 26 Aug 2018 10:08:08 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id d4-v6so15486764qtn.13 for <int-area@ietf.org>; Sun, 26 Aug 2018 10:08:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GcwOA9kVFFFgIJp1l47RBs2Xoi9q0o3HqPfWnq1A6OU=; b=veIEqzMhHrLkW8GT7gsBEvieypxJ/7P1aBRRZ/j6zsq7IL/CwKcaZNkgip/8Jm3Iht eGgnii2tKeErTAAXbA3DN2FKV6KuBtU37F4MA9/Y0WYO4deRzq3qPXS/Wys+CZmFgZTX lTxm1umHQYtmX/9wUt+QDcle2atT6t1l8vlnwVBuhEILIW978MtdwExVRwly70yN7AZx G6k8LiL66N35UcM/q9Yfp9RLGXn7w8EpptTtj/Aq0ifLXXV654Lc1FnPSM6BIIWNjcrG fYe63O+BCQdycWkvQGeMdKQLIgYbpDfYwV4llNCQGVVFxxc6X5kAkoOmJ0UeVX8ri23C jdxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GcwOA9kVFFFgIJp1l47RBs2Xoi9q0o3HqPfWnq1A6OU=; b=Ze95qitOkSD+Y71mXKxBrJVXNOp4ybWyOy9j1ZQKFmzLfHA110qKQfj750JQ3plSAo iADlW6NWX2V7B6d/E5CFjkPiJsXeFnGZ8aBpn/sf9ew4Ceqxd2BDglrv8saTfdJ5/gvp EUMC1oTL8B55QJUpgoPOfJFVMisXJ3Uvnj6zEwwieXdM5EvUDOxkkK9au4v47Zbh4DUk agxgUP5COvLZbSCFCDhSpGiNhS23Gzi9rQ3APBx+A08kfKrVH96RZANVqKSJ8+PfSxFs TmwME639a86Y0Abvqq2tqcs9sMQoGKM8Fpep8h4NgWGorgY67rhXutZJWdqBj/0wAEWh CP7g==
X-Gm-Message-State: APzg51Cb2BocRBEh1t06MEcafxcPzr1Eik3pJLBR0xGnEmdgkxPQxaoo 7GwemOxSQCYRzhocvPnCdDMDKEeEP1BesOMw6iDi4y/U
X-Google-Smtp-Source: ANB0VdY0fRD1TyTI5yEaN/K6nS3IN9oHBypzsvfFFoFDZeZHd82zxlvGKc9wjVIJJOiC/pJMwNziRhBZ2B1i8OsXWec=
X-Received: by 2002:aed:2aa1:: with SMTP id t30-v6mr10780213qtd.101.1535303287816; Sun, 26 Aug 2018 10:08:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac8:3312:0:0:0:0:0 with HTTP; Sun, 26 Aug 2018 10:08:07 -0700 (PDT)
In-Reply-To: <20180825032457.ol5rlrr7h2kqi6px@faui48f.informatik.uni-erlangen.de>
References: <CALx6S36Ef3t7Axmx9hg994DHpVM=NdW-7ygf89E==gL4XKrkQg@mail.gmail.com> <5E21B3C1-0420-404C-9824-9B7E5A850BC5@employees.org> <CALx6S34qmKngi3hK_PVrJA1DMa5kfaLww3jfqRKN=up5v0Y0Ww@mail.gmail.com> <8D23C8B1-C2DA-4A8B-A2BE-8CCF6233B3A5@strayalpha.com> <D1D5EDCE-7C43-4CD8-947C-AA43CDB18892@employees.org> <1B04E207-08FA-400F-BBED-67379FEFD64E@strayalpha.com> <137751A3-7C52-4CCF-AE9C-B99C4A85EFC1@strayalpha.com> <alpine.DEB.2.20.1808021749020.19688@uplift.swm.pp.se> <CALx6S35kw2dodgG2L3LE3A5y8RYEXy6izQWgrQTwg7-yPqpzOg@mail.gmail.com> <alpine.DEB.2.20.1808030857370.19688@uplift.swm.pp.se> <20180825032457.ol5rlrr7h2kqi6px@faui48f.informatik.uni-erlangen.de>
From: Tom Herbert <tom@herbertland.com>
Date: Sun, 26 Aug 2018 10:08:07 -0700
Message-ID: <CALx6S35-n_ROEZv0NReVEWTUhnyc25SNJb5DaeqtnxPAPk6QjQ@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, int-area <int-area@ietf.org>, intarea-chairs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/vfuhO5NgOXqB-iUTG5mhR3I37VI>
Subject: Re: [Int-area] WG Adoption Call: IP Fragmentation Considered Fragile
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Aug 2018 17:08:10 -0000

On Fri, Aug 24, 2018 at 8:24 PM, Toerless Eckert <tte@cs.fau.de> wrote:
> On Fri, Aug 03, 2018 at 09:48:25AM +0200, Mikael Abrahamsson wrote:
>> I've kept saying "Networks must support ip fragmentation properly.
>
> Why ? Wheren't you also saying that you've got (like probably many
> else on this thread) all the experience that only TCP MSS gets you
> working connectivity in many case (like hotels) ?
>
> IMHO, we (network layer) should accept defeat on network layer
> fragmentation and agree that we should make it easier for the
> transport layer to resolve the problem.
>
> Aka: I would lvoe to see a new ICMPv4/ICMPv6 reply and/or PTB reply option
> indicating "Fragmented Packets Not Permitted". Any network device which
> for whatever reason does not like Fragemnts would simply drop
> fragmented packets and send this as a reply. Allows then the
> transport layer to automatically use packetization  (such as TCP MSS)
> to get packets through.
>
> Of course. Will take a decade to get ubiquitously deployed, but
> neither IPv4 nor IPv6 will go away, only the problems with fragmentation
> will become worse and work if we do not have an exit strategy like this.
>
Toeless,

I'm curious why you think the problems with fragmentation will become
worse. The draft and much of this thread has already highlighted the
problems with fragmentation that happen because of non-conformant
implementation. While there's a lot of legacy implementation that
might hard to fix completely, I don't think we've seen a good argument
that these problems are infeasible to fix in new deployments and
products. I think this draft is an opportunity not only highlight the
problems, but to suggest some practical fixes to improve the situation
as a way forward.

Tom

> If we don't try an exit strategy like this, we will just get what
> Joe said, the complete segmentation of the Internet with more and
> more L4 or even higher layer proxies.
>
> Btw: +1 for adopting the doc as a WG item, but primarily because everything
> before section 7 is on a way to become a good read of reality. Section
> 7 recommendations is only a faith based exercise (praying) as long as it tries to
> get the job done primarily by appealing to application developers.
>
> Cheers
>     Toerless
>
>
>