From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iy0-f171.google.com (mail-iy0-f171.google.com [209.85.210.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id CB08F201116; Tue, 6 Dec 2011 20:20:20 -0800 (PST) Received: by iaen33 with SMTP id n33so391949iae.16 for ; Tue, 06 Dec 2011 20:20:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=5LENVnhbpti/txMfh9CgaksHgrdwQneEfZFzpXdeEHg=; b=rRCKXGHafVSemQodvNgLUx62z3hJIiIcnpnQPeVIOq5OhOWoK9AskdKUDhpGez7ZJq l6GP4UjFoK1484qhXYNk2RRVAm+DyB0iQxNa3nbZOEBSdyB2wOlKeL2yk5pUcblSqXQc TPtx6qDk4ImpakYtd8nPHAnDqJQ4zh7i08kCY= MIME-Version: 1.0 Received: by 10.42.151.4 with SMTP id c4mr16849223icw.39.1323231619789; Tue, 06 Dec 2011 20:20:19 -0800 (PST) Received: by 10.231.204.83 with HTTP; Tue, 6 Dec 2011 20:20:19 -0800 (PST) Date: Wed, 7 Dec 2011 05:20:19 +0100 Message-ID: Subject: Beating Bufferbloat in 2012! From: Dave Taht To: bloat , bloat-devel Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2011 04:20:21 -0000 There is a post mortem on what we did right and wrong with cerowrt versions rc1 through rc7 over on the cerowrt-devel list. https://lists.bufferbloat.net/pipermail/cerowrt-devel/2011-December/thread.= html If you are a past, present, or future stakeholder in this sub-project I urge you to participate over there. I need to stress that that was/is always intended to be a 'sub' project of bufferbloat.net's, to conduct R&D into what was going on on the internet edge, and we learned - and fixed - a lot of problems, some solutions for which has been pushed upstream already, and are becoming more widely available. There are *many* other bloat-related problems that I'd like us to be trying= to address in the coming year. While I (and jim) are going to try to touch upon them here, I'm very interested in the opinions and thoughts of those on this list. I miss the heyday of the bloat list, where we had wide-ranging discussions of absolutely everything of relevance to bufferbloat. I mean, go back and review march-august. Wow. https://lists.bufferbloat.net/pipermail/bloat/ What did we forget about? What opinions have changed? What was easy? What seems to be hard? What did we do right and wrong this year? And what can we do better, next year? --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 FR Tel: 0638645374 http://www.bufferbloat.net