From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dave.taht@gmail.com>
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 7740421F55F
	for <cake@lists.bufferbloat.net>; Mon, 16 Nov 2015 07:57:30 -0800 (PST)
Received: by obdgf3 with SMTP id gf3so126126007obd.3
	for <cake@lists.bufferbloat.net>; Mon, 16 Nov 2015 07:57:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=MZFvVmqOPYo/dvbGRcXvenKeYWzP3JmGoislulgky5Q=;
	b=FILiuxTCxDl9NUPIkL9ErmUE2EwwFf5SiRMvlwfVbI/FqqyiDQQk6eNrMTDowMxBuo
	ADjOUAl/d5J5ofzZegluCQTUzBjLjCkeZcG4vP8aH2cBkLPuaSxUveesXL3L7TAYoVI0
	CB3xXL6mj6pz3/Ve1HEOIi8dnbwEFPjUEn7pDvCr3r9/oRwivPyZ08Xk06TCwSNi4ZwY
	HXc/HwpwCeYlgImcu1YIPgE5tLiBdOzmiT/4xjhwOhO0heTBKo31Ia9s5a82nMcV3ohI
	3Y3zk0NfBmUB0r7nogYXGGPECNZS+EPLLdLrzjvfiVAT1Gs0tiWkIqd3On053w9vuLH2
	LOYg==
MIME-Version: 1.0
X-Received: by 10.60.15.131 with SMTP id x3mr22760902oec.74.1447689449256;
	Mon, 16 Nov 2015 07:57:29 -0800 (PST)
Received: by 10.202.50.130 with HTTP; Mon, 16 Nov 2015 07:57:29 -0800 (PST)
In-Reply-To: <5649F423.40000@darbyshire-bryant.me.uk>
References: <56420697.9080606@darbyshire-bryant.me.uk>
	<5649EF39.3060300@darbyshire-bryant.me.uk>
	<CAA93jw5myLePsqvLf=VTsC71OduF-dNz4Pq1EgOzeGkZyR8C3g@mail.gmail.com>
	<5649F423.40000@darbyshire-bryant.me.uk>
Date: Mon, 16 Nov 2015 16:57:29 +0100
Message-ID: <CAA93jw4T_C+FNnhEXm4Ke7A9L0GLybOU5RtaBX6vfM+SjgHF6Q@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Announce - possible new feature - DSCP cleaning
X-BeenThere: cake@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Cake - FQ_codel the next generation <cake.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cake>,
	<mailto:cake-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cake>
List-Post: <mailto:cake@lists.bufferbloat.net>
List-Help: <mailto:cake-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cake>,
	<mailto:cake-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 15:57:52 -0000

isn't there some other boolean variable somewhere ?

Dave T=C3=A4ht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi


On Mon, Nov 16, 2015 at 4:20 PM, Kevin Darbyshire-Bryant
<kevin@darbyshire-bryant.me.uk> wrote:
>
>
> On 16/11/15 15:03, Dave Taht wrote:
>> I have not been doing any active development until... tomorrow.
>>
>> A goal I have for today is to actually build a version of openwrt +
>> all this stuff for the linksys ac1200.
>>
>> I was not particularly huge on using another field (q->squash) to
>> trigger squashing, and I cannot come up with a use case that makes
>> sense to me.
>>
>> Under what circumstances do you think separating these two functions
>> to be useful?
>
> I wanted to be able to use diffserv marking for internal bandwidth
> policing purposes whilst clearing those bits by the time they hit the
> ISP.  On ingress it makes no sense, on egress I can see a use.
>
>
>