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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 28 June 2013 22:33 UTC

Return-Path: <Fred.L.Templin@boeing.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 12FE121F941F for <ipv6@ietfa.amsl.com>; Fri, 28 Jun 2013 15:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level:
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 0kbun4H9j-Di for <ipv6@ietfa.amsl.com>; Fri, 28 Jun 2013 15:33:18 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 54D2321F9346 for <ipv6@ietf.org>; Fri, 28 Jun 2013 15:33:16 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r5SMXFAg014903 for <ipv6@ietf.org>; Fri, 28 Jun 2013 17:33:15 -0500
Received: from XCH-NWHT-10.nw.nos.boeing.com (xch-nwht-10.nw.nos.boeing.com [130.247.25.113]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r5SMXDUo014493 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 28 Jun 2013 17:33:14 -0500
Received: from XCH-EXCO-101.nw.nos.boeing.com (130.247.25.127) by XCH-NWHT-10.nw.nos.boeing.com (130.247.25.113) with Microsoft SMTP Server (TLS) id 8.3.297.1; Fri, 28 Jun 2013 15:33:13 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-EXCO-101.nw.nos.boeing.com ([fe80::fc2d:7b3b:2de5:b12c%15]) with mapi id 14.02.0328.011; Fri, 28 Jun 2013 15:33:13 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Meta-issues: On the deprecation of the fragmentation function
Thread-Topic: Meta-issues: On the deprecation of the fragmentation function
Thread-Index: AQHOdEoZI7x0xWSePUeIaE2lvBCrY5lLtSkA
Date: Fri, 28 Jun 2013 22:33:12 +0000
Message-ID: <2134F8430051B64F815C691A62D983180B024E@XCH-BLV-504.nw.nos.boeing.com>
References: <51CE05E5.4040202@si6networks.com>
In-Reply-To: <51CE05E5.4040202@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
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 22:33:25 -0000

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.

Thanks - Fred
fred.l.templin@boeing,cim