Subject: Re: MSS doesn't honour route MTU
To: Jason Thorpe <thorpej@shagadelic.org>
From: Kentaro A. Kurahone <kurahone@sigusr1.org>
List: tech-net
Date: 06/16/2006 09:20:28
--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 15, 2006 at 03:59:39PM -0700, Jason Thorpe wrote:
> On Jun 8, 2006, at 11:23 AM, Mihai CHELARU wrote:
> >----- Original Message ----- From: "Quentin Garnier" =20
> ><cube@cubidou.net>
> >To: "Mihai CHELARU" <kefren@netbsd.ro>
> >Cc: <tech-net@netbsd.org>
> >Sent: Thursday, June 08, 2006 9:11 PM
> >Subject: Re: MSS doesn't honour route MTU
> >
> >>Not unless you set net.inet.tcp.mss_ifmtu to 1.
> >
> >No, it's the same:
>=20
> Which is correct.  The MSS is independent of the MTU.  The MSS is a =20
> value advertised to the peer that says "this is the maximum segment =20
> size I am willing to receive".

That's technically true.  However, RFC 1191 Section 3.1 suggests that
the MSS that's sent be derived from the MTU because it "may dissuade a
broken peer from sending enormous datagrams".  Also they say to use=20
"the maximum MTU over its connected networks, for a multi-homed host"
when doing the math.

--=20
Kentaro A. Kurahone
SIGUSR1 Research and Development

--BOKacYhQ+x31HxR3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iQIVAwUBRJJ322fp+SLSG+tuAQKKHg//W629n/jPQUn4AOhFZ+tLuUPblowd7/js
zcScqqe21Miocud6y604HBdoYCK7Qq7rJn+f6J1Y/gN2Wd2iTTFIbQj7c7Q832ah
lxVIQRl/rHeA6Jth8Fk9EfOHugG9arLpv/VLuE72hOY3bBIxSJqqyfIjEtmsmjzv
LSsnw+3d8BwMSbJy8zKN+4z4A1nh8CqSJ5q8nJ9jQj/2QvVjtkHmPB0fauTNEIqb
TAso8gS1GBHVZuPFFnoMdkgBWn0hTgr9CWq9HRTNU0AauAanFSHPtvadGsu6CXUq
fNWLxddD1vYME7deZ7C6qVns1vZGW/tkTLEKkOjXLNDgqWLOXHxIdn+i4vuEHwET
YTQjqs+7AxpPMaCExT1yAbglAM2Diao+ZV8ZcP0U0f+kWPUEzRLaK/ahWqalPKuv
qn9ymDZMQbhLUxDa3wXHGz6iahQkhMuZGO1pHf9xE+7vcfe2GU8NGX9JOUy017u+
4Ra7T7keqnH4JdYB5dBmFDQhzZlx4OHMeIRcklf3rDypUt4MsjXMWHmiLdTASKMK
QhDQ22EcQKzN9l7AoS3HTYNXabMYs9OhXtr3lL3WNfh+UZzAAVf0Ob18LjPTrhd+
8U7CZCg4n5hLKJocC7JgL4vyr4kZiIshEPJ3zb6xOZOQoFa+peny1TeX1ypzfvGu
3GYV8LWrFoE=
=BGMa
-----END PGP SIGNATURE-----

--BOKacYhQ+x31HxR3--