From: Yanping Du <ypdu2001@yahoo.com>
To: netdev@vger.kernel.org
Subject: Will RFC1146 (tcp alternative checksum options) be implemented in Linux tcp stack ?
Date: Mon, 15 Oct 2007 18:15:11 -0700 (PDT) [thread overview]
Message-ID: <887901.30138.qm@web55205.mail.re4.yahoo.com> (raw)
Hi,
We found the standard 16-bit tcp checksum is not
strong enough in some cases. Is there any roadmap on
implementing RFC1146 (tcp alternative checksum
options) in Linux tcp stack ? If yes, how soon will
that be in ?
Please kindly copy reply to my email address as I've
not subscribed the netdev@ mailing list at present.
http://www.faqs.org/rfcs/rfc1146.html
Thanks!
-Yanping
____________________________________________________________________________________
Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.
http://smallbusiness.yahoo.com/webhosting
next reply other threads:[~2007-10-16 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 1:15 Yanping Du [this message]
2007-10-16 1:57 ` Will RFC1146 (tcp alternative checksum options) be implemented in Linux tcp stack ? Ian McDonald
2007-10-16 3:38 ` Stephen Hemminger
2007-10-16 10:28 ` Matti Aarnio
2007-10-17 0:29 ` Andi Kleen
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=887901.30138.qm@web55205.mail.re4.yahoo.com \
--to=ypdu2001@yahoo.com \
--cc=netdev@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).