Re: [v6ops] PMTUD forever, was: MTUs on the general Internet

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 08 December 2014 16:23 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A00C01A914B for <v6ops@ietfa.amsl.com>; Mon, 8 Dec 2014 08:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9o3ODEu2WwO for <v6ops@ietfa.amsl.com>; Mon, 8 Dec 2014 08:23:57 -0800 (PST)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8F371A9144 for <v6ops@ietf.org>; Mon, 8 Dec 2014 08:23:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB8GNuoT000396; Mon, 8 Dec 2014 10:23:56 -0600
Received: from XCH-BLV-406.nw.nos.boeing.com (xch-blv-406.nw.nos.boeing.com [130.247.25.162]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB8GNsSl000380 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 8 Dec 2014 10:23:55 -0600
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-BLV-406.nw.nos.boeing.com ([169.254.6.247]) with mapi id 14.03.0210.002; Mon, 8 Dec 2014 08:23:54 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Jeroen Massar <jeroen@massar.ch>, "sthaug@nethelp.no" <sthaug@nethelp.no>
Thread-Topic: [v6ops] PMTUD forever, was: MTUs on the general Internet
Thread-Index: AQHQEJwFpAeu1cDlMEapgQ1gXobqjpyC7YoAgAAEroCAABJggP//uZRwgAMmA/A=
Date: Mon, 08 Dec 2014 16:23:53 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DAE093@XCH-BLV-504.nw.nos.boeing.com>
References: <5481B5C8.6030501@massar.ch> <2134F8430051B64F815C691A62D9831832DAC16A@XCH-BLV-504.nw.nos.boeing.com> <5482E29A.1070802@massar.ch> <20141206.122039.74658588.sthaug@nethelp.no> <5482F5F1.8000907@massar.ch> <2134F8430051B64F815C691A62D9831832DAD225@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832DAD225@XCH-BLV-504.nw.nos.boeing.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
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/4zqyd6-G3OxDAZHZdccm0v_UCGM
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] PMTUD forever, was: MTUs on the general Internet
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 16:23:59 -0000

More on what I said the other day, there are two magic numbers that tunnels
need to concern themselves with: 1280 and 1500. Accommodating all packets
within that size range while placing no explicit upper bound for accommodating
larger packets is what is being proposed. In other words, no MTU clamping.

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


> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Templin, Fred L
> Sent: Saturday, December 06, 2014 8:18 AM
> To: Jeroen Massar; sthaug@nethelp.no
> Cc: v6ops@ietf.org
> Subject: Re: [v6ops] PMTUD forever, was: MTUs on the general Internet
> 
> Hi Jeroen,
> 
> > -----Original Message-----
> > From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Jeroen Massar
> > Sent: Saturday, December 06, 2014 4:26 AM
> > To: sthaug@nethelp.no
> > Cc: v6ops@ietf.org
> > Subject: Re: [v6ops] PMTUD forever, was: MTUs on the general Internet
> >
> > On 2014-12-06 12:20, sthaug@nethelp.no wrote:
> > >>> that should be turned off as soon as possible. That will happen as more
> > >>> and more links set MTUs larger than 1500.
> > >>
> > >> IPv6 should also have been deployed globally as soon as possible...
> > >
> > > Speaking only for myself: We run with a suitable jumbo MTU on most
> > > links *within our AS*. I see no sign of such an increased MTU becoming
> > > more available on peering and transit links.
> >
> > Agreed.
> >
> > IMHO one big reason of which is that there are cases where PMTU does not
> > work 100% and thus there is no real benefit of enabling larger MTUs as
> > it will only give problems (as it is something not well known) and thus
> > higher support cost, than creating faster transfers.
> >
> > Hence, a status quo.
> 
> Yes, the status has been quo for a long time, but we now have an opportunity
> to move beyond that. If tunnels stop clamping the MTU and end hosts start
> using RFC4821 larger MTUs will be possible. The good news is that fixing the
> tunnels and fixing the end hosts can be done independently of one another.
> 
> Thanks - Fred
> fred.l.templin@boeing.com
> 
> > Greets,
> >  Jeroen
> >
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops