From: Mika Liljeberg <mika.liljeberg@welho.com>
To: John Bradford <john@grabjohn.com>
Cc: 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 23:43:58 +0200 [thread overview]
Message-ID: <1045863838.22625.121.camel@devil> (raw)
In-Reply-To: <200302212040.h1LKejY3001679@81-2-122-30.bradfords.org.uk>
On Fri, 2003-02-21 at 22:40, John Bradford wrote:
> > Supporting this would make using ECN a lot less painful - currently, if
> > I want to use ECN by default, I get to turn it off anytime I find an
> > ECN-hostile site that I'd like to communicate with.
>
> Linux shouldn't encourage the use of equipment that violates RFCs, in
> this case, RFC 739.
>
> The correct way to deal with it, is to contact the maintainers of the
> site, and ask them to fix the non conforming equipment.
That's right. Unfortunately, the way most people *will* deal with it is
by turning ECN off permanently and forgetting about it. That won't help
ECN become widely adopted.
MikaL
next prev parent reply other threads:[~2003-02-21 21:33 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
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 [this message]
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=1045863838.22625.121.camel@devil \
--to=mika.liljeberg@welho.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=john@grabjohn.com \
--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