From: kuznet@ms2.inr.ac.ru
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: davem@redhat.com (Dave Miller), linux-kernel@vger.kernel.org
Subject: Re: MTU and 2.4.x kernel
Date: Sun, 18 Feb 2001 23:32:57 +0300 (MSK) [thread overview]
Message-ID: <200102182032.XAA28257@ms2.inr.ac.ru> (raw)
In-Reply-To: <E14TTRF-0000Ul-00@the-village.bc.nu> from "Alan Cox" at Feb 15, 1 06:47:31 pm
Hello!
> Please cite an exact RFC reference.
Imagine, I found this reference yet. This is rfc1191, of course. 8)
in the MSS option. The MSS option should be 40 octets less than the
size of the largest datagram the host is able to reassemble (MMS_R,
as defined in [1]); in many cases, this will be the architectural
limit of 65495 (65535 - 40) octets.
Alexey
PS: But:
A host MAY send an MSS value
derived from the MTU of its connected network (the maximum MTU over
its connected networks, for a multi-homed host); this should not
cause problems for PMTU Discovery, and may dissuade a broken peer
from sending enormous datagrams.
Note: At the moment, we see no reason to send an MSS greater
than the maximum MTU of the connected networks, and we
recommend that hosts do not use 65495. It is quite possible
that some IP implementations have sign-bit bugs that would be
tickled by unnecessary use of such a large MSS.
next prev parent reply other threads:[~2001-02-18 20:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 20:39 roger
2001-02-14 20:51 ` Alan Cox
2001-02-15 18:21 ` kuznet
2001-02-15 18:47 ` Alan Cox
2001-02-15 19:33 ` kuznet
2001-02-15 20:27 ` Alan Cox
2001-02-15 20:41 ` kuznet
2001-02-15 21:01 ` Alan Cox
2001-02-18 19:53 ` kuznet
2001-02-19 1:44 ` Alan Cox
2001-02-19 18:26 ` kuznet
2001-02-19 22:20 ` Rick Jones
2001-02-16 12:54 ` Rik van Riel
2001-02-18 11:26 ` Pierfrancesco Caci
2001-02-16 12:51 ` Rik van Riel
2001-02-18 19:55 ` kuznet
2001-02-18 9:39 ` David S. Miller
2001-02-18 20:17 ` kuznet
2001-02-18 20:32 ` kuznet [this message]
2001-02-15 20:40 ` Rick Jones
2001-02-15 20:54 ` Jordan Mendelson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200102182032.XAA28257@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®