MTU of the Internet?

Mailman List Mirror (Read Only)
1

Jeff Stehman writes...

>
> We recommend that clients who care about interactive response use small
> MTUs, and clients who care about download speed use higher MTUs.

There's an extremely annoying potential gotcha in having clients set
lower MTUs. At least one release of Netscape's web server set the
Don't Fragment bit. In the few cases we've seen, if there was not a
1500 MTU pipe between server and client, the server could be reached,
but no HTML would be downloaded. Usually it's easier to work around
the problem on the client end than convince the server admins they
might want change things on their end.

If the client sets the MTU lower, that becomes the connection MTU and
MTU discovery doesn't take place. The problem only occurs if there is
a router in between (not the client) that has a lower MTU than what the
connection is using, and hence the fragmentation (or discarding if DF
is on) occurs.

There's probably a whole thread due on whether DF should be set or not.
But there really are links that are smaller than 1500, such as SLIP at
1006.

IMHO setting DF should not be allowed where the MTU is greater than 576,
or whatever number today constitutes the "minimum reasonable requirement"
which I would say isn't larger than 1006. Maybe in a few years we can
kiss SLIP bye-bye and make sure everything is 1500.

Netscape's web server is broken. And in more ways than just the DF thing.

But then that begs the question, why 1500? Why not 4000? Or 32000?

2

IMHO setting DF should not be allowed where the MTU is greater than 576,
or whatever number today constitutes the "minimum reasonable requirement"
which I would say isn't larger than 1006. Maybe in a few years we can
kiss SLIP bye-bye and make sure everything is 1500.

Erm... no. The whole point of setting the DF bit is to avoid
fragmentation. Read up on path MTU discovery to see why it is a good
thing. Just because braindead filters cause problems is no reason to
suggest that PMTU discovery is bad. It becomes even more critical in IPv6
where routers don't fragment period, so people had better get used to it.

Trying to force everyone to have the same MTU simply is not practical.
You will always have systems with higher path MTUs that can get a gain
from knowing it and you will always have systems with lower MTUs for
whatever reason.

Netscape's web server is broken. And in more ways than just the DF thing.

It has nothing to do with what web server you are running.