From: "William N." <netfilter@riseup.net>
To: netfilter@vger.kernel.org
Subject: Re: Correct way of setting the TCP max segment sizes for IPv4 and IPv6?
Date: Wed, 10 Apr 2024 15:48:51 -0000 [thread overview]
Message-ID: <20240410154851.6a627134@localhost> (raw)
In-Reply-To: <9AE2B9F2-FE7D-440F-A595-F015957ECBFF@slavino.sk>
On Tue, 09 Apr 2024 22:04:41 +0000 Slavko wrote:
> RFC 9293, sect. 3.7.1
By asking "What about the RFC" I didn't mean "Which RFC sets the
numbers". I meant "Why do you use the same MSS for IPv4 and IPv6,
considering the RFC explains they are different?"
> AFAIK main problem of too low MSS is CPU increase,
This is how I understand it too. Wikipedia calls it "protocol
overhead". I don't know if there are other implications though (e.g. OS
fingerprinting or something else).
> using IPv4 limit for both solves corner cases...
How? The two corner cases are different and 1220 is > x2 than 536, i.e.
very far from the "corner" (limit), i.e. it would not improve
efficiency.
next prev parent reply other threads:[~2024-04-10 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 19:24 Correct way of setting the TCP max segment sizes for IPv4 and IPv6? William N.
2024-04-09 18:43 ` Slavko
2024-04-09 19:33 ` William N.
2024-04-09 22:04 ` Slavko
2024-04-10 15:48 ` William N. [this message]
2024-04-10 18:02 ` Slavko
2024-04-10 18:24 ` William N.
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=20240410154851.6a627134@localhost \
--to=netfilter@riseup.net \
--cc=netfilter@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;
as well as URLs for NNTP newsgroup(s).