General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Matt Mathis <mattmathis@google.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Packet loss in FCC press release
Date: Fri, 27 Feb 2015 11:47:26 -0800	[thread overview]
Message-ID: <CAH56bmAJWdjHF9auVmWy3gD_sN9QtqwUvJaWwpuBOi59UwMh_g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4N9mYyAvpcGtTM10y+2uezzUBJM0Kt_PsvUT2kjgpFmA@mail.gmail.com>

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

You are failing to make a distinction between the edges (access) and the
core (ISP's backbone and interconnects).

At the edges, where multiplexing is relatively low and queueing is
required, loss or ECN is necessary to regulate queue occupancy.

In the core, where traffic is highly aggregated and queues are generally
tiny, (excess) loss indicates insufficient capacity, and that some users
are suffering due to other people's traffic.   In the core losses (or
queueing) are nearly always a bad thing.

This one sentence is sufficient to solve much of the net neutrality problem.

See: https://tools.ietf.org/html/draft-ietf-ippm-model-based-metrics-03

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

Privacy matters!  We know from recent events that people are using our
services to speak in defiance of unjust governments.   We treat privacy and
security as matters of life and death, because for some users, they are.

On Fri, Feb 27, 2015 at 8:35 AM, Dave Taht <dave.taht@gmail.com> wrote:

> On Fri, Feb 27, 2015 at 7:47 AM, Jonathan Morton <chromatix99@gmail.com>
> wrote:
> > It's not ideal, but I'm not quite as worried about that as you might be.
> > There are several potential causes of packet loss in a network, and
> > increasing buffer sizes is only likely to have a minor and temporary
> effect
> > on one of them.
>
> Clearly establishing that 0 packet loss (without ECN) is bad, that
> some range of rates of packet loss relative to
> bandwidth is GOOD, and levels above that indicative of a problem,
> would nice. I can envision a meter
> designed to show that.
>
> >
> > Meanwhile, increased deployment of ECN would permit adding AQM as a
> means to
> > decrease packet loss.
> >
> > Random packet loss due to poor quality lines, and also due to dumb
> policers
> > and overloaded core routers, is probably what's intended here.
> >
> > - Jonathan Morton
> >
> >
> > _______________________________________________
> > Bloat mailing list
> > Bloat@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
> >
>
>
>
> --
> Dave Täht
> Let's make wifi fast, less jittery and reliable again!
>
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

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

  reply	other threads:[~2015-02-27 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 10:49 Eggert, Lars
2015-02-27 15:47 ` Jonathan Morton
2015-02-27 16:35   ` Dave Taht
2015-02-27 19:47     ` Matt Mathis [this message]
2015-02-27 19:08   ` Rick Jones

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=CAH56bmAJWdjHF9auVmWy3gD_sN9QtqwUvJaWwpuBOi59UwMh_g@mail.gmail.com \
    --to=mattmathis@google.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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