From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id DBF2C3B2A4; Sat, 31 Jul 2021 15:26:59 -0400 (EDT) Received: by mail-ed1-x52f.google.com with SMTP id y7so16254723eda.5; Sat, 31 Jul 2021 12:26:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SsruH6Z1bhK2O2I4YnLhJehDxPFkUH5of3cavbK2y80=; b=VJsQPFrr+yc9GnJrV9djvxLefO4UjKsvReB6j5TwZNv/OVsVj1MsNoPuEoBVFa75Rs WozJy87weq3NBvDlMH+eh2O0m3JNlR1B9h6ZwLq0aqVWUBqbJek9ozzxIdKPvI+/6T6E s/rSHBW67yrOdpIKExNNNEqXaapamPJ3GtmvAorhz4KHsSzQmyxF+UoHTHZXh7ZNOY4P g84bRT2X5As3FXjlnCJAK6RPYrnIx1ILAYe0CJpp4DraTWiGbMUcwoB+dRKBO8NmJMDe TfGPBuHp31H+APSjm/04FDTA0uZu2qtaCqqpzRSCOvTrOvugA8pfHcjmBEJo+C/4ybkH F8GQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SsruH6Z1bhK2O2I4YnLhJehDxPFkUH5of3cavbK2y80=; b=IPefkFNwbA0UotiiC+zf3qjBq2ylRkykmTXb+5b24Sl0LvyrOwhSQc835Gdx4xUoJR JkYmrSCGOVS0CFQ8TS7PDjSaBMMDvCwx7+HmFuYNeNpba/iyi4qIb4o8ydPqeFD7s0cp BWt/Pje+sZTUSv/ih01PRMLcql19QhGCrqFrsc42UauWsCTeZuZr/Q+mCCRUXXuADX2v aRnD/fXmz/OpxOKrpxX7V5X28+UvYkTNZwJdsEpkTHE7nX5Pde5qZphth6QjX81Zpnh4 R+1h0KAkWwL2k0FwSE46oCsGvmBznsfbyHUr6zUeobXJCJXCcJ434OfH3SQWKoSTh5t9 CHxQ== X-Gm-Message-State: AOAM53113EBIhKm0AIut29EYemQPPoSfndIxiYgA02DdSx4zCh0rNQz4 Z+x2gJ6sQcbqTt82jHEVN1ORHDaT40DlAvHUvwm5WL0i X-Google-Smtp-Source: ABdhPJy84tzd9wCh/s1BbBSV+ofcrpro68+y4srI3p3n/cAKta7hra91PepJAdf+spIth7Ru4yTBty+yWcrB8Nnqp9Q= X-Received: by 2002:a05:6402:31a4:: with SMTP id dj4mr10336068edb.350.1627759618795; Sat, 31 Jul 2021 12:26:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aaron Wood Date: Sat, 31 Jul 2021 12:26:47 -0700 Message-ID: To: Simon Barber Cc: "Livingood, Jason" , "starlink@lists.bufferbloat.net" , bloat Content-Type: multipart/alternative; boundary="000000000000dbabc705c87051f9" X-Mailman-Approved-At: Sat, 07 Aug 2021 14:21:51 -0400 Subject: Re: [Starlink] [Bloat] Of interest: Comcast AQM Paper X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jul 2021 19:27:00 -0000 --000000000000dbabc705c87051f9 Content-Type: text/plain; charset="UTF-8" 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 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 > --000000000000dbabc705c87051f9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If we see that AQM appears to be not functioning as expect= ed for upstream connections on DOCSIS3.1, what's the right avenue for g= etting that resolved? =C2=A0(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> w= rote:
Awesome to hear that you are turning this o= n 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.buffe= rbloat.net> wrote:
>
> FYI that I will be presenting a lightning talk at the IRTF MAPRG meeti= ng today at 17:30 ET (https://dat= atracker.ietf.org/meeting/111/materials/agenda-111-maprg). The talk lin= ks 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 wo= rking latency from around 250 ms to between 15-30 ms, which is actually kin= d 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@list= s.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
--000000000000dbabc705c87051f9--