From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <wes@mti-systems.com>
Received: from atl4mhob02.myregisteredsite.com
	(atl4mhob02.myregisteredsite.com [209.17.115.40])
	by huchra.bufferbloat.net (Postfix) with ESMTP id 26DCA21F304
	for <cerowrt-devel@lists.bufferbloat.net>;
	Tue,  3 Mar 2015 09:29:44 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.208])
	by atl4mhob02.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id
	t23HTfwu013378 for <cerowrt-devel@lists.bufferbloat.net>;
	Tue, 3 Mar 2015 12:29:41 -0500
Received: (qmail 4357 invoked by uid 0); 3 Mar 2015 17:29:41 -0000
X-TCPREMOTEIP: 24.166.126.82
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.0.3?) (wes@mti-systems.com@24.166.126.82)
	by 0 with ESMTPA; 3 Mar 2015 17:29:41 -0000
Message-ID: <54F5EF7B.4000006@mti-systems.com>
Date: Tue, 03 Mar 2015 12:29:31 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>, Dave Taht <dave.taht@gmail.com>
References: <CAA93jw7KW=9PH002d3Via5ks6+mHScz5VDhpPVqLUGK2K=Mhew@mail.gmail.com>
	<F2745259-5DEB-49B1-AB7C-C8E4E1217360@cisco.com>
In-Reply-To: <F2745259-5DEB-49B1-AB7C-C8E4E1217360@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: "aqm@ietf.org" <aqm@ietf.org>, "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] [aqm] ping loss "considered harmful"
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
	<cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2015 17:30:13 -0000

On 3/3/2015 12:20 PM, Fred Baker (fred) wrote:
> 
>> On Mar 1, 2015, at 7:57 PM, Dave Taht <dave.taht@gmail.com
>> <mailto:dave.taht@gmail.com>> 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.

-- 
Wes Eddy
MTI Systems