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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 11 July 2013 16:41 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 315C521F9AC4 for <ipv6@ietfa.amsl.com>; Thu, 11 Jul 2013 09:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.544
X-Spam-Level:
X-Spam-Status: No, score=-6.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 vRTetfDnMeR2 for <ipv6@ietfa.amsl.com>; Thu, 11 Jul 2013 09:41:51 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id C5DE021F9943 for <ipv6@ietf.org>; Thu, 11 Jul 2013 09:41:51 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r6BGfp5p017077 for <ipv6@ietf.org>; Thu, 11 Jul 2013 09:41:51 -0700
Received: from XCH-NWHT-04.nw.nos.boeing.com (xch-nwht-04.nw.nos.boeing.com [130.247.64.250]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r6BGfnhE017059 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 11 Jul 2013 09:41:49 -0700
Received: from XCH-BLV-404.nw.nos.boeing.com (130.247.25.157) by XCH-NWHT-04.nw.nos.boeing.com (130.247.64.250) with Microsoft SMTP Server (TLS) id 8.3.297.1; Thu, 11 Jul 2013 09:41:49 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-BLV-404.nw.nos.boeing.com ([169.254.4.225]) with mapi id 14.02.0328.011; Thu, 11 Jul 2013 09:41:49 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, james woodyatt <jhw@apple.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: AQHOfLVoEVtgyhVSFES4anVAs4ggI5lci/SAgAAN9ACAAAD+gIAACExQgAALN4CAAF6xUIAA9WwAgAALYhCAAC2kgIAAD8OAgAAKNQCAADgwEIABI5lw
Date: Thu, 11 Jul 2013 16:41:47 +0000
Message-ID: <2134F8430051B64F815C691A62D983180BA667@XCH-BLV-504.nw.nos.boeing.com>
References: <FAD482FE-4583-472A-8B57-E789A942686E@gmail.com> <1DF7BDE3-1490-41FE-A959-EC8EC54B0A5F@tzi.org> <8B84E185-36AC-4F22-A88E-5A2F1200AE8B@gmail.com> <51DC48F7.2080901@dougbarton.us> <2CF4CB03E2AA464BA0982EC92A02CE2509FA39E2@BL2PRD0512MB646.namprd05.prod.outlook.com> <51DC5955.4030700@dougbarton.us> <2CF4CB03E2AA464BA0982EC92A02CE2509FB8317@BY2PRD0512MB653.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983180B812F@XCH-BLV-504.nw.nos.boeing.com> <2CF4CB03E2AA464BA0982EC92A02CE2509FBAB7B@BY2PRD0512MB653.namprd05.prod.outlook.com> <B5A72885-678A-442A-86D7-D710D2324A28@apple.com> <2CF4CB03E2AA464BA0982EC92A02CE2509FBBF5E@BY2PRD0512MB653.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983180B8722@XCH-BLV-504.nw.nos.boeing.com> <2CF4CB03E2AA464BA0982EC92A02CE2509FBC675@BY2PRD0512MB653.namprd05.prod.outlook.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2509FBC675@BY2PRD0512MB653.namprd05.prod.outlook.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: Thu, 11 Jul 2013 16:41:57 -0000

Hi Ron,

> -----Original Message-----
> From: Ronald Bonica [mailto:rbonica@juniper.net]
> Sent: Thursday, July 11, 2013 6:50 AM
> To: Templin, Fred L; james woodyatt; ipv6@ietf.org
> Subject: RE: Meta-issues: On the deprecation of the fragmentation
> function
> 
> Yes, I am talking about IPv6 fragmentation.

OK, but if you want to deprecate that you need to replace it
with something else like SEAL.

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

>                      Ron
> 
> > -----Original Message-----
> > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > Sent: Wednesday, July 10, 2013 3:56 PM
> > To: Ronald Bonica; james woodyatt; ipv6@ietf.org
> > Subject: RE: Meta-issues: On the deprecation of the fragmentation
> > function
> >
> > Hi Ron,
> >
> > > -----Original Message-----
> > > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On
> Behalf
> > > Of Ronald Bonica
> > > Sent: Wednesday, July 10, 2013 12:22 PM
> > > To: james woodyatt; ipv6@ietf.org
> > > Subject: RE: Meta-issues: On the deprecation of the fragmentation
> > > function
> > >
> > > Hi James,
> > >
> > > If ICMPv6 PTB messages are unreliable, fragmentation breaks just as
> > > badly as PMTUD.
> >
> > I'm trying to understand that, but maybe you are talking about IP
> > fragmentation? SEAL fragmentation is a different thing, and can be
> used
> > in place of IP fragmentation.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> > > At the risk of going off-topic, please take a look at draft-bonica-
> > > intarea-gre-mtu-02.
> > >
> > >                                                  Ron
> > >
> > >
> > > > -----Original Message-----
> > > > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On
> > Behalf
> > > Of
> > > > james woodyatt
> > > > Sent: Wednesday, July 10, 2013 2:23 PM
> > > > To: ipv6@ietf.org
> > > > Subject: Re: Meta-issues: On the deprecation of the fragmentation
> > > > function
> > > >
> > > > On Jul 10, 2013, at 08:49 , Ronald Bonica <rbonica@juniper.net>
> > > wrote:
> > > > > [...]
> > > > > Probably, the best alternative is for the tunnel ingress router
> > to
> > > > tunnel ingress router to discover the PMTU to the egress. When
> the
> > > > tunnel ingress router receives a packet that is so large that it
> > > cannot
> > > > be forwarded through the tunnel, it discards the packet and sends
> > an
> > > > ICMP PTB to the packet's originator. The packet's originator then
> > > > modifies its sending behavior based upon its new estimate of the
> > > > PMTU associated with the destination.
> > > > > [...]
> > > >
> > > > ICMPv6 packet too big errors are unreliable on the real-world
> > > Internet.
> > > >
> > > > I hate to sound like a broken record, but I will: I look forward
> to
> > > > reviewing a proposal to update to Generic Packet Tunneling in
> IPv6
> > > [RFC
> > > > 2473] for implementing tunnel path MTU discovery at the
> > > > encapsulation layer [c.f. RFC 4821].
> > > >
> > > >
> > > > --
> > > > james woodyatt <jhw@apple.com>
> > > > core os networking
> > > >
> > > > -----------------------------------------------------------------
> --
> > -
> > > > IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> > > > Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > > > -----------------------------------------------------------------
> --
> > -
> > > >
> > >
> > >
> > >
> > > -------------------------------------------------------------------
> -
> > > IETF IPv6 working group mailing list
> > > ipv6@ietf.org
> > > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > > -------------------------------------------------------------------
> -
> >
> 
>