From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailrelay101.isp.belgacom.be (mailrelay101.isp.belgacom.be [195.238.20.128]) by huchra.bufferbloat.net (Postfix) with ESMTP id 7CAD821F208 for ; Wed, 29 Jul 2015 12:42:02 -0700 (PDT) X-Belgacom-Dynamic: yes X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=on0vsgdz1NEtXcMZlQwg/MwbIQQ3jhei9UjQb9HCs8o= c=1 sm=2 a=c072IT-_BTrDby_eIOQA:9 a=QEXdDO2ut3YA:10 a=6Iw1T2dlFgJbRWAo:21 a=jKOQUN_l6O012i-o:21 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2AEDAAcLLlV/6Re9FFbgxWEYK1cixGJVjsSAQEBAQEBAYEKhE0zBhwnDwIFFgsCCwMCAQIBERYkDQgBAYgUARkBqg6PX4FsjhoKGYELhQSBIpIjgUMBBJRwjESIVpBaJoFWgik8gn0BAQE Received: from 164.94-244-81.adsl-dyn.isp.belgacom.be (HELO zotac.xperim.be) ([81.244.94.164]) by relay.skynet.be with ESMTP; 29 Jul 2015 21:42:01 +0200 Received: from [192.168.1.172] (mordor.xperim.be [192.168.1.172]) by zotac.xperim.be (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id t6TJdV3a029339 for ; Wed, 29 Jul 2015 21:39:31 +0200 Message-ID: <55B92BF3.2000607@gmail.com> Date: Wed, 29 Jul 2015 21:39:31 +0200 From: Jan Ceuleers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: bloat Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [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 19:42:32 -0000 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