From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by lists.bufferbloat.net (Postfix) with ESMTPS id 752CF3ED86 for ; Wed, 23 Dec 2015 06:43:31 -0500 (EST) Received: by mail-ob0-x22d.google.com with SMTP id iw8so162678883obc.1 for ; Wed, 23 Dec 2015 03:43:31 -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=n8eGxOctMTy5C2HNY+nDEe0Ue9jF9OhFYzFmr9szw9Y=; b=m1yWnbPgeNymeFiGgBZjOYDpwoYJDriRNqBE/PSHwNnsVzQBs3neZjmsvbIzZdlqVb /AsVndJ/4jnzmlTAnb9N9UCnXvik8zYCxiDH0+Ng1yl0wAPlsIFigOE+3L2wkIznQ+Pe Fnzt0Zp+wXpVjen1G/OETXy2Ry8bBVWgWcqieYgQ5lyjeVAYaky6kJeWZeWNP7OJbEOl 8OY0HQAq/RjeKtsvvHkIiTFNI7kXbUtZRaB3yUZ6rfsZpOVQVJTHXQTacu5gmX8PwF13 RXaCSQmntIP2hN5MfYCQb5vQ+Hl2ulx7FfrZRbtuzvy1G4VvDl797JbtFnl5GTHHJXXu dg6Q== MIME-Version: 1.0 X-Received: by 10.60.39.200 with SMTP id r8mr14211447oek.81.1450871010925; Wed, 23 Dec 2015 03:43:30 -0800 (PST) Received: by 10.202.187.3 with HTTP; Wed, 23 Dec 2015 03:43:30 -0800 (PST) In-Reply-To: <5679CF0F.4080506@darbyshire-bryant.me.uk> References: <6F86FBB0-AA69-44F3-82D0-31465906974D@gmx.de> <56657A82.2080601@darbyshire-bryant.me.uk> <95560E7E-DEAF-40D8-B704-CEA38A0CDE62@gmx.de> <85A5A21C-E468-4F81-8A36-0F1AD6C84435@gmx.de> <5679CF0F.4080506@darbyshire-bryant.me.uk> Date: Wed, 23 Dec 2015 12:43:30 +0100 Message-ID: From: Dave Taht To: Kevin Darbyshire-Bryant Cc: Jonathan Morton , moeller0 , cake@lists.bufferbloat.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] second system syndrome X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2015 11:43:31 -0000 squashing and washing are both well within the realm of ietf best practices. It is highly desirable to have this level of simple control on cake for inbound - for example, 90+ of all comcast traffic, no matter how originally marked, comes in marked as background, and should be changed to best effort on the gateway. Doing so with an iptables rule is inefficient and it is difficult (along with the rest of sqm-scripts) to hook into other people's iptables rules. On outbound - frankly I was surprised remarking dns, ntp, and mosh as AF42 worked as well as it did, there was only one place where it failed (which resulted in the removal of AF42 marking to mosh mainline) - MIT. There ARE a few indicators like background and IMM that often survive end to end elsewhere. more extensive remarking, as kevin also wants to do, seems complex. Dave T=C3=A4ht Let's go make home routers and wifi faster! With better software! https://www.gofundme.com/savewifi On Tue, Dec 22, 2015 at 11:30 PM, Kevin Darbyshire-Bryant wrote: > > > On 21/12/15 15:36, Jonathan Morton wrote: >> In that context, the =E2=80=9Csquash=E2=80=9D and =E2=80=9Cwash=E2=80=9D= features truly baffle me. I=E2=80=99d prefer to see them both gone. Eith= er you want to *use* Diffserv, in which case downstream networks might also= benefit from the same markings, or you want to *ignore* it, in which case = you might as well leave the existing marks alone, or you want to do somethi= ng more sophisticated that Cake=E2=80=99s core feature set doesn=E2=80=99t = support. >> >> In short, Cake is *not* the right place to change the DSCP field. A sep= arate qdisc could be written to do that job with minimal overhead and a ded= icated configuration interface, and be inserted either before or after Cake= as required. Or we could wait for pre-ingress-qdisc firewall rules to bec= ome available. > Feel free to remove. If squash shouldn't be there, then neither should > wash. It was an idea to split out the use of diffserv markings vs the > clearing of them that the original "squash" option implemented into > 'diffserv/squash/wash". Bad ideas shouldn't be included so get rid of > it :-) > > Kevin >