
From nobody Wed Feb  8 10:40:35 2017
Return-Path: <session_request_developers@ietf.org>
X-Original-To: aqm@ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B6B1912957F; Wed,  8 Feb 2017 10:40:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: <session-request@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148657923372.4382.11305109458554855106.idtracker@ietfa.amsl.com>
Date: Wed, 08 Feb 2017 10:40:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/oAGlC1vBbK6d4DKNqhb5jZmMvao>
Cc: wes@mti-systems.com, ietf@kuehlewind.net, aqm-chairs@ietf.org, aqm@ietf.org
Subject: [aqm] aqm - Not having a session at IETF 98
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 18:40:33 -0000

Wesley Eddy, a chair of the aqm working group, indicated that the aqm working group does not plan to hold a session at IETF 98.

This message was generated and sent by the IETF Meeting Session Request Tool.



From nobody Mon Feb 13 22:30:45 2017
Return-Path: <dave.taht@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3D712940B for <aqm@ietfa.amsl.com>; Mon, 13 Feb 2017 22:30:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXsM62qDbxCG for <aqm@ietfa.amsl.com>; Mon, 13 Feb 2017 22:30:43 -0800 (PST)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB5371204D9 for <aqm@ietf.org>; Mon, 13 Feb 2017 22:30:42 -0800 (PST)
Received: by mail-qk0-x229.google.com with SMTP id p22so22473821qka.0 for <aqm@ietf.org>; Mon, 13 Feb 2017 22:30:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=HjRAqGfQDZHaq+qD0h2B6Q+J+Lr71x6cGufxTBzPMgM=; b=Dpt6Ao56CGQK86VoBPminNUJDLKQXkJvPRQ/LHSgvX8CdZrljLHlPD3pT5Xt6EpPUr F5A8iN4f9Mc/N+Z2BtDvXWBRv56EplAert64FZywFvVO53kgAuWTussafOOWGd/ejnRQ mpd27EUcsLw6bAXs49E1iNU/Zz1a53TPvK/yj2TJNYfFffyakYQ9GhrxbdvKYFmXKGDv 2HgctvVNQzZ7zBpdHw8S+uIXVLvFCx/5qGuxNSWbaBcvQZ5/5WO0u8/R64axdUU6yU0f s8i0vm3XIm5eGBi1H3/KuYux/D4g2Z9dWNnsx+omTpKc01C8xSjmc+rxy3pOOcOjHIK3 FvKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=HjRAqGfQDZHaq+qD0h2B6Q+J+Lr71x6cGufxTBzPMgM=; b=ru6IRDGvH3pKfyhu4rgjozO+cGTIpbTlLBsb1BnfpN7NQoCzQxzLbna63G6rwtfb5b Q6gtEhg3OkxfdWHCnxgBwhAxXv1Ynf6EXY02iWhyLp+VutoKE6PFyFDEvNfIj4JtuaHb 87bd8h8XaME4cX78BqWeDcxXQxIQ6gjxdxnrCm+oASLT89L1v7aftxbEUAUTA0lJTTn0 U4VS3zP74S99443lEoUuPL4QxBBqv9+mJFT5ETCUcd070lotC95dngUXgQldaSAlYuH0 n5GZ4a56U3gRN4RD3USA7t2PUqxKvtFy3kq2N3Al2IrdKs/w9oilLsJV/Kv6XW6loD+9 pZ2w==
X-Gm-Message-State: AMke39manfPhthd5IhnJWY0yAawu8DiGald4gRSameAAzGRi+4HZAgk2M7oK18mng/wi2emq6YhkqwlvguAtvg==
X-Received: by 10.55.9.15 with SMTP id 15mr25343779qkj.118.1487053841796; Mon, 13 Feb 2017 22:30:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.142.132 with HTTP; Mon, 13 Feb 2017 22:30:41 -0800 (PST)
From: Dave Taht <dave.taht@gmail.com>
Date: Mon, 13 Feb 2017 22:30:41 -0800
Message-ID: <CAA93jw5UZTbohs01aMwiHfggG+ytSZKZmQfkys-V2mpVh8+dnw@mail.gmail.com>
To: "aqm@ietf.org" <aqm@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/JAEjKB6LaHHNWWtpsJP3K6MLgqM>
Subject: [aqm] I am setting up a per holiday cron job
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 06:30:44 -0000

the template:

For [INSERT HOLIDAY], I'd really love to see a codel & fq_codel RFC publish=
ed.




--=20
Dave T=C3=A4ht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org


From nobody Tue Feb 14 07:26:41 2017
Return-Path: <wes@mti-systems.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA6EE129588 for <aqm@ietfa.amsl.com>; Tue, 14 Feb 2017 07:26:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mti-systems-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lU6FbPymt3rh for <aqm@ietfa.amsl.com>; Tue, 14 Feb 2017 07:26:38 -0800 (PST)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ADB4129530 for <aqm@ietf.org>; Tue, 14 Feb 2017 07:26:38 -0800 (PST)
Received: by mail-it0-x236.google.com with SMTP id c7so37247017itd.1 for <aqm@ietf.org>; Tue, 14 Feb 2017 07:26:38 -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=8tX433VUAvX+3c65QLWX309i+GdvzRSFjx/NHYUiDsc=; b=nwBWTwBt1CV8kYYISdbNVGScokM+6ptuwyYA9fxlHzjEFoeWmXIakQqgrDmVFRSj/q oySaHmC8gmiW/VyJMg/QKgxSkk0JW+vuTXVGTdicNRizXtculLHIKAjogrKW6+rxqb+S VD8X98V5BzkANO3SHka74A5H0rgsHY96iFb8dyKZdVxj84ZzRgPBksT5dKW4U1ZXN5jb 613QwEmWtbOOnHh+yek7zMlnLcCYgTqI/3hLURGFeqRDZhr98vxz+OabtuBPvDJUWgLI ZYzf77SNDqX1AcQdt/Ylrq0lCdYhqcEyxj5/ononc7uzmgbd7bAiUntoz4fCZtxltq+f u8mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=8tX433VUAvX+3c65QLWX309i+GdvzRSFjx/NHYUiDsc=; b=S4B4lIaHYjodq9hbJmNc19ey2PMiIALSu8VUleWaV6xajEXMThMM5Wuttfoi06LncO pk8mSIcnLgCOYWnP1LGBrcRL5MmueuaF0aFCx+YDi7IY7gGGuw0XHQuuUxXY6uirQr+F R9NWv+T2Ejwo8OzlgHO8ib6Fb2K8moCX3T3YHQR3GyiV/t8DTRHhHgq5Q4QP2Tw2g305 150oaJQgEIpyzgTHe4RRGyTTEo9NQX1g/OT8aEeVaVwR60BE+0uTSWN4x8og5qs98k2U 9YeCoy2hedh8yvND3rFh6hmdN9ExR62QXqDTYxVaEx6vtXieInL4cIC+tUTZ44x/1Cxe 7sMA==
X-Gm-Message-State: AMke39nXw+mH4eMOwwrX00eiPAnaa2uI57GUtsF/Y1PJb+kHVpFQSLCSK5R6RfMD4ME0Eg==
X-Received: by 10.36.185.93 with SMTP id k29mr3898335iti.66.1487085997690; Tue, 14 Feb 2017 07:26:37 -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 188sm1413195itm.12.2017.02.14.07.26.36 for <aqm@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 07:26:37 -0800 (PST)
To: aqm@ietf.org
References: <CAA93jw5UZTbohs01aMwiHfggG+ytSZKZmQfkys-V2mpVh8+dnw@mail.gmail.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <d5b720b3-2bb2-66b3-8573-638e323de352@mti-systems.com>
Date: Tue, 14 Feb 2017 10:26:30 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAA93jw5UZTbohs01aMwiHfggG+ytSZKZmQfkys-V2mpVh8+dnw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/SrgXNHSfNtmfEbNRjH9eEUJvcJE>
Subject: Re: [aqm] I am setting up a per holiday cron job
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 15:26:40 -0000

Hi Dave, thanks for asking :)

Since I've been the assigned shepherd for both, here's an update for the 
working group on status:

- The fq-codel draft cleared the working group last call, IETF last 
call, and IESG reviews, and has been waiting in the RFC Editor's queue 
on the codel draft (in RFC editor cluster #288: 
https://www.rfc-editor.org/cluster_info.php?cid=C288 ).

- The codel draft cleared the working group last call, and is in AD 
review, with some comments back and forth between Mirja and the 
editors.  As I understand, there is a question about compatibility 
between the IETF Trust statements at the beginning and later text in the 
document that talks about copyright and licensing of code snippets, 
which they are working through and getting advice on.



On 2/14/2017 1:30 AM, Dave Taht wrote:
> the template:
>
> For [INSERT HOLIDAY], I'd really love to see a codel & fq_codel RFC published.
>
>
>
>


From nobody Tue Feb 14 10:29:31 2017
Return-Path: <jri@google.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B20A5129A96 for <aqm@ietfa.amsl.com>; Tue, 14 Feb 2017 10:29:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Njfc79mW4KG4 for <aqm@ietfa.amsl.com>; Tue, 14 Feb 2017 10:29:28 -0800 (PST)
Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0FFD129A95 for <aqm@ietf.org>; Tue, 14 Feb 2017 10:29:27 -0800 (PST)
Received: by mail-ua0-x22c.google.com with SMTP id i68so91622096uad.0 for <aqm@ietf.org>; Tue, 14 Feb 2017 10:29:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=oAdJITGerVbJ8mAVYHPZxbKshMymwG/srbbcWDlyhjY=; b=TpPpLIsDXM3xHUTD6xc6k33s5nHeaMfNSZ8uUqJfe63Qv1Fq3FG5MEUx6SvwotJjxn r2pXYMTtOMwjlT0TY4iLpMDRZSv/3C0Nc25Ie4MyVlP7scnIgVogIKlaEC327pgtd177 1+a+wZ53M8v+3Fx6ov2hV8NKBdB/1Yrt1eboJJmvNkwELoz1SyIlnSltBQN3YIfXbjy6 CmEnkWHoOO7BdRC+rP8pBcR7F0QEGcpK6E5GLV3alDb84oYzjzjVWXv8teAOLME7Jf+3 AwKeqWFrT3RNVfflyOnvLulA9tkiIRxqS1h5MhCBVEBL/t1TWz3JasNOqglPOsHJYTrv nNgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=oAdJITGerVbJ8mAVYHPZxbKshMymwG/srbbcWDlyhjY=; b=WMy4dhn5MLeTkcI99h609bH+yRmxbU0f8HlK6MPsLHuc0q9ygiOUrejKHW9FzGcYS9 5gAEDlCp99hbQANDlLRjvMqlIH8mHzrtqT8Hd8tTLozMOggJUPpgJMwczf2KLvGd1dqJ 5WZmcL6EF3T1Y22PG2fbUN+9uKIMsnv/opHy1zurysJnSNqVcQUtDg5aRGHF+EOVLKpH yrsOu6DwwFPUvvRaRrWcJCGNaME0R0y7C/za5lmTYt36OxsDWZnQ+R0VgiZZRibABoGl ptpOC6AqBrzMNuC2I+rMLW/ApI4RH9InnzSQnJ0javkYpOhECK89nKGs3D3eXqwIHw15 /G+A==
X-Gm-Message-State: AMke39nQ/yl2hdWJb6hpov5MZjTmH6IAGCwk2OVB266BW3SSiSZKtZTtQdc6Sxs11dTpfJFdoxgDKmcpU0+RAJ/4
X-Received: by 10.159.38.73 with SMTP id 67mr13803750uag.155.1487096966501; Tue, 14 Feb 2017 10:29:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.51.14 with HTTP; Tue, 14 Feb 2017 10:29:26 -0800 (PST)
In-Reply-To: <d5b720b3-2bb2-66b3-8573-638e323de352@mti-systems.com>
References: <CAA93jw5UZTbohs01aMwiHfggG+ytSZKZmQfkys-V2mpVh8+dnw@mail.gmail.com> <d5b720b3-2bb2-66b3-8573-638e323de352@mti-systems.com>
From: Jana Iyengar <jri@google.com>
Date: Tue, 14 Feb 2017 10:29:26 -0800
Message-ID: <CAGD1bZbWL65kKjk3vuXgh+SHsh+1TybPiwhjysyTJ5YkwS+5cQ@mail.gmail.com>
To: Wesley Eddy <wes@mti-systems.com>
Content-Type: multipart/alternative; boundary=001a114950dc6ffd74054881bef7
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/NkvDk9TpeQiEnO2_sZt_W8fzNzo>
Cc: aqm@ietf.org
Subject: Re: [aqm] I am setting up a per holiday cron job
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:29:30 -0000

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

As Wes responded, we're working out the bits of code and the license in the
draft. We have resolution, and I need to get a revised draft to the AD with
some changes in.

On Tue, Feb 14, 2017 at 7:26 AM, Wesley Eddy <wes@mti-systems.com> wrote:

> Hi Dave, thanks for asking :)
>
> Since I've been the assigned shepherd for both, here's an update for the
> working group on status:
>
> - The fq-codel draft cleared the working group last call, IETF last call,
> and IESG reviews, and has been waiting in the RFC Editor's queue on the
> codel draft (in RFC editor cluster #288: https://www.rfc-editor.org/clu
> ster_info.php?cid=C288 ).
>
> - The codel draft cleared the working group last call, and is in AD
> review, with some comments back and forth between Mirja and the editors.
> As I understand, there is a question about compatibility between the IETF
> Trust statements at the beginning and later text in the document that talks
> about copyright and licensing of code snippets, which they are working
> through and getting advice on.
>
>
>
> On 2/14/2017 1:30 AM, Dave Taht wrote:
>
>> the template:
>>
>> For [INSERT HOLIDAY], I'd really love to see a codel & fq_codel RFC
>> published.
>>
>>
>>
>>
>>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>

--001a114950dc6ffd74054881bef7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As Wes responded, we&#39;re working out the bits of code a=
nd the license in the draft. We have resolution, and I need to get a revise=
d draft to the AD with some changes in.</div><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Tue, Feb 14, 2017 at 7:26 AM, Wesley Eddy <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:wes@mti-systems.com" target=3D"_blank=
">wes@mti-systems.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">Hi Dave, thanks for asking :)<br>
<br>
Since I&#39;ve been the assigned shepherd for both, here&#39;s an update fo=
r the working group on status:<br>
<br>
- The fq-codel draft cleared the working group last call, IETF last call, a=
nd IESG reviews, and has been waiting in the RFC Editor&#39;s queue on the =
codel draft (in RFC editor cluster #288: <a href=3D"https://www.rfc-editor.=
org/cluster_info.php?cid=3DC288" rel=3D"noreferrer" target=3D"_blank">https=
://www.rfc-editor.org/clu<wbr>ster_info.php?cid=3DC288</a> ).<br>
<br>
- The codel draft cleared the working group last call, and is in AD review,=
 with some comments back and forth between Mirja and the editors.=C2=A0 As =
I understand, there is a question about compatibility between the IETF Trus=
t statements at the beginning and later text in the document that talks abo=
ut copyright and licensing of code snippets, which they are working through=
 and getting advice on.<span class=3D"im HOEnZb"><br>
<br>
<br>
<br>
On 2/14/2017 1:30 AM, Dave Taht wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
the template:<br>
<br>
For [INSERT HOLIDAY], I&#39;d really love to see a codel &amp; fq_codel RFC=
 published.<br>
<br>
<br>
<br>
<br>
</blockquote>
<br></span><div class=3D"HOEnZb"><div class=3D"h5">
______________________________<wbr>_________________<br>
aqm mailing list<br>
<a href=3D"mailto:aqm@ietf.org" target=3D"_blank">aqm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/aqm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/aqm</a><br>
</div></div></blockquote></div><br></div>

--001a114950dc6ffd74054881bef7--


From nobody Tue Feb 28 17:16:15 2017
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8051289C4; Tue, 28 Feb 2017 17:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KiG2WQTCoceR; Tue, 28 Feb 2017 17:16:12 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A332912711D; Tue, 28 Feb 2017 17:16:12 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9A5F5B820DA; Tue, 28 Feb 2017 17:16:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170301011612.9A5F5B820DA@rfc-editor.org>
Date: Tue, 28 Feb 2017 17:16:12 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/1wG23QJawObZ8QVBCqk9ukFtIW8>
Cc: drafts-update-ref@iana.org, aqm@ietf.org, rfc-editor@rfc-editor.org
Subject: [aqm] RFC 8033 on Proportional Integral Controller Enhanced (PIE): A Lightweight Control Scheme to Address the Bufferbloat Problem
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 01:16:14 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8033

        Title:      Proportional Integral Controller Enhanced (PIE): 
                    A Lightweight Control Scheme to Address 
                    the Bufferbloat Problem 
        Author:     R. Pan, P. Natarajan,
                    F. Baker, G. White
        Status:     Experimental
        Stream:     IETF
        Date:       February 2017
        Mailbox:    ropan@cisco.com, 
                    prenatar@cisco.com, 
                    fredbaker.ietf@gmail.com,
                    g.white@cablelabs.com
        Pages:      30
        Characters: 58829
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-aqm-pie-10.txt

        URL:        https://www.rfc-editor.org/info/rfc8033

        DOI:        10.17487/RFC8033

Bufferbloat is a phenomenon in which excess buffers in the network
cause high latency and latency variation.  As more and more
interactive applications (e.g., voice over IP, real-time video
streaming, and financial transactions) run in the Internet, high
latency and latency variation degrade application performance.  There
is a pressing need to design intelligent queue management schemes
that can control latency and latency variation, and hence provide
desirable quality of service to users.

This document presents a lightweight active queue management design
called "PIE" (Proportional Integral controller Enhanced) that can
effectively control the average queuing latency to a target value.
Simulation results, theoretical analysis, and Linux testbed results
have shown that PIE can ensure low latency and achieve high link
utilization under various congestion situations.  The design does not
require per-packet timestamps, so it incurs very little overhead and
is simple enough to implement in both hardware and software.

This document is a product of the Active Queue Management and Packet Scheduling Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Tue Feb 28 17:16:44 2017
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF57212963A; Tue, 28 Feb 2017 17:16:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JN2ZqpWXyg1u; Tue, 28 Feb 2017 17:16:29 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF2BE129559; Tue, 28 Feb 2017 17:16:29 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C93EEB820E4; Tue, 28 Feb 2017 17:16:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170301011629.C93EEB820E4@rfc-editor.org>
Date: Tue, 28 Feb 2017 17:16:29 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/BDeeiiIFHEYJVhbpOvDGIsNKAvQ>
Cc: drafts-update-ref@iana.org, aqm@ietf.org, rfc-editor@rfc-editor.org
Subject: [aqm] RFC 8034 on Active Queue Management (AQM) Based on Proportional Integral Controller Enhanced PIE) for Data-Over-Cable Service Interface Specifications (DOCSIS) Cable Modems
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 01:16:37 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8034

        Title:      Active Queue Management (AQM) Based 
                    on Proportional Integral Controller Enhanced PIE) 
                    for Data-Over-Cable Service Interface Specifications (DOCSIS) 
                    Cable Modems 
        Author:     G. White, R. Pan
        Status:     Informational
        Stream:     IETF
        Date:       February 2017
        Mailbox:    g.white@cablelabs.com, 
                    ropan@cisco.com
        Pages:      17
        Characters: 33326
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-aqm-docsis-pie-02.txt

        URL:        https://www.rfc-editor.org/info/rfc8034

        DOI:        10.17487/RFC8034

Cable modems based on Data-Over-Cable Service Interface
Specifications (DOCSIS) provide broadband Internet access to over one
hundred million users worldwide.  In some cases, the cable modem
connection is the bottleneck (lowest speed) link between the customer
and the Internet.  As a result, the impact of buffering and
bufferbloat in the cable modem can have a significant effect on user
experience.  The CableLabs DOCSIS 3.1 specification introduces
requirements for cable modems to support an Active Queue Management
(AQM) algorithm that is intended to alleviate the impact that
buffering has on latency-sensitive traffic, while preserving bulk
throughput performance.  In addition, the CableLabs DOCSIS 3.0
specifications have also been amended to contain similar
requirements.  This document describes the requirements on AQM that
apply to DOCSIS equipment, including a description of the
"DOCSIS-PIE" algorithm that is required on DOCSIS 3.1 cable modems.

This document is a product of the Active Queue Management and Packet Scheduling Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


