From: "Holland, Jake" <jholland@akamai.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Steven Blake <slblake@petri-meat.com>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] IETF 110 quick summary
Date: Tue, 9 Mar 2021 19:27:51 +0000 [thread overview]
Message-ID: <DF129E33-301C-48F6-BF6E-1EE074D8BC89@akamai.com> (raw)
In-Reply-To: <B42B2343-89F4-4C08-AC60-A0580E846B8B@gmail.com>
Sorry Jonathan, I think I didn't convey some context properly...
On 3/9/21, 11:09 AM, "Jonathan Morton" <chromatix99@gmail.com> wrote:
>> On 9 Mar, 2021, at 8:44 pm, Holland, Jake <jholland@akamai.com> wrote:
>>
>> …classic ECN traffic will not respond as quickly as L4S…
>
>I know it wasn't you making this claim, Jake, but I have to point out that it's completely false. Classic ECN transports actually respond *more* quickly to a CE mark than L4S transports.
Here I meant to talk about an SCE-style low-congestion signal (in
either 1->0 or 0->1 direction), which would be ignored by a classic
endpoint but which a high-fidelity endpoint would respond to.
So I'm not referring to a CE mark here, but rather an SCE mark, as
I thought Steve was proposing with this bit:
>> Maybe that is an argument that you can throw at them: if it is safe to
>> ignore classic ECN, might as well move straight to SCE with non-ECT
>> traffic shunted off to a separate queue(s).
Sorry for any confusion there, I'm not in favor of talking past each
other and I think we probably agree here if I've understood correctly.
What I was trying to say is that an SCE response (specifically
including an L4S-using-SCE response, though I think you had some
intriguing alternate ideas to reduce the effect) would be faster
than a classic response that ignores SCE and waits for a CE.
I do agree with your explanation that a classic CC responds faster to
a CE mark than TCP Prague, that's just not what I was trying to talk
about.
-Jake
next prev parent reply other threads:[~2021-03-09 19:27 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 [this message]
2021-03-09 19:42 ` Jonathan Morton
2021-03-09 8:43 ` Pete Heist
2021-03-09 15:57 ` Holland, Jake
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=DF129E33-301C-48F6-BF6E-1EE074D8BC89@akamai.com \
--to=jholland@akamai.com \
--cc=chromatix99@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=slblake@petri-meat.com \
/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