From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "Wes Felter" <wmf@felter.org>,
"Joel Wirāmu Pauling" <joel@aenertia.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fixing bufferbloat: How about an open letter to the web benchmarkers?
Date: Thu, 11 Sep 2014 20:31:40 -0400 (EDT) [thread overview]
Message-ID: <1410481900.628723265@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw7Zy2vwLPcV0cb9O1jj2QU_h6Vj2fHok9fm-X7-ssnStA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2709 bytes --]
I will sign. It would be better if we had an actual demonstration of how to implement a speedtest improvement.
On Thursday, September 11, 2014 12:03pm, "Dave Taht" <dave.taht@gmail.com> said:
> The theme of networks being "engineered for speedtest" has been a
> common thread in nearly every conversation I've had with ISPs and
> vendors using every base technology out there, be it dsl, cable,
> ethernet, or fiber, for the last 4 years. Perhaps, in pursuing better
> code, and RFCs, and the like, we've been going about fixing
> bufferbloat the wrong way.
>
> If Verizon can petition the FCC to change the definition of
> broadband... why can't we petition speedtest to *change their test*?
> Switching to merely reporting the 98th percentile results for ping
> during an upload or download, instead of the baseline ping, would be a
> vast improvement on what happens today, and no doubt we could suggest
> other improvements.
>
> What if we could publish an open letter to the benchmark makers such
> as speedtest, explaining how engineering for their test does *not*
> make for a better internet? The press fallout from that letter, would
> improve some user education, regardless if we could get the tests
> changed or not.
>
> Who here would sign?
>
>
> On Wed, Sep 10, 2014 at 2:54 PM, Joel Wirāmu Pauling
> <joel@aenertia.net> wrote:
> > I have been heavily involved with the UFB (Ultrafast Broadband) PON
> > deployment here in New Zealand.
> >
> > I am not sure how the regulated environment is playing out in Canada
> > (I am moving there in a month so I guess I will find out). But here
> > the GPON architecture is METH based and Layer2 only. Providers (RSP's)
> > are the ones responsible for asking for Handoffer buffer tweaks to the
> > LFC(local fibre companies; the layer 0-2 outfits-) which have mandated
> > targets for Latency (at most 4.5ms) accross their PON Access networks
> > to the Handover port.
> >
> > Most of the time this has been to 'fix' Speedtest.net TCP based
> > results to report whatever Marketed service (100/30 For example) is in
> > everyones favourite site speedtest.net.
> >
> > This has meant at least for the Chorus LFC regions where they use
> > Alcatel-Lucent 7450's as the handover/aggregation switches we have
> > deliberately introduced buffer bloat to please the RSP's - who
> > otherwise get whingy about customers whinging about speedtest not
> > showing 100/30mbit. Of course user education is 'too hard' .
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 3667 bytes --]
next prev parent reply other threads:[~2014-09-12 0:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 16:03 Dave Taht
2014-09-11 16:35 ` [Cerowrt-devel] [Bloat] " Pedro Tumusok
2014-09-11 18:19 ` [Cerowrt-devel] " Maciej Soltysiak
2014-09-11 18:33 ` David Personette
2014-09-12 0:13 ` [Cerowrt-devel] [Bloat] " Rich Brown
2014-09-12 0:35 ` dpreed
2014-09-12 0:42 ` Jonathan Morton
2014-09-12 1:24 ` dpreed
2014-09-12 1:49 ` Joel Wirāmu Pauling
2014-09-12 2:04 ` Jonathan Morton
2014-09-12 2:11 ` Joel Wirāmu Pauling
2014-09-12 1:48 ` Rich Brown
2014-09-12 15:24 ` Rick Jones
2014-09-13 0:19 ` David P. Reed
2014-09-12 7:17 ` Jesper Dangaard Brouer
2014-09-12 12:16 ` Rich Brown
2014-09-12 12:55 ` Jesper Dangaard Brouer
2014-09-12 0:31 ` dpreed [this message]
2014-09-12 9:44 ` [Cerowrt-devel] " Toke Høiland-Jørgensen
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=1410481900.628723265@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=joel@aenertia.net \
--cc=wmf@felter.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