From: Jonathan Morton <chromatix99@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] BBRv3 ecn_low per-route feature and the CE confusion
Date: Tue, 28 Nov 2023 16:03:18 +0200 [thread overview]
Message-ID: <16FCEB18-8C61-4EDB-9C1A-4EEAE266F6FE@gmail.com> (raw)
In-Reply-To: <d97399e7a486fac11c2c750d58017ebba8b37738.camel@heistp.net>
> On 28 Nov, 2023, at 2:57 pm, Pete Heist via Ecn-sane <ecn-sane@lists.bufferbloat.net> wrote:
>
> This isn't a problem with BBR. The problem is, we've started an
> experiment [RFC9331] that redefines the meaning of CE in a way that's
> incompatible with existing RFC3168 middleboxes. This feature in BBR is
> just a reflection of that. CCA developers are now tasked with somehow
> deciding which type of CE they're seeing.
>
> Speaking of ecn "sane", does anyone else see this as not? :) and as a
> problem that needs solving?
Count me in the "not sane" camp, at least. This is exactly the kind of ambiguity that SCE is designed to avoid.
- Jonathan Morton
next prev parent reply other threads:[~2023-11-28 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:57 Pete Heist
2023-11-28 14:03 ` Jonathan Morton [this message]
2023-11-28 15:21 ` Sebastian Moeller
2023-11-28 16:28 ` 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=16FCEB18-8C61-4EDB-9C1A-4EEAE266F6FE@gmail.com \
--to=chromatix99@gmail.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