Re: FW: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt

Hagen Paul Pfeifer <hagen@jauu.net> Mon, 24 June 2013 20:40 UTC

Return-Path: <hagen@jauu.net>
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 69E3A21E8129 for <ipv6@ietfa.amsl.com>; Mon, 24 Jun 2013 13:40:18 -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 Kl1BrhCYQnT9 for <ipv6@ietfa.amsl.com>; Mon, 24 Jun 2013 13:40:18 -0700 (PDT)
Received: from Chamillionaire.breakpoint.cc (Chamillionaire.breakpoint.cc [IPv6:2001:4d88:1ffa:82:880:aa0:9009:64ae]) by ietfa.amsl.com (Postfix) with ESMTP id 65D1321E8108 for <ipv6@ietf.org>; Mon, 24 Jun 2013 13:40:13 -0700 (PDT)
Received: from pfeifer by Chamillionaire.breakpoint.cc with local (Exim 4.72) (envelope-from <hagen@jauu.net>) id 1UrDYZ-0007pQ-Dp; Mon, 24 Jun 2013 22:40:11 +0200
Date: Mon, 24 Jun 2013 22:40:09 +0200
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: FW: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt
Message-ID: <20130624204008.GB3647@virgo.local>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F85151@BY2PRD0512MB653.namprd05.prod.outlook.com> <51C32FA9.1090207@gmail.com> <2CF4CB03E2AA464BA0982EC92A02CE2509F85F38@BY2PRD0512MB653.namprd05.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2509F85F38@BY2PRD0512MB653.namprd05.prod.outlook.com>
X-Key-Id: 98350C22
X-Key-Fingerprint: 490F 557B 6C48 6D7E 5706 2EA2 4A22 8D45 9835 0C22
X-GPG-Key: gpg --recv-keys --keyserver wwwkeys.eu.pgp.net 98350C22
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Arturo Servin <arturo.servin@gmail.com>
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: Mon, 24 Jun 2013 20:40:18 -0000

* Ronald Bonica | 2013-06-21 19:00:51 [+0000]:

>I don't know of a study. However, this is probably a safe assumption considering that:
>
>- many TCP implementation leverage PMTUD
>- many enterprise block fragments
>- many firewalls, by default, block IPv6 fragments

One of my clients using extensive fragmentation features, their
application/transport layer is "build around" IPv6 fragmentation. Problem:
all components are hard wired in silicon, there is no change/modification
possible in the next decade.

I'm a little bit sad about this incompatible protocol change/break.
Fragmentation was an early design failure in IPv4 - for IPv6 fragmentation it
is still supported and I see no way to obsolete fragmentation without
incompatible protocol change. Especially "New IPv6 host implementations MAY
support IPv6 fragmentation and reassembly, but are not required to do so." and
"Network operators MAY filter IPv6 fragments.". - this break legacy
application/stacks using fragmentation.

Fragmentation is a nightmare for a middleboxes, no doubt and fragmentation was
an design failure. But fixing it in a incompatible manner is even worse. There
should never ever an protocol break.


Hagen