General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Dave Täht" <dave.taht@gmail.com>,
	"David Collier-Brown" <davec-b@rogers.com>,
	bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Comcast & L4S
Date: Sat, 1 Feb 2025 16:51:59 +0200	[thread overview]
Message-ID: <D59FAE71-CB1C-442B-91D6-088AA9D58184@gmail.com> (raw)
In-Reply-To: <9A110AF4-E976-4228-9FA6-92C5C99F611A@gmx.de>

> On 1 Feb, 2025, at 4:33 pm, Sebastian Moeller via Bloat <bloat@lists.bufferbloat.net> wrote:
> 
> …Comcast's use of the Internet Engineering Task Force's Low Latency Low Loss Scalable Throughput (L4S) standards…

That's the tail wagging the dog - but precisely the kind of non-specialist misunderstanding that L4S' hijacking of the IETF process was designed to foster.

It's an EXPERIMENT that the IETF has been BROWBEATEN by Comcast into PERMITTING to occur.  It is NOT a STANDARD, and it was NOT IETF-led.  Every single design suggestion that IETF proposed, to improve coexistence with other schemes that ARE IETF standards, was resisted or outright ignored.

As with NQB, Cake already does essentially what L4S requires, except for default-configured Codel being less than ideal as an AQM for producing congestion signals for a DCTCP-type response.  I have no intention of modifying Cake to *specifically* accommodate L4S in any way.  If their crap doesn't work properly in a standards-compliant environment, that's THEIR problem.

 - Jonathan Morton

  reply	other threads:[~2025-02-01 14:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 13:20 Rich Brown
2025-01-31 13:27 ` Sebastian Moeller
2025-01-31 23:57   ` Dave Taht
2025-02-01  0:40     ` David Collier-Brown
2025-02-01  0:49       ` Dave Taht
2025-02-01 14:33         ` Sebastian Moeller
2025-02-01 14:51           ` Jonathan Morton [this message]
2025-02-01 17:06             ` Sebastian Moeller
2025-02-01 17:26               ` Jonathan Morton
2025-02-01 18:05                 ` Sebastian Moeller
2025-02-02  0:09                   ` Jonathan Morton
2025-02-02 11:39                     ` Sebastian Moeller
2025-02-03 14:04                       ` Jonathan Morton
2025-02-01 13:35     ` Sebastian Moeller

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D59FAE71-CB1C-442B-91D6-088AA9D58184@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=davec-b@rogers.com \
    --cc=moeller0@gmx.de \
    /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