From: "John Heffner" <johnwheffner@gmail.com>
To: "David Newall" <davidn@davidnewall.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Dave Hudson" <linux-kernel@blueteddy.net>,
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
"Mikael Abrahamsson" <swmike@swm.pp.se>,
"David Miller" <davem@davemloft.net>,
daniel.blueman@gmail.com, LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
linux-net@vger.kernel.org
Subject: Re: time for TCP ECN defaulting to on?
Date: Fri, 7 Nov 2008 10:38:26 -0800 [thread overview]
Message-ID: <1e41a3230811071038p58a55cc6g9103b891ca15a1df@mail.gmail.com> (raw)
In-Reply-To: <491454A3.1040802@davidnewall.com>
The IETF has provided a spec, and additional documents on deployment
issues. They have provided all the guidance they are going to. It's
now up to implementers to weigh the trade-offs.
My own observations and opinions, for what they're worth:
Turning on ECN doesn't hurt as much as it used to. Back in the early
'00s, there were a lot of devices sold especially to financial
institutions to "protect" their web sites. These devices dropped any
packets with (previously) reserved header bits set, because some
people used these as a covert information channel. I believe these
devices are not as common as they once were, but there are still a few
big sites that black hole these packets. (I know that southwest.com
is still an offender.)
I have not actually heard of any issues with consumer-grade stuff, but
that may be because ECN has been disabled by default for so long.
Almost no network operators turn on ECN marking in their routers. In
fact, almost none care to do any sort of AQM. The practical benefits
of ECN are still somewhat unclear for most people. For example, it
can help with latency-sensitive applications, but mostly requires a
big queue to work well, so doesn't help as much as you would hope.
There are some interesting ideas on how to better use ECN information,
but these are mostly still research.
ECN black hole detection is pretty simple, and I don't see much reason
not to do it.
-John
On Fri, Nov 7, 2008 at 6:45 AM, David Newall <davidn@davidnewall.com> wrote:
> Isn't this a question for the IETF to answer? Are they saying turn on
> ECN now?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-11-07 18:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 14:32 Daniel J Blueman
2008-11-04 16:16 ` Dave Hudson
2008-11-04 22:52 ` David Miller
2008-11-05 1:16 ` Michael Chan
2008-11-05 5:58 ` David Miller
2008-11-05 6:31 ` Michael Chan
2008-11-05 7:29 ` David Miller
2008-11-16 9:13 ` Herbert Xu
2008-11-16 9:24 ` David Miller
2008-11-05 22:20 ` Mikael Abrahamsson
2008-11-05 23:10 ` David Miller
2008-11-07 4:46 ` Mikael Abrahamsson
2008-11-07 4:49 ` David Miller
2008-11-07 7:53 ` Ilpo Järvinen
2008-11-07 8:11 ` Mikael Abrahamsson
2008-11-07 9:12 ` Bjørn Mork
2008-11-07 11:16 ` Mikael Abrahamsson
2008-11-07 11:28 ` Ilpo Järvinen
2008-11-07 11:38 ` Mikael Abrahamsson
2008-11-07 12:22 ` Ilpo Järvinen
2008-11-07 13:43 ` Daniel J Blueman
2008-11-07 14:30 ` Ilpo Järvinen
2008-11-07 11:18 ` Dave Hudson
2008-11-07 14:29 ` Alan Cox
2008-11-07 14:45 ` David Newall
2008-11-07 15:07 ` Rémi Denis-Courmont
2008-11-07 18:38 ` John Heffner [this message]
2008-11-07 14:33 ` Andi Kleen
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=1e41a3230811071038p58a55cc6g9103b891ca15a1df@mail.gmail.com \
--to=johnwheffner@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daniel.blueman@gmail.com \
--cc=davem@davemloft.net \
--cc=davidn@davidnewall.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@blueteddy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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®