General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	 "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] AQM & Net Neutrality
Date: Fri, 28 May 2021 15:28:08 -0700	[thread overview]
Message-ID: <CALQXh-N8hCHov=2tiAkn9S8t209ZCoSPjYEzr6JOfXOP6rDOPg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4ZJOi=CTmsRzDv-S_R=YzHZd9tDWXyNuU1LUfQW-peng@mail.gmail.com>

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

I think one of the big advantages that AQM has is that it doesn't know, or
care, who the flow is.  It can't, itself, violate NN concerns because it
has no knowledge with which to do so.

Instead, it punishes the greed flows that try to use more than their fair
share of the available bandwidth.  It doesn't really favor one protocol, or
provider, or site, or anything else, because it's not aware of them, as
such.  Instead it just stops the kid that's trying to take all the candy
from the candy bowl, to make sure there's enough for everyone else in line.

The working could perhaps be softened from "punished", perhaps, depending
on the audience.

"Everyone gets an equal slice, up to their fill" is another way of looking
at it, I think.

On Wed, May 26, 2021 at 11:36 AM Dave Taht <dave.taht@gmail.com> wrote:

> oops, wrong link for the that plea to both sides of the debate. The
> correct link was:
>
> http://blog.cerowrt.org/post/net_neutrality_customers/
>
> On Wed, May 26, 2021 at 11:32 AM Dave Taht <dave.taht@gmail.com> wrote:
> >
> > I made the most articulate pleas I could to both sides of the debate on
> this:
> >
> >
> https://blog.apnic.net/2020/01/22/bufferbloat-may-be-solved-but-its-not-over-yet/
> >
> > I do think that now that the scandal here has reached a peak:
> > https://ag.ny.gov/sites/default/files/oag-fakecommentsreport.pdf
> >
> > that perhaps an honest appraisal of both AQM and fq+aqm technologies can
> be had
> > in public, again. I'd be willing to reach across the isle on this, and
> > patiently explain stuff to lawmakers where their thinking is
> > incorrect, in order to finally fix bufferbloat.
>
>
>
> --
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>
> Dave Täht CTO, TekLibre, LLC
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

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

  reply	other threads:[~2021-05-28 22:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 13:09 Livingood, Jason
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 [this message]
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='CALQXh-N8hCHov=2tiAkn9S8t209ZCoSPjYEzr6JOfXOP6rDOPg@mail.gmail.com' \
    --to=woody77@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dave.taht@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