From: Rich Brown <richb.hanover@gmail.com>
To: Rich Brown via Bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Comcast & L4S
Date: Fri, 31 Jan 2025 08:20:31 -0500 [thread overview]
Message-ID: <48F77C27-0E57-4F96-9BD8-238CC93342F8@gmail.com> (raw)
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?
next reply other threads:[~2025-01-31 13:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 13:20 Rich Brown [this message]
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
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=48F77C27-0E57-4F96-9BD8-238CC93342F8@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.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