Re: Meta-issues: On the deprecation of the fragmentation function

Hannes Frederic Sowa <hannes@stressinduktion.org> Fri, 28 June 2013 23:54 UTC

Return-Path: <hannes@stressinduktion.org>
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 8125221F99B2 for <ipv6@ietfa.amsl.com>; Fri, 28 Jun 2013 16:54:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611]
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 PvkoY0FS3Igw for <ipv6@ietfa.amsl.com>; Fri, 28 Jun 2013 16:54:26 -0700 (PDT)
Received: from order.stressinduktion.org (s15338416.onlinehome-server.info [87.106.68.36]) by ietfa.amsl.com (Postfix) with ESMTP id 67C3221F888F for <ipv6@ietf.org>; Fri, 28 Jun 2013 16:53:40 -0700 (PDT)
Received: by order.stressinduktion.org (Postfix, from userid 500) id A54B11A0CC44; Sat, 29 Jun 2013 01:53:29 +0200 (CEST)
Date: Sat, 29 Jun 2013 01:53:29 +0200
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Meta-issues: On the deprecation of the fragmentation function
Message-ID: <20130628235329.GA6519@order.stressinduktion.org>
References: <51CE05E5.4040202@si6networks.com> <2134F8430051B64F815C691A62D983180B024E@XCH-BLV-504.nw.nos.boeing.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <2134F8430051B64F815C691A62D983180B024E@XCH-BLV-504.nw.nos.boeing.com>
Cc: Fernando Gont <fgont@si6networks.com>, "ipv6@ietf.org" <ipv6@ietf.org>
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 23:54:31 -0000

On Fri, Jun 28, 2013 at 10:33:12PM +0000, Templin, Fred L wrote:
> Hi Fernando,
> 
> > 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.
> 
> I was originally thinking this way too, but now I am thinking
> that deprecation of an old method is often the first step in
> the path to adoption of a new method that avoids the old issues.
> There have been examples in the past (e.g., deprecation of site
> locals leading to ULAs), and I don't see why it would be any
> different in this case.

While browsing the draft I wondered if applications do handle the
EPROTO errno case for writes on a socket with a recevied icmp error
parameter-problem correctly today.

I doubt that recommending not implementing reassembly would be beneficial.

Greetings,

  Hannes