From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <chromatix99@gmail.com>
Received: from mail-vc0-x235.google.com (mail-vc0-x235.google.com
	[IPv6:2607:f8b0:400c:c03::235])
	(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 AE6EC21F38C
	for <bloat@lists.bufferbloat.net>; Thu, 26 Feb 2015 12:42:38 -0800 (PST)
Received: by mail-vc0-f181.google.com with SMTP id im6so4899406vcb.12
	for <bloat@lists.bufferbloat.net>; Thu, 26 Feb 2015 12:42:37 -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;
	bh=p7l6qQVMeav6WNJ9+VViXbf33obQrU0h1wkOkq1miLM=;
	b=Ytnlw7t6YmtQpZ0AjFfUcPNp5A5zrBcw9SipLahFNovj+k8W7dCCBC73zQwV/2qeg4
	iJ0zU+aePqpOtU+eNUknAU9shnO4TPL57oE6bCN4TpD4YYj5WYvwDUL6fPRJmWux4/qO
	iW9UshM3/8YGckYl19uBe1rWRdUwzCPZtFy9CcEBqgpk8N5YwZTw/sP6cYP/2ipDTrxv
	2zb2FK2I578aHmQDirPmT9t6cB8b2/kTzpV72WYSHZCTjEPMVuZ4GMgb80GQrcPO9ew1
	HE51ICXM/JQxF7VsIB6/MCKlPhkBKJWgqVMPhFkujRpVDIHwhaQKWRf3NN4Hzw5Q81Gj
	u9fg==
MIME-Version: 1.0
X-Received: by 10.52.107.227 with SMTP id hf3mr10402224vdb.44.1424983357140;
	Thu, 26 Feb 2015 12:42:37 -0800 (PST)
Received: by 10.52.24.79 with HTTP; Thu, 26 Feb 2015 12:42:36 -0800 (PST)
Received: by 10.52.24.79 with HTTP; Thu, 26 Feb 2015 12:42:36 -0800 (PST)
In-Reply-To: <AE7F97DB5FEE054088D82E836BD15BE93194AC0D@xmb-aln-x05.cisco.com>
References: <CADnS-2hPmb3zt6GvdbZjDuM10VgN5yvMrxigUL5Z_-nA-dOyjw@mail.gmail.com>
	<alpine.DEB.2.02.1502250737150.4007@uplift.swm.pp.se>
	<201502250806.t1P86o5N011632@bagheera.jungle.bt.co.uk>
	<mck1t7$ies$1@ger.gmane.org>
	<FC82EEB0-5E7E-473F-B9B3-2BFEC06C7689@ifi.uio.no>
	<4A80D1F9-F4A1-4D14-AC75-958C5A2E8168@gmx.de>
	<3F47B274-B0E4-44F2-A434-E3C9F7D5D041@ifi.uio.no>
	<87twyaffv3.fsf@toke.dk>
	<alpine.DEB.2.02.1502251138490.4007@uplift.swm.pp.se>
	<1D438EDC-358D-4DD5-9B8D-89182256F66C@gmx.de>
	<alpine.DEB.2.02.1502251433230.4007@uplift.swm.pp.se>
	<54EDD951.50904@orange.com>
	<alpine.DEB.2.02.1502251659430.4007@uplift.swm.pp.se>
	<54EE07C0.60703@orange.com>
	<alpine.DEB.2.02.1502261353500.4007@uplift.swm.pp.se>
	<54EF2877.8030302@orange.com>
	<alpine.DEB.2.02.1502261517230.4007@uplift.swm.pp.se>
	<54EF3932.6020007@orange.com>
	<CAA93jw6zvB+ip4wFc2enNjnE+U7fvFzT4XFKzKP0V-3rgfkF2g@mail.gmail.com>
	<alpine.DEB.2.02.1502261952450.4007@uplift.swm.pp.se>
	<AE7F97DB5FEE054088D82E836BD15BE93194AC0D@xmb-aln-x05.cisco.com>
Date: Thu, 26 Feb 2015 22:42:36 +0200
Message-ID: <CAJq5cE08HcC6FEwNmOV5yv0XpSELLGR5M_Ur+2zqm2f_-HrSDA@mail.gmail.com>
From: Jonathan Morton <chromatix99@gmail.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec5485f94d03704051003ca7b
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] RED against bufferbloat
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2015 20:43:07 -0000

--bcaec5485f94d03704051003ca7b
Content-Type: text/plain; charset=UTF-8

> We need to be careful to specify behaviors, as opposed to
implementations. If we start to specify implementation details, the process
will get bogged down in intractable differences.

I understand these sorts of requirements. Since I'm waiting for one of my
computers to do something substantial, I'll have a quick stab at the
problem.

I suspect a modular approach might work best. Different modules can be
assigned to separate design teams, and a diagram can show how they fit
together. So a shaper module, a Codel queue module, a fair queue module.

- Jonathan Morton

--bcaec5485f94d03704051003ca7b
Content-Type: text/html; charset=UTF-8

<p dir="ltr">&gt; We need to be careful to specify behaviors, as opposed to implementations. If we start to specify implementation details, the process will get bogged down in intractable differences.</p>
<p dir="ltr">I understand these sorts of requirements. Since I&#39;m waiting for one of my computers to do something substantial, I&#39;ll have a quick stab at the problem.</p>
<p dir="ltr">I suspect a modular approach might work best. Different modules can be assigned to separate design teams, and a diagram can show how they fit together. So a shaper module, a Codel queue module, a fair queue module.</p>
<p dir="ltr"> - Jonathan Morton<br>
</p>

--bcaec5485f94d03704051003ca7b--