General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Pedro Tumusok <pedro.tumusok@gmail.com>
To: David Collier-Brown <davecb@spamcop.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Fixing bufferbloat in 2017
Date: Mon, 28 Nov 2016 16:14:22 +0100	[thread overview]
Message-ID: <CACQiMXY6C4qZMVeUR_TTkS7YuL6_O6A7fHOSF6QtUMU9a9-uCA@mail.gmail.com> (raw)
In-Reply-To: <cd39a3fb-4de2-a7bc-6410-307be177d879@rogers.com>

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

On Mon, Nov 28, 2016 at 1:48 PM, David Collier-Brown <davec-b@rogers.com>
wrote:

> A short RFC with a clear summary would change the ground on which we stand.
> Include me in if you're planning one.
>
> --dave
>
>
There are some RFCs that vendors uses for throughput testing, RFC2544 I
have seen on a few Firewall vendors datasheets atleast, not seen any
reference RFC3511.

Pedro



>
> On 28/11/16 01:00 AM, Jan Ceuleers wrote:
>
>> On 28/11/16 03:16, Jim Gettys wrote:
>>
>>> Ookla may have made themselves long term irrelevant by their recent
>>> behavior.  When your customers start funding development of a
>>> replacement (as Comcast has), you know they aren't happy.
>>>
>>> So I don't sweat Ookla: helping out the Comcast test effort is probably
>>> the best way to get bufferbloat in front of everyone, and best yet, the
>>> code for the tests is out there.
>>>
>> I do hope you're right Jim, but I still worry that Ookla is heavily
>> entrenched in carriers' test labs. This position has, I believe, come
>> about not because of Ookla's expertise in network testing but rather
>> because of market pull (i.e. speedtest.net's huge popularity with
>> end-users).
>>
>> As long as both of these positions remain (i.e. Ookla's mind share of
>> end-users and their resulting market share in the labs of large
>> purchasers of CPE) their lack of interest in bufferbloat is going to
>> keep this topic off the agenda in a large part of the industry.
>>
>> Unless Ookla can be coerced somehow.
>>
>> I have previously suggested standardising network throughput testing
>> methods and "grading" criteria. If there's an RFC on this subject
>> carriers are going to be interested in conformance to it and will
>> pressure their suppliers (of network testing gear, of CPE etc).
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>>
>
>
> --
> David Collier-Brown,         | Always do right. This will gratify
> System Programmer and Author | some people and astonish the rest
> davecb@spamcop.net           |                      -- Mark Twain
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>



-- 
Best regards / Mvh
Jan Pedro Tumusok

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

  parent reply	other threads:[~2016-11-28 15:14 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.454.1479929363.3555.bloat@lists.bufferbloat.net>
2016-11-26 15:33 ` Rich Brown
2016-11-27  1:53   ` Aaron Wood
2016-11-27  6:10     ` Mikael Abrahamsson
2016-11-27 21:24   ` Dave Taht
2016-11-28  2:11     ` Kathleen Nichols
2016-11-28  2:16       ` Jim Gettys
2016-11-28  6:00         ` Jan Ceuleers
2016-11-28 12:48           ` David Collier-Brown
2016-11-28 15:12             ` Dave Taht
2016-11-28 15:23               ` Wesley Eddy
2016-11-28 15:35                 ` Dave Taht
2016-11-28 16:58                   ` Stephen Hemminger
2016-11-28 17:07                     ` Dave Taht
2016-11-28 19:02                       ` Jonathan Morton
2016-11-28 17:52                     ` Kathleen Nichols
2016-11-28 15:14             ` Pedro Tumusok [this message]
2016-11-28 15:23               ` Dave Taht
2016-11-28 15:10           ` Dave Taht
2016-11-28  2:47       ` David Lang
     [not found] <mailman.447.1479909940.3555.bloat@lists.bufferbloat.net>
2016-11-23 18:16 ` [Bloat] fixing " Rich Brown
2016-11-23 18:46   ` David Lang
2016-11-23 18:58     ` Jonathan Morton
2016-11-23 19:15       ` David Lang
2016-11-23 20:37       ` Toke Høiland-Jørgensen
2016-11-22 15:32 Dave Taht
2016-11-22 16:19 ` Jan Ceuleers
2016-11-22 16:25   ` Dave Taht
2016-11-22 16:38     ` Jim Gettys
2016-11-23  8:28     ` Mikael Abrahamsson
2016-11-23 11:04       ` Jonathan Morton
2016-11-23 11:59       ` Kelvin Edmison
2016-11-23 13:31         ` Pedro Tumusok
2016-11-23 14:05           ` Mário Sérgio Fujikawa Ferreira
2016-11-23 17:20           ` Mikael Abrahamsson
2016-11-23 17:27             ` Benjamin Cronce
2016-11-23 17:31               ` Mikael Abrahamsson
2016-11-23 17:40                 ` Sebastian Moeller
2016-11-23 17:50                 ` Noah Causin
2016-11-23 17:56                   ` David Lang
2016-11-23 18:05                     ` Benjamin Cronce
2016-11-23 18:38                       ` David Lang
2016-11-23 19:29                         ` Benjamin Cronce
2016-11-23 19:42                           ` David Lang
2016-11-23 20:20                             ` Dave Taht
2016-11-23 17:54                 ` David Lang
2016-11-23 18:09                   ` Mikael Abrahamsson
2016-11-23 18:18                     ` Sebastian Moeller
2016-11-23 18:24                       ` Dave Taht
2016-11-23 20:39                         ` Toke Høiland-Jørgensen
2016-11-23 19:13                       ` David Lang
2016-11-23 18:17                   ` Dave Taht
2016-11-23 15:32 ` Pedretti Fabio
2016-11-23 19:29   ` Stephen Hemminger
2016-11-23 19:22 ` Dave Taht

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=CACQiMXY6C4qZMVeUR_TTkS7YuL6_O6A7fHOSF6QtUMU9a9-uCA@mail.gmail.com \
    --to=pedro.tumusok@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.net \
    /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