General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Kelvin Edmison <kelvin@edmison.net>, Dave Taht <dave.taht@gmail.com>
Cc: jb <justinbeech@gmail.com>, bloat <Bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports bufferbloat tests
Date: Thu, 7 Apr 2016 18:23:21 +0000	[thread overview]
Message-ID: <D32BD653.12F65E%jason_livingood@cable.comcast.com> (raw)
Message-ID: <20160407182321.0njVL9dIQRz1TZgyu1ktqrhJfcvHo2qBvNxdWBLZqfg@z> (raw)
In-Reply-To: <F6266EE9-3024-4C68-ADB1-52ADB288595A@edmison.net>

On 4/6/16, 1:08 PM, "Bloat on behalf of Kelvin Edmison"
<bloat-bounces@lists.bufferbloat.net on behalf of kelvin@edmison.net>
wrote:


>I think people focus on packet loss so much because the term is short,
>seemingly conveys a lot of info and is easy to measure.
>
>Given that know how to measure bloat, it strikes me that what is needed
>is a short marketing-style tag for bloat that can be put up against the
>term "packet loss".

The BITAG has discussed this issue and debated whether to take up a work
item on it, because it is clear that it is not always the case that more
(or any) packet loss is necessarily bad. And Dave Clark and Steve Bauer
have done some good analysis basically saying packet loss measurements
don¹t really correlate the broadband quality and more work is needed.

My sincere hope is that the new FCC broadband label does not encourage
behavior that will lead to a goal of 0% loss, which would quite obviously
be bad in many ways from a performance and quality standpoint and run
counter to all the good AQM-related work.

Jason


  reply	other threads:[~2016-04-07 18:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  1:04 Dave Taht
2016-04-06  1:33 ` Brandon Applegate
2016-04-06  2:21   ` Dave Taht
2016-04-06  3:19     ` jb
2016-04-06 15:30       ` Dave Taht
2016-04-06 16:08         ` Kelvin Edmison
2016-04-07 18:13           ` Livingood, Jason [this message]
2016-04-07 18:23             ` Livingood, Jason
2016-04-20  6:06             ` jb
2016-04-20  6:10               ` Dave Taht
2016-04-20 12:43               ` Jonathan Morton
2016-04-20 22:53                 ` jb
2016-04-21  2:22                   ` Jonathan Morton
2016-04-07  2:06         ` jb
2016-04-07  2:14           ` Jonathan Morton
2016-04-07 18:16         ` Livingood, Jason

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=D32BD653.12F65E%jason_livingood@cable.comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=Bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=justinbeech@gmail.com \
    --cc=kelvin@edmison.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