General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jan Ceuleers <jan.ceuleers@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Speed tests - attribution of latency to relevant network hops
Date: Wed, 29 Jul 2015 21:39:31 +0200	[thread overview]
Message-ID: <55B92BF3.2000607@gmail.com> (raw)

Dear list,

Now that dslreports has set the benchmark on combining speed testing
with latency measurements I was thinking about what the next steps could
be. Here's what I came up with:

Would it be useful to try and attribute the latency to certain relevant
network hops, like so:

First hop: round-trip latency of the link connecting the user's machine
to their local network. This could be wifi or Ethernet in a home or
office environment; it could be wifi or cellular in a public
environment, etc.

Local network: round-trip latency to the first upstream port that has a
public IP address. Of course this is only useful if the user's machine
doesn't already have a routable IP address.

ISP: round-trip latency to the second upstream port that has a public IP
address. So this would be the DSLAM/BRAS/CMTS or whatever access
concentrator the ISP uses.

This would probably need to be based on ping. Which IP addresses to ping
would initially need to be found out through traceroute-like methods.

If we can then get users to tell us not only what Internet access
technology they use (i.e. cable, DSL, GPON etc) but also what local
access technology (i.e. wifi, Ethernet etc) we'd know how to attribute
the above numbers to technologies.

Jan

             reply	other threads:[~2015-07-29 19:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 19:39 Jan Ceuleers [this message]
2015-07-29 21:28 ` David Lang
2015-07-30  4:52   ` Mikael Abrahamsson
2015-07-30  5:17     ` Jan Ceuleers
2015-07-30 13:04       ` Bill Ver Steeg (versteb)
2015-07-30 14:54         ` Jan Ceuleers
2015-07-30 15:27           ` 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=55B92BF3.2000607@gmail.com \
    --to=jan.ceuleers@gmail.com \
    --cc=bloat@lists.bufferbloat.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