From: Sebastian Moeller <moeller0@gmx.de>
To: Rich Brown <richb.hanover@gmail.com>
Cc: Rich Brown via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Comcast & L4S
Date: Fri, 31 Jan 2025 14:27:39 +0100 [thread overview]
Message-ID: <F7984D1A-10A8-4CF3-B883-5F1B77B75665@gmx.de> (raw)
In-Reply-To: <48F77C27-0E57-4F96-9BD8-238CC93342F8@gmail.com>
Hi Rich,
> On 31. Jan 2025, at 14:20, Rich Brown via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> Google Alerts sent me this: https://www.webpronews.com/comcasts-latency-leap-a-game-changer-in-network-performance/
>
> Key quote: "Compatibility and Ecosystem: For L4S to have a significant impact, it requires an ecosystem where both the network infrastructure and the end-user devices support the standard..."
>
> Can anyone spell "boil the ocean"? :-)
>
> Or am I missing someting?
Well, the whole safety mechanisms in L4$ are laughably inadequate... this "design" essentially exposes a priority scheduler* without meaningful admission control to the open internet. This is so optimistically naive that it almost is funny again. I wish all the effort and hard work to make L4$ happen, would have been put in a reasonable design... but at least I learned one of the IETF's failure modes, and that is at least something valuable ;)
*) Just because something is not a strict preempting priority scheduler does not make it a good idea to expose it blindly... a conditional priority scheduler with e.g. L4$' weight share of 10:1 already can do a lot of harm.
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2025-01-31 13:27 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 [this message]
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
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=F7984D1A-10A8-4CF3-B883-5F1B77B75665@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.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