From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: [Bloat] AQM & Net Neutrality
Date: Mon, 24 May 2021 13:09:54 +0000 [thread overview]
Message-ID: <8CA408F6-C8FA-4AAF-908A-B52BDC5030FF@cable.comcast.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
I’m looking for opinions here re bloat-busting techniques like AQM in the context of network neutrality (NN). The worry I have is whether some non-technical people will misunderstand how AQM works & conclude that implementing it may violate NN because it would make interactive traffic perform better than it does today. That is true of course – it’s a design goal of AQM, but non-interactive traffic performs as well as it always has – it is not disadvantaged.
Maybe the worries I have heard just points out the need for more education/awareness about what delay is and why things like AQM are not prioritization/QoS? I appreciate any thoughts.
Jason
[-- Attachment #2: Type: text/html, Size: 2622 bytes --]
next reply other threads:[~2021-05-24 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 13:09 Livingood, Jason [this message]
2021-05-24 14:30 ` Jonathan Morton
2021-05-24 14:51 ` Jonathan Morton
2021-05-24 21:13 ` Michael Richardson
2021-05-24 19:18 ` Stuart Cheshire
2021-05-24 21:23 ` Michael Richardson
2021-05-25 16:03 ` Jonathan Morton
2021-05-26 18:32 ` Dave Taht
2021-05-26 18:36 ` Dave Taht
2021-05-28 22:28 ` Aaron Wood
2021-05-28 23:18 ` Sebastian Moeller
2021-06-03 9:23 ` Holland, Jake
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=8CA408F6-C8FA-4AAF-908A-B52BDC5030FF@cable.comcast.com \
--to=jason_livingood@comcast.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