From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <swmike@swm.pp.se>
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by huchra.bufferbloat.net (Postfix) with ESMTPS id 4A66A21F3A8;
	Wed,  4 Mar 2015 11:45:48 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501)
	id F4127A3; Wed,  4 Mar 2015 20:45:45 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail;
	t=1425498346; bh=OwR9PQ4wtryx+aWTQupyt2jkcPfCnGh89Tmi59GYGlQ=;
	h=Date:From:To:cc:Subject:In-Reply-To:References:From;
	b=dUjnUzhJC4wA9lHSj2MhgAjmb3+Jo2IKePAul2WL42JhDib+gwxI9K7dubgDJApEK
	9D9WxmHmkcOFBqVAeMvWDXMdIKU1M0Sg08mrmlKcVlg9P5jJfaXsMQmrZOOLx8sqHr
	qE+eNoX0m8CnwFk9QIMyS5fKmGCMf8Oe3y4tOTyM=
Received: from localhost (localhost [127.0.0.1])
	by uplift.swm.pp.se (Postfix) with ESMTP id EA861A1;
	Wed,  4 Mar 2015 20:45:45 +0100 (CET)
Date: Wed, 4 Mar 2015 20:45:45 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: dpreed@reed.com
In-Reply-To: <1425490481.842932044@apps.rackspace.com>
Message-ID: <alpine.DEB.2.02.1503042044380.20507@uplift.swm.pp.se>
References: <CAA93jw7KW=9PH002d3Via5ks6+mHScz5VDhpPVqLUGK2K=Mhew@mail.gmail.com>
	<F2745259-5DEB-49B1-AB7C-C8E4E1217360@cisco.com>
	<54F5EF7B.4000006@mti-systems.com>
	<E44C11DD-68F9-4340-8F99-18D2894FE36B@cisco.com>
	<1425490481.842932044@apps.rackspace.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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] [aqm]   [Bloat] 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: Wed, 04 Mar 2015 19:46:17 -0000

On Wed, 4 Mar 2015, dpreed@reed.com wrote:

> DSCP should not be changed en route, so the receiver of the echo reply 
> should be able to know what DSCP was used on the reply packet.

Changing the DSCP bits by the ISP is definitely not unheard of, so don't 
count on it.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se