From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 9A3A03B260 for ; Mon, 28 Nov 2016 10:23:31 -0500 (EST) Received: by mail-io0-x22a.google.com with SMTP id c21so228563295ioj.1 for ; Mon, 28 Nov 2016 07:23:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=lg9TAzfC1IsS6tlRo0kggFhPZ5sBYBO1OOSDe9mfvKE=; b=ov6ODfUkyeQrQYW6kkdNDjx6wYGwrkOWhNGKmemzSTf/ltnJEFB8At1KJL0xjMWp+o xENATfpVFmQCeDv11E5aZ+AgV75FcEBBM3sblmqq7HBDW67eDRN3mes5IXVZxiEiJB4x 4poAoaNLVY5pzuwYtKhEjnRmw6raf9PSrgbQNENqXB39Dq91Ol4K9M8k/KBoQrhlvATp Xrk74co2+ZR0w1JIWdva9j+UV41IsBJuG9qgrhtu44iuhkVoQtDM7QLObwFwNQzH4Zf1 C8W/0Rq3BWoRAul4KHyJwLFa5rjBibMoFttOmsdw/EUbR42mfLDpmIoc8WysCB3E+Yiy 8hUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=lg9TAzfC1IsS6tlRo0kggFhPZ5sBYBO1OOSDe9mfvKE=; b=M7M+O2FeTEnHUog2EgAIqeY8zC7EFpYtCgHVaORlPoz/xJuPR4DAyYoBo1v+3WQZig SlHo/5AzCbHOydyLOnzcFDzXilXhx0PgFCptmHtfl/XpqcaKRJ/GDjK8JnBStDSOOfgd V3XjRD1Pz0vm6ijc56Y5EqB9524GfCitN0M2c0M0eix8lTv8JXcyy2JABcjlC7cesKvd S9/KmZNXYyO7gf6kLZD2X+umbFX1NrT9KKflYL2jsAWc7pAuyIuoPXCRjpMIJilTJzrZ iKDaRsS0FUbEx696LNN9M1JRRDges5xiNyJ417uw/GzMO5LVI7UD2IDB6DPstarucVhv lukQ== X-Gm-Message-State: AKaTC03hdzIvrbG9hEwADDLSSsZuKpOVkMYmf9/ggAgJX9KurjSWS8HUtNoWlQddCp+Ijw== X-Received: by 10.36.28.204 with SMTP id c195mr18635428itc.81.1480346609274; Mon, 28 Nov 2016 07:23:29 -0800 (PST) Received: from [192.168.1.104] (cpe-76-188-215-129.neo.res.rr.com. [76.188.215.129]) by smtp.gmail.com with ESMTPSA id h76sm19990292ioi.43.2016.11.28.07.23.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Nov 2016 07:23:28 -0800 (PST) To: bloat@lists.bufferbloat.net References: <548F6875-8670-4784-8A4D-9D4E6F0F20BD@gmail.com> <65cde0ee-4cc8-22c8-5274-a4eafe9cf338@pollere.com> From: Wesley Eddy Message-ID: <229474f1-841f-60f9-0c7a-e613adac12fc@mti-systems.com> Date: Mon, 28 Nov 2016 10:23:22 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Bloat] Fixing bufferbloat in 2017 X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2016 15:23:31 -0000 On 11/28/2016 10:12 AM, Dave Taht wrote: > On Mon, Nov 28, 2016 at 4:48 AM, David Collier-Brown wrote: >> A short RFC with a clear summary would change the ground on which we stand. >> Include me in if you're planning one. > Call me grumpy. Call me disaffected. But it's been 4 years into the > IETF RFC process with codel and fq_codel with still no end in sight. > Hi Dave, while it's been undeniably slow, "no end in sight" is not really accurate. Here is the correct status, since I am document shepherd for both: - The fq-codel draft is completely and totally done in terms of IETF process, and has been in the RFC Editor's queue simply awaiting the codel draft to arrive. This is what the "MISSREF" state indicates in that IETF datatracker tool. It completed the IETF last call and IESG balloting in March/April earlier this year. - The codel document completed AQM working group last call, and I believe is awaiting the authors to make changes requested by the Area Director in order to go for IETF Last Call and IESG balloting. The end is most definitely within sight!