Re: [aqm] [Bloat] ping loss "considered harmful"

"Fred Baker (fred)" <> Tue, 03 March 2015 18:00 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id BF05B1A1A45 for <>; Tue, 3 Mar 2015 10:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Status: No, score=-114.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id J1207RNPydFQ for <>; Tue, 3 Mar 2015 10:00:29 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EECA81A0360 for <>; Tue, 3 Mar 2015 10:00:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2916; q=dns/txt; s=iport; t=1425405616; x=1426615216; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=qb6U/qDebyNjZ4JuxVQ4iCHDiyjP3e0wi79v56lCwEI=; b=EVRfnlAYVwGe8P0Hu0LIfuo386ZYrgh4DP3FUC14jmCcOdpCRlPQUcUu z4cOr92SR0AtQ7SmSIkoyX1unFnu/Fdec2Uh1rjZftdh4hOvv8tCl0O/P rizDy+B+Gyarnogpu4bQyXhWN0W2xTsztpQKisHVBkquy4eMs+zKBG7AD 4=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.09,682,1418083200"; d="asc'?scan'208";a="400494557"
Received: from ([]) by with ESMTP; 03 Mar 2015 18:00:15 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t23I0FYn021417 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Mar 2015 18:00:15 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Tue, 3 Mar 2015 12:00:15 -0600
From: "Fred Baker (fred)" <>
To: Wesley Eddy <>
Thread-Topic: [aqm] [Bloat] ping loss "considered harmful"
Thread-Index: AQHQVdvmDWBYEA2CWkyvb8nphm+1ug==
Date: Tue, 03 Mar 2015 18:00:14 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/signed; boundary="Apple-Mail=_B6E8299E-53E0-4F4C-BE1F-5FCE73074BD1"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <>
Cc: bloat <>, Dave Taht <>, "" <>, "" <>
Subject: Re: [aqm] [Bloat] ping loss "considered harmful"
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 03 Mar 2015 18:00:30 -0000

> On Mar 3, 2015, at 9:29 AM, Wesley Eddy <> wrote:
> On 3/3/2015 12:20 PM, Fred Baker (fred) wrote:
>>> On Mar 1, 2015, at 7:57 PM, Dave Taht <
>>> <>> wrote:
>>> How can we fix this user perception, short of re-prioritizing ping in
>>> sqm-scripts?
>> IMHO, ping should go at the same priority as general traffic - the
>> default class, DSCP=0. When I send one, I am asking whether a random
>> packet can get to a given address and get a response back. I can imagine
>> having a command-line parameter to set the DSCP to another value of my
>> choosing.
> I generally agree, however ...
> The DSCP of the response isn't controllable though, and likely the DSCP
> that is ultimately received will not be the one that was sent, so it
> can't be as simple as echoing back the same one.  Ping doesn't tell you
> latency components in the forward or return path (some other protocols
> can do this though).
> So, setting the DSCP on the outgoing request may not be all that useful,
> depending on what the measurement is really for.

Note that I didn’t say “I demand”… :-)

I share the perception that ping is useful when it’s useful, and that it is at best an approximation. If I can get a packet to the destination and a response back, and I know the time I sent it and the time I received the response, I know exactly that - messages went out and back and took some amount of total time. I don’t know anything about the specifics of the path, of buffers en route, or delay time in the target. Traceroute tells me a little more, at the cost of a more intense process. In places I use ping, I tend to send a number of them over a period of time and observe on the statistics that result, not a single ping result.