[190699] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: MTU

daemon@ATHENA.MIT.EDU (Mark Tinka)
Fri Jul 22 08:53:59 2016

X-Original-To: nanog@nanog.org
To: Baldur Norddahl <baldur.norddahl@gmail.com>, nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
Date: Fri, 22 Jul 2016 14:53:51 +0200
In-Reply-To: <CAPkb-7AOoQ4=7cCuqwN96u-q5cBsr6q1aTnQ8sxW83LNqcjb2g@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org



On 22/Jul/16 14:01, Baldur Norddahl wrote:

>
> Obviously I only need to increase my MTU by the size of the GRE header.=
 But
> I am thinking is there any reason not to go all in and ask every peer t=
o go
> to whatever max MTU they can support? My own equipment will do MTU of 9=
600
> bytes.

See the below:

    http://mailman.nanog.org/pipermail/nanog/2016-March/084598.html

You can reliably run Jumbo frames in your own network core, and also to
another network that can guarantee you the same (which would typically
be under some form of commercial, private arrangement like an NNI).

Across the Internet, 1,500 bytes is still safest, simply because that is
pretty much the standard. Trying to achieve Jumbo frames across an
Internet link (which includes links to your upstreams, links to your
peers and links to your customers) is an exercise in pain.

Mark.

home help back first fref pref prev next nref lref last post