From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jan.ceuleers@gmail.com>
Received: from mailrelay116.isp.belgacom.be (mailrelay116.isp.belgacom.be
	[195.238.20.143])
	by huchra.bufferbloat.net (Postfix) with ESMTP id AB4A421F304
	for <bloat@lists.bufferbloat.net>; Wed, 29 Jul 2015 22:22:03 -0700 (PDT)
X-Belgacom-Dynamic: yes
X-Cloudmark-SP-Filtered: true
X-Cloudmark-SP-Result: v=1.1 cv=Ax9Kd9og7W2htzcJF9odWb+87PP6pPoG1t8Q07ebhfo=
	c=1 sm=2 a=p-Fh0BJKayhyu-NfRpMA:9 a=pILNOxqGKmIA:10
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2DWCgDds7lV/6Re9FFbgxqyQIsYhSaCUAQCAoFcOhMBAQEBAQEBgQqEJAEBBFYGHAEQCwsDCgkWDwkDAgECAREWHgYBDAEHAQGIFAEZAbsajhAKGYELhFgBAQEBAQEEAQEBAQEBARuLToQ8SweELAEEhxWGX4cCjEiBRocRjH2DZCaDfzyCfQEBAQ
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; 30 Jul 2015 07:22: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
	t6U5HlCZ027314; Thu, 30 Jul 2015 07:17:48 +0200
Message-ID: <55B9B37B.9050506@gmail.com>
Date: Thu, 30 Jul 2015 07:17:47 +0200
From: Jan Ceuleers <jan.ceuleers@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>, David Lang <david@lang.hm>
References: <55B92BF3.2000607@gmail.com>
	<alpine.DEB.2.02.1507291426410.16775@nftneq.ynat.uz>
	<alpine.DEB.2.02.1507300651040.11810@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1507300651040.11810@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: bloat <bloat@lists.bufferbloat.net>
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 <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Thu, 30 Jul 2015 05:22:32 -0000

On 30/07/15 06:52, Mikael Abrahamsson wrote:
> On Wed, 29 Jul 2015, David Lang wrote:
> 
>> 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?
> 
> Measuring latency is doable (using the same mechanism that traceroute
> with for instance max-ttl 5), but I don't know how much of this is
> available to your web application?
> 
> If you sent 5 packets with TTL 1-5 and measured the time to get back the
> ttl-expired-in-transit ICMP, you could get an indication where the
> latency increase was happening.

Yes, that's what I had in mind.