Meta-issues: On the deprecation of the fragmentation function

Fernando Gont <fgont@si6networks.com> Fri, 28 June 2013 21:54 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3001621F9D4E for <ipv6@ietfa.amsl.com>; Fri, 28 Jun 2013 14:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PypeNOJfgNG for <ipv6@ietfa.amsl.com>; Fri, 28 Jun 2013 14:54:20 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 8353F21F9D32 for <ipv6@ietf.org>; Fri, 28 Jun 2013 14:54:20 -0700 (PDT)
Received: from [2001:5c0:1400:a::53b] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UsgcP-0002At-Ut; Fri, 28 Jun 2013 23:54:18 +0200
Message-ID: <51CE05E5.4040202@si6networks.com>
Date: Fri, 28 Jun 2013 23:53:41 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Meta-issues: On the deprecation of the fragmentation function
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 28 Jun 2013 21:54:21 -0000

Folks,

I wanted to comment on some met-issues regarding the deprecation of the
IPv6 fragmentation function.

** On the motivation of deprecating the fragmentation function **

So far (and without having read Ron's recent I-D -- shame on me), it
looks like the main two reasons for deprecating the fragmentation
function are:

1) The inability of middle-boxes to parse past the first XXX bytes of a
packet

2) Unavailability of the connection-id (five-tuple) in the non-first
fragments.

Regarding "1)", I believe that deprecating fragmentation is not really
the right solution. If anything, one could require the entire header
chain to be within the first XXX bytes of a packet (as a former version
of draft-ietf-6man-oversized-header-chain did). Besides, if we're going
to deprecate the fragmentation function because of this, then we should
also deprecate all extension headers, because they might lead to the
same issue.

Regarding "2)", IPv4 doesn't have the connection-id in the non-first
fragments, either. So whatever middle-boxes are doing, they should/could
do it in the same way as they currently do for IPv4.


** On the impact on applications **

It has been stated that fragmentation is uncommon. However, multiple
uses for IPv6 fragmentation have been mentioned -- from NFS, to tunnels
or the recent data posted by Mark Andrews. I think such use cases should
really be considered.

That aside, if the IPv6 fragmentation function is removed, it also means
that UDP can only be used for applications that send datagrams
smaller than 1280 bytes (assuming no Path-MTUD for UDP). I haven't done
a survey myself, but I wonder to what extent one can really conclude
there's no need for that (e.g., I'm told that in the stock market sector
they employ multicast... which might mean that they need to send such
"large" UDP datagrams).


** Therefore.... **

Considering the above, I guess I'm in the camp of "avoid fragmentation
where possible". However, I don't think I'd go as far as deprecating it.

Just my two cents.

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