Re: [Bloat] Of interest: Comcast AQM Paper

[Aaron Wood <woody77@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]

If we see that AQM appears to be not functioning as expected for upstream
connections on DOCSIS3.1, what's the right avenue for getting that
resolved?  (and does that only apply to the Comcast-owned, vs.
customer-owned, modems?)

On Sat, Jul 31, 2021 at 10:50 AM Simon Barber <simon@superduper.net> wrote:

> Awesome to hear that you are turning this on both upstream and downstream.
> Do you know if the wifi stacks in your home routers also have AQM?
>
> Simon
>
>
> > On Jul 30, 2021, at 10:28 PM, Livingood, Jason via Bloat <
> bloat@lists.bufferbloat.net> wrote:
> >
> > FYI that I will be presenting a lightning talk at the IRTF MAPRG meeting
> today at 17:30 ET (
> https://datatracker.ietf.org/meeting/111/materials/agenda-111-maprg). The
> talk links to a just-published paper at https://arxiv.org/abs/2107.13968
> (click PDF link in upper right of page) that will likely be of interest to
> these two lists.
> >
> > High-level: turning on AQM in the cable modem (upstream queue) took
> working latency from around 250 ms to between 15-30 ms, which is actually
> kind of cool. ;-) AQM is turned on in all of our CMTSes (downstream queue)
> and in DOCSIS 3.1 modems (upstream queue).
> >
> > Have a nice weekend,
> > Jason
> >
> > _______________________________________________
> > Bloat mailing list
> > Bloat@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

[-- Attachment #2: Type: text/html, Size: 2542 bytes --]