From: Dave Taht <dave.taht@gmail.com>
To: Jan Ceuleers <jan.ceuleers@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] The Dark Problem with AQM in the Internet?
Date: Thu, 28 Aug 2014 11:13:21 -0700 [thread overview]
Message-ID: <CAA93jw4DrBp5DkQ1SCicO5x+CLUa-w3V49AGXML-pGk0EhNa8g@mail.gmail.com> (raw)
In-Reply-To: <53FF6E56.8070800@gmail.com>
On Thu, Aug 28, 2014 at 11:00 AM, Jan Ceuleers <jan.ceuleers@gmail.com> wrote:
> On 08/28/2014 06:35 PM, Fred Baker (fred) wrote:
>> When a message is lost due to an error, how do you determine whose fault
>> it is?
>
> Links need to be engineered for the optimum combination of power,
> bandwidth, overhead and residual error that meets requirements. I agree
> with your implied point that a single error is unlikely to be indicative
> of a real problem, but a link not meeting requirements is someone's fault.
>
> So like Jerry I'd be interested in an ability for endpoints to be able
> to collect statistics on per-hop loss probabilities so that admins can
> hold their providers accountable.
I will argue that a provider demonstrating 3% packet loss and low
latency is "better" than a provider showing .03% packet loss and
exorbitant latency. So I'd rather be measuring latency AND loss.
One very cool thing that went by at sigcomm last week was the concept
of "active networking" revived in the form of "Tiny Packet Programs":
see:
http://arxiv.org/pdf/1405.7143v3.pdf
Which has a core concept of a protocol and virtual machine that can
actively gather data from the path itself about buffering, loss, etc.
No implementation was presented, but I could see a way to easily do it
in linux via iptables. Regrettably, elsewhere in the real world, we
have to infer these statistics via various means.
> Jan
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
next prev parent reply other threads:[~2014-08-28 18:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 18:16 Jerry Jongerius
2014-08-23 19:30 ` Jonathan Morton
2014-08-23 20:01 ` Sebastian Moeller
2014-08-25 17:13 ` Greg White
2014-08-25 18:09 ` Jim Gettys
2014-08-25 19:12 ` Sebastian Moeller
2014-08-25 21:17 ` Bill Ver Steeg (versteb)
2014-08-25 21:20 ` Bill Ver Steeg (versteb)
2014-08-28 13:19 ` Jerry Jongerius
2014-08-28 14:07 ` Jonathan Morton
2014-08-28 17:20 ` Jerry Jongerius
2014-08-28 17:41 ` Dave Taht
2014-08-28 18:15 ` Jonathan Morton
2014-08-29 14:21 ` Jerry Jongerius
2014-08-29 16:31 ` Jonathan Morton
2014-08-29 16:54 ` Jerry Jongerius
2014-08-28 18:59 ` Sebastian Moeller
2014-08-29 11:33 ` Jerry Jongerius
2014-08-29 12:18 ` Sebastian Moeller
2014-08-29 14:42 ` Dave Taht
2014-08-29 1:59 ` David Lang
2014-08-29 14:37 ` Jerry Jongerius
2014-08-30 6:05 ` Jonathan Morton
2014-08-30 6:28 ` Stephen Hemminger
2014-08-30 6:45 ` Jonathan Morton
2014-09-01 17:30 ` Jerry Jongerius
2014-09-01 17:40 ` Dave Taht
2014-08-28 14:39 ` Rich Brown
2014-08-28 16:20 ` Jerry Jongerius
2014-08-28 16:35 ` Fred Baker (fred)
2014-08-28 18:00 ` Jan Ceuleers
2014-08-28 18:13 ` Dave Taht [this message]
2014-08-29 1:57 ` David Lang
2014-08-28 18:41 ` Kenyon Ralph
2014-08-28 19:04 ` Dave Taht
2014-08-28 16:36 ` Greg White
2014-08-28 16:52 ` Bill Ver Steeg (versteb)
2014-09-01 11:47 ` Richard Scheffenegger
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=CAA93jw4DrBp5DkQ1SCicO5x+CLUa-w3V49AGXML-pGk0EhNa8g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jan.ceuleers@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