Re: Responding to Ron's comment about removing fragmentation

Jeroen Massar <jeroen@massar.ch> Fri, 14 November 2014 20:49 UTC

Return-Path: <jeroen@massar.ch>
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 3CD941AC39F for <ipv6@ietfa.amsl.com>; Fri, 14 Nov 2014 12:49:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham
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 hvdYsIGKNIXH for <ipv6@ietfa.amsl.com>; Fri, 14 Nov 2014 12:49:52 -0800 (PST)
Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [IPv6:2a02:2528:503:2::4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17C0E1A9175 for <ipv6@ietf.org>; Fri, 14 Nov 2014 12:49:52 -0800 (PST)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jeroen) by bastion.ch.unfix.org (Postfix) with ESMTPSA id 9376A1008708D; Fri, 14 Nov 2014 20:49:49 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=massar.ch; s=DKIM2009; t=1415998189; bh=RHUKivBHrNbNuv01Bd6U1yNKhgANJvZXOevwG9AClPM=; h=Date:From:To:Subject:References:In-Reply-To; b=CzvPThiCt5DICfSp12dkJ14fxUTZu5UCHYOLz2nWfbVhVIKYXv5jgANRzU8Ph2hij mSbX4o+qaU0ThXI2HCmgRmioqCgjXI17JBpOdjwsMG/zkW8oGBDnyTSjxwFIVYNtc/ Ap9Zm4ZvfFCDO8kdwm9NHR6rAhfGSvN6N0vix2pyhe+nP5Oz4sKA9UUjwKLtSwWUFA MMhmnUFDEYd0qUcGbTk74sM6naAv7tnTH880oYtNDV5GG8G1nxoXJdnqkGR5/HXuzU xcn1we1yK8a8oHcYzM8Bpq9yMDxBhDB/SnOfZPnQiPynj0oWlrs5Mn9bprGL4a5Xis SYLeX5O3MeUjA==
Message-ID: <54666AEB.8010701@massar.ch>
Date: Fri, 14 Nov 2014 21:49:47 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, Erik Nordmark <nordmark@acm.org>, IETF IPv6 <ipv6@ietf.org>
Subject: Re: Responding to Ron's comment about removing fragmentation
References: <5466662F.6080400@acm.org> <4ee7bd6bbd61425a8720dcd6ac402854@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <4ee7bd6bbd61425a8720dcd6ac402854@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/ScXCyJjHoXPxdJlb1V3ZKQYm3r4
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: Fri, 14 Nov 2014 20:49:53 -0000

On 2014-11-14 21:44, Ronald Bonica wrote:
> Erik,
> 
> In one sense, I agree with you. Encapsulation is the best argument
> for fragmentation.
> 
> However, I think the designers of IPv6 anticipated the problem.
> Knowing that most interfaces support a 1500 byte MTU, the designers
> specified a required MTU of 1280. This leaves 220 bytes for
> encapsulation.

Exactly. And if one needs more space, then we need to talk about getting
MTU discovery also being able to scale up. See other threads ;)

> BTW, I don't intend to resurrect draft-bonica-6man-frag-deprecate.
> There doesn't appear to be WG support for that.

That is because there are people who do not want to change the work they
have been working on for a long long time.

Though I appreciate the effort that a lot of folks have stuck into it.
Fragmentation (and Flow Labels...) are not matching the ideas used on
the current Internet.

We have learnt a lot of over the close to 20 years that IPv6 has existed
and a lot has changed in the Internet during that time.

As IPv6 is in a way still in it's infancy we have still the possibility
to make changes to it.

Lets not hold "but I did a lot of work on that back then" stop
possibilities of fixing something that will be used for another 50 years.

Unless one wants to start doing this whole "IPng" thing again a lot
sooner than that...

Greets,
 Jeroen