Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "dpreed@deepplum.com" <dpreed@deepplum.com>,
	cerowrt-devel@lists.bufferbloat.net,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Invisibility of bufferbloat and its remedies
Date: Mon, 18 Jun 2018 14:14:21 -0700	[thread overview]
Message-ID: <CAA93jw6eJ6GFVEx=uZsvZ27yRjTNDCE7cU_9chc+ZHd6X6U78A@mail.gmail.com> (raw)
In-Reply-To: <978.1529355565@localhost>

From a ton of memes at: https://me.me/t/buffering

"Dear youtube:

I can deal with ads
I can deal with buffer
But when ads buffer, I suffer"

and innumerable others, some NSFW

https://me.me/i/16133421

On Mon, Jun 18, 2018 at 1:59 PM, Michael Richardson <mcr@sandelman.ca> wrote:
>
> dpreed@deepplum.com <dpreed@deepplum.com> wrote:
>     > I blame IETF members, individually and collectively. If ietf exists for
>     > any reason other than as a boondoggle for world travel, it's for
>     > resolving issues like this one.
>
> Slightly fair.
>
> A thing that I tried to get ISOC's "deploy360" to do was to create a wall of
> shame on bufferbloat five or eight years ago.  It was before the AQM WG did
> any work, I think.  I wanted ISOC to collect the data, because I wanted it
> visible at the CTO level.
>
> At the very very least, I wanted a series of curated links to statements from
> various equipment vendors about the problem.
> I.e. www.example.com/bufferbloat.html for example in
> {cisco,juniper,huawei,calix,...}
>
> I asked many of my IETF contacts at these places if they knew who at their
> company was dealing with it.  I also asked salespeople that I dealt with,
> hoping to put pressure the other way.  I got nowhere.
>
> I wanted, at the very least, to get them to acknowledge that there was a
> problem, even if they didn't have an estimate on a solution, at least I could
> point the salesperson at the page on their site, and say, "I'll buy when you
> get me a delivery date".
> A major client of mine lost three large (VoIP) customers because of hidden
> bufferbloat in Bell Canada's LAN extension service... which "never lost any
> packets", the sales people explained.  It was at a time when we
> weren't quite using the term bufferbloat, and we didn't quite know how to
> measure it in convincing ways.
>
> I still think that this is a good idea.
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>
>



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

      reply	other threads:[~2018-06-18 21:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 16:26 dpreed
2018-06-18 19:07 ` Dave Taht
2018-06-18 22:43   ` dpreed
2018-06-18 23:17     ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2018-06-19  2:21       ` dpreed
2018-06-19  1:46     ` [Cerowrt-devel] " Dave Taht
2018-06-19 19:33       ` Dave Taht
2018-06-19 19:45         ` dpreed
2018-06-19 20:34       ` valdis.kletnieks
2018-06-19 23:32         ` Sebastian Moeller
2018-06-20  6:56           ` [Cerowrt-devel] (no subject) Sebastian Moeller
2018-06-19 23:41         ` [Cerowrt-devel] Invisibility of bufferbloat and its remedies Jonathan Morton
2018-06-19 23:47           ` [Cerowrt-devel] [Bloat] " Sebastian Moeller
2018-06-20  7:12           ` Kevin Darbyshire-Bryant
2018-06-20  8:07             ` Sebastian Moeller
2018-06-20  9:15               ` Kevin Darbyshire-Bryant
2018-06-20  9:34                 ` Sebastian Moeller
2018-06-18 20:59 ` [Cerowrt-devel] " Michael Richardson
2018-06-18 21:14   ` Dave Taht [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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw6eJ6GFVEx=uZsvZ27yRjTNDCE7cU_9chc+ZHd6X6U78A@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --cc=mcr@sandelman.ca \
    /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