IETF Logo Mail Archive

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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 24 June 2013 17:50 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 3EFF421E8106 for <ipv6@ietfa.amsl.com>; Mon, 24 Jun 2013 10:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 Bq4+vLFTsKlI for <ipv6@ietfa.amsl.com>; Mon, 24 Jun 2013 10:50:40 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id 375E811E816F for <ipv6@ietf.org>; Mon, 24 Jun 2013 10:50:39 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r5OHoc16005202 for <ipv6@ietf.org>; Mon, 24 Jun 2013 12:50:39 -0500
Received: from XCH-NWHT-08.nw.nos.boeing.com (xch-nwht-08.nw.nos.boeing.com [130.247.25.112]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r5OHobmX005183 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 24 Jun 2013 12:50:38 -0500
Received: from XCH-BLV-503.nw.nos.boeing.com (130.247.25.192) by XCH-NWHT-08.nw.nos.boeing.com (130.247.25.112) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 24 Jun 2013 10:50:37 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-BLV-503.nw.nos.boeing.com ([169.254.3.132]) with mapi id 14.02.0328.011; Mon, 24 Jun 2013 10:50:37 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker (fred)" <fred@cisco.com>, Tore Anderson <tore@fud.no>
Subject: RE: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt
Thread-Topic: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt
Thread-Index: AQHOcGcOI1L7sow7kkSTr5SDOLoWMJlFJNrg
Date: Mon, 24 Jun 2013 17:50:36 +0000
Message-ID: <2134F8430051B64F815C691A62D983180A93A6@XCH-BLV-504.nw.nos.boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F85151@BY2PRD0512MB653.namprd05.prod.outlook.com> <51C56E60.5040009@fud.no> <8C48B86A895913448548E6D15DA7553B9237F3@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B9237F3@xmb-rcd-x09.cisco.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
Cc: "ipv6@ietf.org 6man-wg" <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: Mon, 24 Jun 2013 17:50:46 -0000

Hi Fred,

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Fred Baker (fred)
> Sent: Sunday, June 23, 2013 4:12 PM
> To: Tore Anderson
> Cc: ipv6@ietf.org 6man-wg
> Subject: Re: New Version Notification for draft-bonica-6man-frag-
> deprecate-00.txt
> 
> 
> On Jun 22, 2013, at 2:29 AM, Tore Anderson <tore@fud.no> wrote:
> > - When a SIIT translator receives an IPv4 packet with DF=0 that would
> > result in an IPv6 packet that would exceed the IPv6 link MTU, it will
> > split the original packet into IPv6 fragments.
> 
> It *could* fragment the IPv4 packet and send it in two unfragmented
> IPv6 packets.
> 
> > I cannot support your draft until it discusses or provides solutions
> for
> > the above considerations.
> 
> I'm in a similar case with respect to protocols above IPv6 (OSPF and
> NFS/UDP come quickly to mind) that depend on fragmentation to deal with
> the issue. I think the Robustness Principle tells us that such
> applications SHOULD figure out how to live with PMTU, but it also tells
> us that we can't deprecate fragmentation unless all known instances
> that depend on it have defined practical work-arounds. I suspect that
> this would imply the re-creation of the fragmentation feature in an
> intermediate protocol,

That is essentially what SEAL does - it provides an intermediate-level
segmentation and reassembly capability that avoids the pitfalls of IP
fragmentation.

> which seems like a lot of work with little real gain.

It's not that bad, and IMHO worth it.

Thanks - Fred
fred.l.templin@boeing.com

> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email