Re: How to use an IP-header bit for Path MTU discovery.

Philippe Prindeville <philipp@Gipsi.Gipsi.Fr> Tue, 20 February 1990 01:22 UTC

Received: from decwrl.dec.com by acetes.pa.dec.com (5.54.5/4.7.34) id AA17457; Mon, 19 Feb 90 17:22:25 PST
Received: by decwrl.dec.com; id AA20179; Mon, 19 Feb 90 17:22:19 -0800
Received: from [192.33.166.11] by inria.inria.fr (5.61+/89.0.8) via Fnet-EUnet id AA25074; Tue, 20 Feb 90 02:21:55 +0100 (MET)
Received: by gipsi.Gipsi.Fr (4.12/4.8) id AA23377; Tue, 20 Feb 90 02:22:40 -0100 (MET)
Date: Tue, 20 Feb 90 02:22:40 -0100
From: Philippe Prindeville <philipp@Gipsi.Gipsi.Fr>
Message-Id: <9002200122.AA23377@gipsi.Gipsi.Fr>
X-Phone: +33 1 30 60 75 25 / +33 1 47 34 42 74
To: JMWOBUS%SUVM.BITNET@cornellc.cit.cornell.edu
Subject: Re: How to use an IP-header bit for Path MTU discovery.
Cc: mtudwg

If the host doesn't implement this bit, then what is to stop
its peer from negotiating down to 28 octet packets?  Keep in
mind the scheme should not assume the minimum MTU you will
ever see is 576 octets (eg. satellite)...

-Philip