[157579] in North American Network Operators' Group

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

RE: IP tunnel MTU

daemon@ATHENA.MIT.EDU (Templin, Fred L)
Mon Oct 29 19:03:03 2012

From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: William Herrin <bill@herrin.us>, Ray Soucy <rps@maine.edu>
Date: Mon, 29 Oct 2012 16:02:33 -0700
In-Reply-To: <CAP-guGUeeLG4nQafKjPE4HLDaUy_EiFjFQFD+ho+obWLt2CezQ@mail.gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Hi Bill,

> Maybe something as simple as clearing the don't fragment flag and
> adding a TCP option to report receipt of a fragmented packet along
> with the fragment sizes back to the sender so he can adjust his mss to
> avoid fragmentation.

That is in fact what SEAL is doing, but there is no guarantee
that the size of the largest fragment is going to be an accurate
reflection of the true path MTU. RFC1812 made sure of that when
it more or less gave IPv4 routers permission to fragment packets
pretty much any way they want.

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


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