From: "David S. Miller" <davem@redhat.com>
To: John Bradford <john@grabjohn.com>
Cc: "Zephaniah E\\. Hull" <warp@mercury.d2dc.net>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: RFC3168, section 6.1.1.1 - ECN and retransmit of SYN
Date: 21 Feb 2003 16:47:02 -0800 [thread overview]
Message-ID: <1045874822.25411.3.camel@rth.ninka.net> (raw)
In-Reply-To: <200302212125.h1LLPgxE001759@81-2-122-30.bradfords.org.uk>
On Fri, 2003-02-21 at 13:25, John Bradford wrote:
> What if the first SYN packet, or the response to it is lost, (which is
> more possible on congested links, which is when ECN would be most
> useful), and we disable ECN - then we loose out on functionality we
> could have, and the work around is actually detremental to
> performance. Once 99% of internet hosts support ECN, we could be
> loosing more than we gain.
How do you know this is the reason for the lost SYN? What if other
things caused the SYN to be dropped by some intermediate site?
All the workarounds for ECN blackholes violate the protocol and
cause more problems than they solve.
That is why we refuse to implement them, and this is why the ECN
RFCs mark the "suggested workarounds" as optional not required to
implement.
next prev parent reply other threads:[~2003-02-21 23:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.lnpabmu.5sd1q@ifi.uio.no>
2003-02-21 20:13 ` Valdis.Kletnieks
2003-02-21 20:40 ` John Bradford
2003-02-21 20:53 ` Zephaniah E. Hull
2003-02-21 21:25 ` John Bradford
2003-02-22 0:47 ` David S. Miller [this message]
2003-02-22 0:48 ` Valdis.Kletnieks
2003-02-22 6:46 ` David S. Miller
2003-02-22 18:45 ` Werner Almesberger
2003-02-22 23:26 ` David S. Miller
2003-02-22 10:56 ` John Bradford
2003-02-22 10:47 ` David S. Miller
2003-02-21 21:43 ` Mika Liljeberg
2003-02-21 22:05 ` Valdis.Kletnieks
2003-02-21 22:32 ` Maciej Soltysiak
2003-02-23 4:57 ` Kevin Buhr
2003-02-21 21:37 jordan.breeding
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=1045874822.25411.3.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=warp@mercury.d2dc.net \
/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®