From: Pavel Machek <pavel@suse.cz>
To: "James A. Sutherland" <jas88@cam.ac.uk>, Andi Kleen <ak@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <andrewm@uow.edu.au>,
Oliver Xymoron <oxymoron@waste.org>,
barryn@pobox.com, linux-kernel@vger.kernel.org,
jamal <hadi@cyberus.ca>
Subject: Re: [PATCH] document ECN in 2.4 Configure.help
Date: Fri, 10 Nov 2000 15:58:00 +0100 [thread overview]
Message-ID: <20001110155800.B33@bug.ucw.cz> (raw)
In-Reply-To: <3A068C00.272BD5D2@uow.edu.au> <E13sk36-00066o-00@the-village.bc.nu> <20001106121153.A14104@gruyere.muc.suse.de> <00110613333600.01541@dax.joh.cam.ac.uk>
In-Reply-To: <00110613333600.01541@dax.joh.cam.ac.uk>; from James A. Sutherland on Mon, Nov 06, 2000 at 01:31:23PM +0000
Hi!
> > > > 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
> > >
> > > Now that is nice. The end user perceived effect is that folks with faulty
> > > firewalls have horrible slow web sites with a 3 or 4 second wait for each
> > > page. The perfect incentive. If only someone could do the same to path mtu
> > > discovery incompetents.
> >
> > And it penalizes good guys.
> > If the host cannot answer to the first SYN for some legitimate reason
> > then it'll never be able to use ECN.
>
> It could be a good idea to retry as normal with ECN set; iff that fails
> (so the user would normally see an error connecting) try again with
> ECN clear. This way, ECN-capable hosts will only see non-ECN
> connections under circumstances where the connection would
> otherwise have failed completely.
Hmm, so you want to wait 5 minutes for your TCP connection? TCP
retries for _long_ time.
I do not think that's such a good idea.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
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-10 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 6:15 [PATCH] document ECN in 2.4 Configure.help 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
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 [this message]
2000-11-06 13:08 ` Gregory Maxwell
-- strict thread matches above, loose matches on Subject: below --
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=20001110155800.B33@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=barryn@pobox.com \
--cc=hadi@cyberus.ca \
--cc=jas88@cam.ac.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.