General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Matt Mathis <mattmathis@google.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] fcc input
Date: Mon, 29 Mar 2021 22:36:10 -0700	[thread overview]
Message-ID: <CAH56bmDg9=Smqq-P-GR3Mu5L+ny_n+9dvuUad-M=xp2+aF+Kag@mail.gmail.com> (raw)
In-Reply-To: <44899809-1b3b-ecea-e0fa-4281111f8f1a@gmail.com>

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

I  encourage you to collectively think about a different strategy for
framing the problem.    Rather than talk about BB, and then forever looping
back and try to explain why it is important to non-network folks, develop a
tool (or a skin for an existing tool)  that estimates the suitability of a
link to carry video conferencing  and gamer traffic, using the
language from those communities (e.g. "lag").

No explanation is needed to tell a gamer why lag is bad.
No explanation is needed to tell a musician why lag is bad for a
distributed ensemble.
Very little explanation is needed to tell a VC user why lag is bad,
since these days everybody has experienced it.

Keep the up front the language at the application layer, but down inside
reveal that the largest culprit is often excess network queueing delay
under load, AKA buffer bloat.

Although a well framed tool could have high impact, you would get even more
bang for your buck to have a semi-standard jitter metric that could be
grafted into any real time application.  The goal would be to connect the
observed (and measured) application lag to the underlying network jitter,
queueing delay and bufferbloat.

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

We must not tolerate intolerance;
       however our response must be carefully measured:
            too strong would be hypocritical and risks spiraling out of
control;
            too weak risks being mistaken for tacit approval.


On Sat, Mar 27, 2021 at 1:54 AM Jan Ceuleers <jan.ceuleers@gmail.com> wrote:

> On 26/03/2021 20:09, Dave Taht wrote:
> > I have often thought hard about trying to explain things better via
> > animations, and on more than one occasion tried to find an animator
> > who could turn this old 8m talk from "people as packets" into "unruly
> > animals as packets".
> >
> > https://www.youtube.com/watch?v=Rb-UnHDw02o&t=1657s
> >
> > But that requires both money and time, and I've usually had neither.
> > Grant money would be nice for a whole string of educational videos,
> > but not being part of the MICA complex has made that difficult. If I
> > ever get caught up on bills, and some other pressing problems, perhaps
> > we could do a kickstarter campaign to get some things animated.
>
> I have often admired Randall Munroe's ability to grasp and satirise
> sometimes quite complex concepts. Perhaps he could be prevailed upon to
> draw a bufferbloat-inspired cartoon? He publishes his work at xkcd.com
> under a Creative Commons license.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

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

      reply	other threads:[~2021-03-30  5:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  4:11 Dave Taht
2021-03-24 19:52 ` Jonathan Foulkes
2021-03-26 16:58   ` Aaron Wood
2021-03-26 19:04     ` Kenneth Porter
     [not found]     ` <A82CBB923160F8F7F5DC395E@172.27.17.193>
2021-03-26 19:09       ` Dave Taht
2021-03-26 19:22         ` Kenneth Porter
     [not found]         ` <5EDB17C519EAF0BFE3755CE4@172.27.17.193>
2021-03-26 19:37           ` Dave Taht
2021-03-27  8:54         ` Jan Ceuleers
2021-03-30  5:36           ` Matt Mathis [this message]

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='CAH56bmDg9=Smqq-P-GR3Mu5L+ny_n+9dvuUad-M=xp2+aF+Kag@mail.gmail.com' \
    --to=mattmathis@google.com \
    --cc=bloat@lists.bufferbloat.net \
    --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