From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Neal Cardwell <ncardwell@google.com>,
Aaron Wood <woody77@gmail.com>,
"starlink\@lists.bufferbloat.net"
<starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] [Bloat] Of interest: Comcast AQM Paper
Date: Sun, 01 Aug 2021 09:13:25 -0400 [thread overview]
Message-ID: <27719.1627823605@localhost> (raw)
In-Reply-To: <CADVnQyk+DnCootU9bOZhX9PS2tAqXDc+wZB4djr6rQTVAcMm-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
Neal Cardwell via Bloat <bloat@lists.bufferbloat.net> wrote:
> On Sat, Jul 31, 2021 at 3:27 PM Aaron Wood <woody77@gmail.com> wrote:
>>
>> 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?)
> FWIW, from the paper it sounds like not all Comcast cable modems
> had/have PIE, which enabled the A/B experiment:
This does bring up an interesting discovery question:
the presences of AQM (whether PIE or FQ_CODEL), and what the settings might
be (for some things need to be tuned), would be something that might be
interested to emit via LLDP.
And/or at a /.well-known URL (accessible via IPv6-LL only).
--
Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2021-08-01 13:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 21:28 [Starlink] " Livingood, Jason
2021-07-31 17:50 ` [Starlink] [Bloat] " Simon Barber
2021-07-31 19:26 ` Aaron Wood
2021-07-31 22:55 ` Neal Cardwell
2021-08-01 13:13 ` Michael Richardson [this message]
2021-08-01 20:20 Livingood, Jason
2021-08-01 21:39 ` Dick Roy
2021-08-04 11:49 ` Jonathan Morton
2021-08-04 12:46 ` Mikael Abrahamsson
2021-08-04 13:03 ` Sebastian Moeller
2021-08-04 13:06 ` Mikael Abrahamsson
2021-08-04 13:43 ` Sebastian Moeller
2021-08-04 18:28 ` Jonathan Morton
2021-08-04 20:44 ` David Lang
2021-08-04 20:51 ` Sebastian Moeller
2021-08-04 18:31 ` Juliusz Chroboczek
2021-08-04 18:58 ` Jonathan Morton
2021-08-04 20:08 ` Jonathan Bennett
2021-08-04 20:18 ` Nathan Owens
2021-08-04 20:46 ` Jonathan Bennett
2021-08-05 0:24 ` Michael Richardson
2021-08-05 15:11 ` Frank Carmickle
2021-08-07 23:59 ` Michael Richardson
2021-08-07 20:31 ` Dave Taht
2021-08-01 20:21 Livingood, Jason
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27719.1627823605@localhost \
--to=mcr+ietf@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=ncardwell@google.com \
--cc=starlink@lists.bufferbloat.net \
--cc=woody77@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