Re: [Int-area] draft-bonica-intarea-frag-fragile-01

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 01 June 2018 09:54 UTC

Return-Path: <swmike@swm.pp.se>
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 56B581275FD for <int-area@ietfa.amsl.com>; Fri, 1 Jun 2018 02:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 1kn7O-BjKkwW for <int-area@ietfa.amsl.com>; Fri, 1 Jun 2018 02:54:45 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6ACF127522 for <int-area@ietf.org>; Fri, 1 Jun 2018 02:54:45 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 87D2DB1; Fri, 1 Jun 2018 11:54:40 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1527846880; bh=i/L+7CDGPm9PyiAyPcPVw5H8hWaYWJ869dPTVmB+LiY=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=YKaDoBXCwyJBqX1QNZeLr+tXJry9RF2ku46q8DqQwa7CPejhnfK9mG722MsUygUu8 0jrNPYSnN3dAc5GCVnqm2pXRVuBPgmySajF6j2nsOVjNUfxhHx12EMksOG88b8BF5t qGHfq8BTklMFVAC4jBL35evqL3lenZ50/GDUHt+0=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 85FBAB0; Fri, 1 Jun 2018 11:54:40 +0200 (CEST)
Date: Fri, 01 Jun 2018 11:54:40 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Joe Touch <touch@strayalpha.com>
cc: Ron Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
In-Reply-To: <855AFF4E-F2B7-4C35-ABA5-EFC571AF90F9@strayalpha.com>
Message-ID: <alpine.DEB.2.20.1806011150370.17103@uplift.swm.pp.se>
References: <BLUPR0501MB2051C0DCCE28384FCD08F7C4AEDA0@BLUPR0501MB2051.namprd05.prod.outlook.com> <57DFBADC-9064-4DF8-AAC1-8C0DBB41D8A6@strayalpha.com> <76F3B3E5-6FA8-4A27-815C-32415E0D7CB6@gmail.com> <FCE8FC77-3A30-4EE3-B6A1-35969E7DD1E2@strayalpha.com> <SN6PR05MB424048AD14382C38788DE158AE630@SN6PR05MB4240.namprd05.prod.outlook.com> <855AFF4E-F2B7-4C35-ABA5-EFC571AF90F9@strayalpha.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="-137064504-1394257731-1527846880=:17103"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/9Qo20DmYxGzbDMRistdlsJjs4aY>
Subject: Re: [Int-area] draft-bonica-intarea-frag-fragile-01
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 01 Jun 2018 09:54:49 -0000

On Thu, 31 May 2018, Joe Touch wrote:

> I disagree.
>
> UDP fragmentation has its benefits and uses, but should not be required when a transport layer isn’t needed - e.g., for IP tunneling.
>
> Fundamentally, IP fragmentation is fragile for only a few reasons:
> 1) the ID space is small (which shouldn’t matter unless there is a very large amount of reordering)
> 2) loss of fragments creates inefficiencies (true, but routers can fate-share fragments they drop sometimes, just as was eventually done for ATM AAL5)
> 3) in-network devices can’t find transport ports in some fragments, causing problems for NATs, policy filters and firewalls, etc.
>
> Of these, my view is that #3 is the only reason actually driving a claim of fragility - and all it tells me is that “the Internet is fragile when devices don’t follow the rules”.
>
> I do not think it is appropriate to validate that conclusion.

You're fundamentally right, unfortunately operational reality adds lots of 
more points to your list, meaning the end outcome is that IP fragmentation 
doesn't work well in real life.

I am as opposed to letting bad practices win as you probably are, but I 
also don't think this is fixable. This means applications need to have a 
mode where they do not rely on IP fragments for basic operation.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se