From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (mail.lang.hm [64.81.33.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 5D1E221F827 for ; Wed, 29 Jul 2015 14:28:03 -0700 (PDT) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id t6TLS1ix008070; Wed, 29 Jul 2015 14:28:01 -0700 Date: Wed, 29 Jul 2015 14:28:00 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Jan Ceuleers In-Reply-To: <55B92BF3.2000607@gmail.com> Message-ID: References: <55B92BF3.2000607@gmail.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: bloat Subject: Re: [Bloat] Speed tests - attribution of latency to relevant network hops X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2015 21:28:32 -0000 On Wed, 29 Jul 2015, Jan Ceuleers wrote: > 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. unless you measure it per hop, how are you going to attribute it to each hop? and unless you have a server at that layer to talk to, how do you know what the latency or bandwidth is? David Lang