From: "David S. Miller" <davem@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC3168, section 6.1.1.1 - ECN and retransmit of SYN
Date: Fri, 21 Feb 2003 22:46:44 -0800 (PST) [thread overview]
Message-ID: <20030221.224644.118785184.davem@redhat.com> (raw)
In-Reply-To: <200302220048.h1M0mjCu020837@turing-police.cc.vt.edu>
From: Valdis.Kletnieks@vt.edu
Date: Fri, 21 Feb 2003 19:48:45 -0500
2) Temporary queueing congestion causes your *first* SYN to be dropped
on the floor. So if you send a second without ECN, you really can't
tell if it worked because of the second SYN working Just Because, or
because ECN was turned off. On the other hand, you get the same
connection as if you had done ECN-off to begin with (just 1 transmit
later).
This is totally broken behavior. Features don't get turned off
just because of a temporary queue overflow at some intermediate
router.
This is why the workarounds are broken by design. This kind of
behavior is totally anti- the most basic principles of how the
internet works.
next prev parent reply other threads:[~2003-02-22 6:52 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 ` RFC3168, section 6.1.1.1 - ECN and retransmit of SYN 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
2003-02-22 0:48 ` Valdis.Kletnieks
2003-02-22 6:46 ` David S. Miller [this message]
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=20030221.224644.118785184.davem@redhat.com \
--to=davem@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@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