Re: Responding to Ron's comment about removing fragmentation

"C. M. Heard" <heard@pobox.com> Sat, 15 November 2014 05:02 UTC

Return-Path: <heard@pobox.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C50601A1A01 for <ipv6@ietfa.amsl.com>; Fri, 14 Nov 2014 21:02:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.179
X-Spam-Level: *
X-Spam-Status: No, score=1.179 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_INXPNS=2.3, SPF_NEUTRAL=0.779] 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 cL5Odx3oNiQG for <ipv6@ietfa.amsl.com>; Fri, 14 Nov 2014 21:02:57 -0800 (PST)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AE261A0B76 for <ipv6@ietf.org>; Fri, 14 Nov 2014 21:02:57 -0800 (PST)
Received: (qmail 20538 invoked from network); 14 Nov 2014 21:02:46 -0800
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Nov 2014 21:02:46 -0800
Date: Fri, 14 Nov 2014 21:02:46 -0800
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: Jeroen Massar <jeroen@massar.ch>
Subject: Re: Responding to Ron's comment about removing fragmentation
In-Reply-To: <54666C90.4060600@massar.ch>
Message-ID: <Pine.LNX.4.64.1411142031280.8764@shell4.bayarea.net>
References: <5466662F.6080400@acm.org> <54666977.3030803@gmail.com> <54666C90.4060600@massar.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/d6rw68J-czmlrNc_blvrtYMVNnU
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 15 Nov 2014 05:02:59 -0000

On Fri, 14 Nov 2014, Jeroen Massar wrote:
> Fragmentation is not needed. Packets that are larger than 1280 where the
> MTU is 1280 should be split up by the tool/protocol sending those packets.
> 
> That is what TCP does. UDP rejects them so that the app can fix the size
> and chunk them up properly.

Some application protocols do not perform chunking but require that 
a message be encapsulated in a single UDP datagram, i.e., they rely 
on UDP to provide message framing.  DNS is one of those (unless it 
is in expensive TCP-fallback mode).  And it is an established fact 
that if DNSSEC is turned on, it's not difficult for UDP-encapsulated 
replies to exceed the 1280-byte guaranteed minimum MTU.  See Section 
3.2 of https://tools.ietf.org/html/draft-bonica-6man-frag-deprecate-02

If there were some incrementally deployable way of adding a 
fragmentation capability to UDP so that it does not have to rely on 
IP fragmentation for large datagrams, I think the case for removing 
fragmentation from IPv6 would be a lot stronger.  However, I've not 
seen such a proposal.  That's not for want of trying on my part, 
though it may well be from lack of imagination.

Mike Heard