From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 27EC921F411 for ; Mon, 25 Aug 2014 11:09:51 -0700 (PDT) Received: by mail-ob0-f172.google.com with SMTP id wn1so10942688obc.31 for ; Mon, 25 Aug 2014 11:09:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=YIM9Oc7YEHVosl99I58EUclurD/jkvK3QYhlwDHf5Rs=; b=ZQoZxR8q8qPNIGrjER5i5V4R1ZA/jq0UMndzhgwH9LlPuLQOPADNRvygX3hOH6gs5d 2Fh+LxFS3wWzeS3jybEE5UdGjRKF3cGYRV/sjoPfKm1fAuvykJAWp0FGnhsBL8NyEZJf GtcHSVFC/7kFc/f8geAbW60Wsy5D44SJCpsjKFRT3dldvEmPKDMQ+yPxw7/OxwEKi55q H38JMnqgLSSS7doI4A7Pk7iLaE0qvLDlhgpMIuai9ycqDOYrHZXg22l7CMVOt41/pcPx fmL2zTgo/M6WUl628nAbF+DlI3XoKhHaH+JiyGWHzRse/AqdIi7XTpZxxOk+5nkhz8Nu sBZw== MIME-Version: 1.0 X-Received: by 10.60.62.234 with SMTP id b10mr22923450oes.3.1408990190253; Mon, 25 Aug 2014 11:09:50 -0700 (PDT) Sender: gettysjim@gmail.com Received: by 10.76.124.72 with HTTP; Mon, 25 Aug 2014 11:09:50 -0700 (PDT) In-Reply-To: References: <000001cfbefe$69194c70$3b4be550$@duckware.com> Date: Mon, 25 Aug 2014 14:09:50 -0400 X-Google-Sender-Auth: vrNvDaHFwq6Bvk5nDOLpei73AB0 Message-ID: From: Jim Gettys To: Greg White Content-Type: multipart/alternative; boundary=047d7b45102cc83d3f0501781747 Cc: "bloat@lists.bufferbloat.net" Subject: Re: [Bloat] The Dark Problem with AQM in the Internet? 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: Mon, 25 Aug 2014 18:09:51 -0000 --047d7b45102cc83d3f0501781747 Content-Type: text/plain; charset=UTF-8 Note that I worked with Folkert Van Heusden to get some options added to his httping program to allow "ping" style testing against any HTTP server out there using HTTP/TCP. See: http://www.vanheusden.com/httping/ I find it slightly ironic that people are now concerned about ICMP ping no longer returning queuing information given that when I started working on bufferbloat, a number of people claimed that ICMP Ping could not be relied upon to report reliable information, as it may be prioritized differently by routers. This "urban legend" may or may not be true; I never observed it in my explorations. In any case, you all may find it useful, and my thanks to Folkert for a very useful tool. - Jim --047d7b45102cc83d3f0501781747 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Not= e that I worked with Folkert Van Heusden to get some options added to his h= ttping program to allow "ping" style testing against any HTTP ser= ver out there using HTTP/TCP.

See:

<= a href=3D"http://www.vanheusden.com/httping/">http://www.vanheusden.com/htt= ping/

I= find it slightly ironic that people are now concerned about ICMP ping no l= onger returning queuing information given that when I started working on bu= fferbloat, a number of people claimed that ICMP Ping could not be relied up= on to report reliable information, as it may be prioritized differently by = routers. This "urban legend" may or may not be true; I never obse= rved it in my explorations.

In any = case, you all may find it useful, and my thanks to Folkert for a very usefu= l tool.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Jim
<= br>
--047d7b45102cc83d3f0501781747--