RE: "Deprecate"

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 02 August 2013 14:54 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 B06FB11E8106 for <ipv6@ietfa.amsl.com>; Fri, 2 Aug 2013 07:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.339
X-Spam-Level:
X-Spam-Status: No, score=-6.339 tagged_above=-999 required=5 tests=[AWL=0.260, 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 qoOhkp7rWi44 for <ipv6@ietfa.amsl.com>; Fri, 2 Aug 2013 07:54:25 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id E1A0011E80EC for <ipv6@ietf.org>; Fri, 2 Aug 2013 07:54:24 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r72EsNPc029110 for <ipv6@ietf.org>; Fri, 2 Aug 2013 07:54:24 -0700
Received: from XCH-NWHT-09.nw.nos.boeing.com (xch-nwht-09.nw.nos.boeing.com [130.247.25.115]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r72EsLir029078 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 2 Aug 2013 07:54:22 -0700
Received: from XCH-BLV-401.nw.nos.boeing.com (130.247.25.18) by XCH-NWHT-09.nw.nos.boeing.com (130.247.25.115) with Microsoft SMTP Server (TLS) id 8.3.297.1; Fri, 2 Aug 2013 07:54:21 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-401.nw.nos.boeing.com ([169.254.1.219]) with mapi id 14.02.0328.011; Fri, 2 Aug 2013 07:54:20 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Mark Andrews <marka@isc.org>
Subject: RE: "Deprecate"
Thread-Topic: "Deprecate"
Thread-Index: AQHOjxg6iYfnka6nOUeBop7mpmo4ZpmCAPYQ
Date: Fri, 02 Aug 2013 14:54:20 +0000
Message-ID: <2134F8430051B64F815C691A62D983180DD8C6@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> <51DC77B1.9020206@gmail.com> <DEDA9E45-2839-4D7C-9D86-04360DDE9C1D@gmail.com> <2134F8430051B64F815C691A62D983180DCA04@XCH-BLV-504.nw.nos.boeing.com> <20130802003547.71BB137EE821@drugs.dv.isc.org>
In-Reply-To: <20130802003547.71BB137EE821@drugs.dv.isc.org>
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" <ipv6@ietf.org>, RJ Atkinson <rja.lists@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: Fri, 02 Aug 2013 14:54:34 -0000

Hi Mark,

> -----Original Message-----
> From: Mark Andrews [mailto:marka@isc.org]
> Sent: Thursday, August 01, 2013 5:36 PM
> To: Templin, Fred L
> Cc: RJ Atkinson; ipv6@ietf.org
> Subject: Re: "Deprecate"
> 
> 
> In message <2134F8430051B64F815C691A62D983180DCA04@XCH-BLV-
> 504.nw.nos.boeing.co
> m>, "Templin, Fred L" writes:
> > Hi Ran,
> >
> > > Discussion:
> > >    Deployments using tunnels, whether IP-in-IP, GRE, IPsec tunnel-
> mode,
> > >    or some other IETF specified technology, are NOT going away.
> >
> > Yes, this is the same as I and others have been saying all along.
> >
> > > If the physical MTU is 1280, then the tunnel MTU will be smaller.
> >
> > Not allowed; the tunnel MUST be able to do a minimum 1280.
> >
> > >   Nested tunnels are not unusual and can be difficult to detect
> > >   absent a working PMTUD mechanism (whatever that might be).
> >
> > Agree that nested tunnels are not unusual and are in fact in
> > common widespread deployment. But, there is no need to "detect"
> > them from the source host's perspective as long as they honor
> > the IPv6 1280 minMTU. That means that tunnels MUST be prepared
> > to do a small amount of fragmentation and reassembly when
> > necessary.
> 
> And if we generate appoximately equal sized fragments rather than
> 1280 byte fragments + a runt fragment tunnels would need to fragment
> less often.  Your 1500 byte UDP payloads become 2 x 750 byte fragments
> which can be encapulated multiple times.

Yes, SEAL covers this in earlier document versions. "Approximately equal
length is what it used to say; now it says:

" breaks the inner packet into N non-overlapping segments (where N is
  minimized and each segment is significantly smaller than (MINMTU-HLEN)
  to allow for additional encapsulations in the path)."

but I can modify this to say: "in N approximately equal length
non-overlapping segments" to bring back what I had in earlier
versions.

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


> It doesn't take a lot of math to work out what size to fragment at to
> produce optimal fragment sizes for a given MTU.
> 
> Mark
> 
> > 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
> > --------------------------------------------------------------------
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org