From: Dave Taht <dave.taht@gmail.com>
To: Mel Beckman <mel@beckman.org>
Cc: NANOG <nanog@nanog.org>, "aqm@ietf.org" <aqm@ietf.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Bufferbloat related censorship at Virgin Media
Date: Sun, 1 Mar 2015 16:01:02 -0800 [thread overview]
Message-ID: <CAA93jw4zWms7Toyc=CTENq715Cmc8RU82Q+=ootJ_GYrQGJb1A@mail.gmail.com> (raw)
In-Reply-To: <A665ECE3-FAFA-4624-B78B-1BCF10E94631@beckman.org>
On Sun, Mar 1, 2015 at 3:47 PM, Mel Beckman <mel@beckman.org> wrote:
> Dave,
>
> I appreciate all your work on buffer bloat. It looks like you have done quite a lot of selfless contribution. However, I don't think you're effectively communicating with the people who can change things.
>
> After I read what you said, here is what I would have heard as a service provider:
>
> "I am the smartest person in the room.
I am pretty close to being the smartest person in the room. That said,
people like van jacobson, eric dumazet, tom herbert, jim gettys, eric
raymond, vint cerf, dave reed, fred baker, and many, many others,
smarter than me, have also been banging this drum, politely, and
rationally, to not much effect, for 4+ years now.
google for any of those names and the word "bufferbloat".
> You better listen to me, because if you don't there will be trouble. But you probably won't because you're too stupid. Your customers suffer because you are idiots. Listen to me! This issue is too important for me to be polite, or even coherent. If you can't figure out what I'm saying, do some research and figure it out! Plus, apologize to me! I demand it!"
Oh, banning my ip for *3 links to sane benchmarks and fixes*,
realllllly pushed me over the edge.
> Bees, honey, vinegar, etc.
I have been polite, constructive, and helpful, for four+ years. I have
worked both in the background and foreground with many companies, to
start hopefully, getting bufferbloat fixed across the entire edge of
the internet. It hasn't worked fast enough for my liking, and the last
batch of new products that claimed to fix it, didn't, and the market
is now rife with genuine lies as to whether they did or not.
So, this morning, I tried this. Sorry for the noise on these lists.
Honestly! I totally agree with your assessment of my tone, btw! but I
would rather like the cable industry in particular, to come clean,
with schedules for deployable fixes.
I am off to go fix wifi next, and I do hope that 2+ billion people in
the world - if not the isps, maybe - would like wifi to get better
also, and indeed, I spent the weekend constructively starting to
implement some of the fixes I outlined at the last 802.11 meeting I
attended. That part, on fixing wifi bufferbloat - a much harder
problem than edge bufferbloat - , is a lot of fun! For some info on
what we plan to do there, see:
http://snapon.lab.bufferbloat.net/~d/ieee802.11-sept-17-2014/11-14-1265-00-0wng-More-on-Bufferbloat.pdf
So I took a break from that, reared back, and got some stuff off my chest.
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
next prev parent reply other threads:[~2015-03-02 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 23:28 Dave Taht
2015-03-01 23:47 ` Mel Beckman
2015-03-02 0:01 ` Dave Taht [this message]
2015-03-02 0:08 ` Mel Beckman
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='CAA93jw4zWms7Toyc=CTENq715Cmc8RU82Q+=ootJ_GYrQGJb1A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=mel@beckman.org \
--cc=nanog@nanog.org \
/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