From: "Holland, Jake" <jholland@akamai.com>
To: Pete Heist <pete@heistp.net>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] IETF 110 quick summary
Date: Tue, 9 Mar 2021 15:57:48 +0000 [thread overview]
Message-ID: <745712EB-F92B-462D-A201-A67CCFE0B16C@akamai.com> (raw)
In-Reply-To: <09ec86122a89989aa3fed5ed25a8fb34ce033f30.camel@heistp.net>
On 3/9/21, 12:43 AM, "Pete Heist" <pete@heistp.net> wrote:
> I'm glad to hear that. At least it adds something to your work before,
> from a different vantage point, albeit much smaller. I know that
> studies from entirely disinterested parties would be good too, but that
> might the hard part, they're disinterested! :)
Yeah, sorry I couldn't manage to re-run my scripts successfully yet.
I'm still curious to figure out if there's been any deployment motion,
but the attempts that are easy to try haven't succeeded, and I haven't
had time to refactor it to insist on an answer. (I re-tried a few times,
hoping it was a cluster capacity issue that would sort itself out or that
it would complete if I batched the jobs smaller, but no joy.)
>> I seem to recall a thread in the wake of Apple's ECN enabling about
>> one of the Linux distros considering turning ECN on by default for
>> outbound connections, in which one of them found that it completely
>> wrecked his throughput, and so it got tabled with unfortunately
>> no pcap posted.
>>
>> Any recollection of where that was? I was guessing it might be
>> one of the misbehaviors from the network that Apple encountered.
>
> That is odd and would be good to know about. I enabled ECN on my Linux
> laptop a long time ago and haven't noticed a problem that I'm aware of.
> I wish the distros would reconsider enabling it, unless there are
> active reasons it shouldn't be deployed, but they may now just be in a
> holding pattern on it.
There's apparently a few misbehaving boxes out there, so using ECN from
the wrong network location can leave you messed up, which I thought was
why Apple had the heuristics running to detect pathologies and respond
by turning off ECT for a while. But it's pretty hard to pin down what's
happening (and from where) without a zillion clients running ECN from all
over the world.
Anyway, I thought I remembered Dave posting a link to that thread to one
of the lists (maybe this one?) and commenting in the thread (my vague
recollection was he was asking for a pcap but was told they had already
moved on and couldn't get one easily, or some such).
I also thought I remembered someone in that thread was maybe considering
(or maybe just suggesting) adding something like the apple heuristics,
so I was curious if anything ever happened.
-Jake
next prev parent reply other threads:[~2021-03-09 15:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 23:47 Pete Heist
2021-03-08 23:57 ` Dave Taht
2021-03-09 2:13 ` Holland, Jake
2021-03-09 4:06 ` Steven Blake
2021-03-09 9:57 ` Pete Heist
2021-03-09 13:53 ` Jonathan Morton
2021-03-09 14:27 ` Sebastian Moeller
2021-03-09 14:35 ` Dave Taht
2021-03-09 17:31 ` Steven Blake
2021-03-09 17:50 ` Steven Blake
2021-03-09 18:07 ` Rodney W. Grimes
2021-03-09 18:13 ` Pete Heist
2021-03-09 19:51 ` Holland, Jake
2021-03-09 20:53 ` Pete Heist
2021-03-09 18:44 ` Holland, Jake
2021-03-09 19:09 ` Jonathan Morton
2021-03-09 19:27 ` Holland, Jake
2021-03-09 19:42 ` Jonathan Morton
2021-03-09 8:43 ` Pete Heist
2021-03-09 15:57 ` Holland, Jake [this message]
2021-03-09 11:06 ` Jonathan Morton
2021-03-09 8:21 ` Pete Heist
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
List information: https://lists.bufferbloat.net/postorius/lists/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=745712EB-F92B-462D-A201-A67CCFE0B16C@akamai.com \
--to=jholland@akamai.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=pete@heistp.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