General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Jim Gettys <jg@freedesktop.org>,
	Daniel Sterling <sterling.daniel@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Re: [EXTERNAL] Re: Re: Consumer CPE with Modern AQM?
Date: Tue, 17 Feb 2026 16:35:59 +0000	[thread overview]
Message-ID: <DM6PR11MB42684E822712CF2012908DA0C76DA@DM6PR11MB4268.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAGhGL2DahVL9CdDeOr6=G3j0p8X+HUXir+-p0D9+2yuW0EgfDg@mail.gmail.com>


> One of the pieces of leverage that a major ISP such as Comcast has is its recommended hardware list, not just the hardware that you guys distribute directly.

Sure - and we did that for all the COAM cable modems years ago. We now have a subset of end users that run their own router, which they have purchased. Some of these are shockingly old. I’m working on an outreach campaign to those users now - with the idea being to offer advice on how to improve latency by replacing device X with a new device from a list at some TBD URL.

The motivation for an ISP is clear - we see complaints from users with these old routers saying service is poor. But their DOCSIS or EPON connection quality is great. The root cause is the router and/or AP - so working to help them understand and address this.

> If Comcast and other major ISP's made it clear to the vendors of home routers and other cpe equipment that they would be penalized explicitly if they failed Wi-Fi bufferbloat or other buffer bloat testing, that is probably the fastest way to get the Wi-Fi side of these CPE devices fixed, or at least reduced to a semi-manageable level.

We already do this for cable modems that connect to and authenticate on the network. AQM is build into every D3.1 CM that ships today - whether we provide it or a user buys it in retail.

But we do not have a way to qualify COAM routers and APs. But I suppose a company may ask how to get on the ‘suggested list’ of routers - in which case it is to implement AQM and/or other latency-reducing technologies. ;-)

JL

  parent reply	other threads:[~2026-02-17 16:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-15 17:42 [Bloat] CAKE-MQ merged to OpenWrt 25.12 today (February 15) Frantisek Borsik
2026-02-16 16:51 ` [Bloat] Consumer CPE with Modern AQM? Livingood, Jason
2026-02-16 17:24   ` [Bloat] " Frantisek Borsik
2026-02-16 17:45   ` Daniel Sterling
2026-02-16 20:10     ` David Collier-Brown
2026-02-17  4:12     ` Jim Gettys
2026-02-17 12:12       ` Jan Ceuleers
2026-02-17 16:35       ` Livingood, Jason [this message]
2026-02-17 16:24     ` [Bloat] Re: [EXTERNAL] " Livingood, Jason
2026-02-17  6:10 ` [Bloat] Re: [Cake] CAKE-MQ merged to OpenWrt 25.12 today (February 15) dave seddon
2026-02-17  6:41   ` Stephen Hemminger
2026-02-17 13:23   ` Toke Høiland-Jørgensen
2026-02-17 14:34     ` [Bloat] Re: [Cake] Re: " Stephen Hemminger
2026-02-17 16:32       ` Toke Høiland-Jørgensen
2026-02-17 16:55         ` Jonas Köppeler
2026-02-20 15:59         ` dave seddon
2026-02-23 10:18           ` Toke Høiland-Jørgensen

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=DM6PR11MB42684E822712CF2012908DA0C76DA@DM6PR11MB4268.namprd11.prod.outlook.com \
    --to=jason_livingood@comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jg@freedesktop.org \
    --cc=sterling.daniel@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