Re: Is Fragmentation at IP layer even needed ?

Warren Kumari <warren@kumari.net> Mon, 08 February 2016 18:23 UTC

Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7608C1B30ED for <ietf@ietfa.amsl.com>; Mon, 8 Feb 2016 10:23:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] autolearn=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 wg8BdZSQoDJz for <ietf@ietfa.amsl.com>; Mon, 8 Feb 2016 10:23:31 -0800 (PST)
Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) (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 CFA301B30EA for <ietf@ietf.org>; Mon, 8 Feb 2016 10:23:30 -0800 (PST)
Received: by mail-yk0-x229.google.com with SMTP id u9so90511358ykd.1 for <ietf@ietf.org>; Mon, 08 Feb 2016 10:23:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=ai6NZj+g6H2aVOqp6Mo8jYtvS7sQ1Ts02LHf3Mjehjo=; b=ZfQRZyMPq7xLFKUB1RDaT43CI8ChLmPXu/qjFqsmf2Ez13yU1VJo+mE/EYzKWbW02/ BuiBSRc289bDcTzajGCuaTwL24v8ytJ9Ue0WL+UPQxgpc7VXVVEx+i8eNew+Jn16CYjv aU1/TdC1HHrRzx/TBqodUQlWnVzyMiG3GrPuBxwBCgiUbsQyWJzDXRUXMvyBO3ygxQvG VAADjdm+rSWuFGw9SFYFqKsZ2eXw32jd6effooHgDg54+RnMxj4zYkxcF3lyu2nNoE1T 2h4+/sAqyOBJPEPD5cNwGfcuItwr0hEruja/Tnguj58ZKXE7QKRncWHjxzGh7ylQRxBe Jblw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; bh=ai6NZj+g6H2aVOqp6Mo8jYtvS7sQ1Ts02LHf3Mjehjo=; b=aZmgl7xVNjGWWYWVFwz2RdWiJv/YU3cMysWWgRLaHRh3JT1x8EEryzYjFC6w3Mam0w CW/62PWILhxI/NE22d0shQgxD4Gsd2j62s5Oi/rWz3esRxORNq+6eVrvi/bJzjrpgTkO vKuMeVHV/xcS8bC0FcUXozzDe6fKvK7CikMgQUDM0smSot+ZLd2DoiNpdT4gm0YQz9u+ sXoae+I6HErtweun3psSpo9lvuS+ImvmWuRejYOH5hCdaWt8+TcL9PlzFZgXgGLHBxa7 qrmZTeaUYjuaH/SJTag/gy9MBMRjj4yQVDHwlGYE6ImYjAQJ2NO+Uco4K7sS4a01FRJN UbIw==
X-Gm-Message-State: AG10YORrMv1DK/osK9TMLkcbytsML3GKRFxdDVhrzl4ZAJJTN5zpoRWTnXIw9egOq2w6X2coNDXLwhQEMQn5hpp0
X-Received: by 10.37.84.212 with SMTP id i203mr15468811ybb.119.1454955810148; Mon, 08 Feb 2016 10:23:30 -0800 (PST)
MIME-Version: 1.0
References: <CAOJ6w=G4ysJGsNC_F-N5+-P9-OmUYDx1f14mew7GNAEaUmDfYg@mail.gmail.com> <20160208155214.91667.qmail@ary.lan> <CAOJ6w=H3F5Tyez0=hJYnq+wscBsCN0ROxwA4RppjfXzV5nwBJw@mail.gmail.com> <2F942F4E-F890-49A1-91C8-F304B9FBA2D3@weston.borman.com>
In-Reply-To: <2F942F4E-F890-49A1-91C8-F304B9FBA2D3@weston.borman.com>
From: Warren Kumari <warren@kumari.net>
Date: Mon, 08 Feb 2016 18:23:20 +0000
Message-ID: <CAHw9_iKw5chdJqy4QTqAKXa5q3pMgSQFdbZfi-7TKOs325+1wA@mail.gmail.com>
Subject: Re: Is Fragmentation at IP layer even needed ?
To: David Borman <dab@weston.borman.com>, Alexey Eromenko <al4321@gmail.com>
Content-Type: multipart/alternative; boundary="001a11423afc3a87b3052b464cd9"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9oXXVARc-LU9oEtaj8WH6EobE-w>
Cc: John Levine <johnl@taugh.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 18:23:32 -0000

On Mon, Feb 8, 2016 at 9:05 AM David Borman <dab@weston.borman.com> wrote:

>
> > On Feb 8, 2016, at 10:08 AM, Alexey Eromenko <al4321@gmail.com> wrote:
> >
> > On Mon, Feb 8, 2016 at 5:52 PM, John Levine <johnl@taugh.com> wrote:
> > >2. What kind of UDP applications use such big packets, over 1280 bytes ?
> >
> > >Um, the DNS with EDNS0, and particularly with DNSSEC?  Is this a trick
> question?
> >
> >
> > Yes.
> > The trick lies right there in IPv6 specification:
> >
> > "A node must be able to accept a fragmented packet that, after
> >    reassembly, is as large as 1500 octets."
> > ... which is not much greater than 1280 bytes defined as minimum MTU for
> IPv6.
> >
> > Basically, Fragmentation, as specified in RFC-2460 (IPv6), solves the
> problem ONLY for packet-sized between 1280 and 1500 bytes. Which is why I
> doubt if it is useful at all.
>
> That’s the minimum required implementation, which guarantees that you can
> send at least a basic ethernet sized packet to any host.  What is omitted
> in the above qoute is next 2 sentences:
>    "A node is permitted to
>    accept fragmented packets that reassemble to more than 1500 octets.
>    An upper-layer protocol or application that depends on IPv6
>    fragmentation to send packets larger than the MTU of a path should
>    not send packets larger than 1500 octets unless it has assurance that
>    the destination is capable of reassembling packets of that larger
>    size.”
> So if you are writing an application that needs >1500 octets, use an IPv6
> implementation that supports >1500 octet fragmentation and reassembly.
>

... but as an application writer (or, basically anyone else), I have no
control over the "IPv6 implementation". Even if I'm in an environment where
I do control the OS / model of all devices, and I know they support >1500
octet, it seems like a bad idea to *rely* on that. Sometime I'm going to
want to change OS / add some other device, be able to interact with some
other system. This sounds like vendor lock at its worst...

W




>
>                 -David Borman
>
> >
> > (I also understand, that IPv4 fragmentation is much more flexible, yes.
> It can go as small as 68 byte packets.)
>
>