From: Andrew Morton <andrewm@uow.edu.au>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: barryn@pobox.com, linux-kernel@vger.kernel.org, jamal <hadi@cyberus.ca>
Subject: Re: [PATCH] document ECN in 2.4 Configure.help
Date: Mon, 06 Nov 2000 21:46:24 +1100 [thread overview]
Message-ID: <3A068C00.272BD5D2@uow.edu.au> (raw)
In-Reply-To: <200011060615.WAA05490@cx518206-b.irvn1.occa.home.com> <Pine.LNX.4.10.10011060113240.8248-100000@waste.org>
Oliver Xymoron wrote:
>
> I'm still not sure why it's been decided not to do fallback or how this
> whole situation is any different from path MTU discovery.
It has:
"Changes to make to the ECN RFC before it goes to proposed standard:
* If the TCP host receives no response to a SYN packet sent
with the TCP ECN_ECHO and CWR flags set, to indicate
ECN-capability, then the sender should send its second
SYN packet without these flags set. This is because
there are several deployed TCP implementations that
don't respond to SYN packets with these ECN-related flags set"
http://www.aciri.org/floyd/ecn.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-06 10:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 6:15 Barry K. Nathan
2000-11-06 7:03 ` David S. Miller
2000-11-06 12:16 ` Dominik Kubla
2000-11-06 7:34 ` Oliver Xymoron
2000-11-06 7:30 ` David S. Miller
2000-11-06 8:02 ` Oliver Xymoron
2000-11-06 10:46 ` Andrew Morton [this message]
2000-11-06 11:02 ` Alan Cox
2000-11-06 11:11 ` Andi Kleen
2000-11-06 13:02 ` jamal
2000-11-06 13:31 ` James A. Sutherland
2000-11-10 14:58 ` Pavel Machek
2000-11-06 13:08 ` Gregory Maxwell
2000-11-07 2:38 Bernd Eckenfels
2000-11-07 3:34 ` David S. Miller
2000-11-10 22:00 ` Werner Almesberger
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=3A068C00.272BD5D2@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=barryn@pobox.com \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.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®