Re: [aqm] WG status

Michael Welzl <michawe@ifi.uio.no> Fri, 17 March 2017 08:39 UTC

Return-Path: <michawe@ifi.uio.no>
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 83C2C126BF6 for <aqm@ietfa.amsl.com>; Fri, 17 Mar 2017 01:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 EF0VJ3iMYzuC for <aqm@ietfa.amsl.com>; Fri, 17 Mar 2017 01:39:09 -0700 (PDT)
Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48A3C124D68 for <aqm@ietf.org>; Fri, 17 Mar 2017 01:39:08 -0700 (PDT)
Received: from mail-mx01.uio.no ([129.240.10.26]) by mail-out02.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1conPd-0007cs-3k for aqm@ietf.org; Fri, 17 Mar 2017 09:39:05 +0100
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx01.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1conPc-0005OF-Eq for aqm@ietf.org; Fri, 17 Mar 2017 09:39:05 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <9ca75fc4-c92c-fd92-fe53-d732189e2bec@mti-systems.com>
Date: Fri, 17 Mar 2017 09:39:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <089311A2-192B-4BF1-97C1-98D8F6E11770@ifi.uio.no>
References: <9ca75fc4-c92c-fd92-fe53-d732189e2bec@mti-systems.com>
To: "aqm@ietf.org" <aqm@ietf.org>
X-Mailer: Apple Mail (2.2104)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx01.uio.no: 129.240.68.135 is neither permitted nor denied by domain of ifi.uio.no) client-ip=129.240.68.135; envelope-from=michawe@ifi.uio.no; helo=boomerang.ifi.uio.no;
X-UiO-Ratelimit-Test: rcpts/h 6 msgs/h 4 sum rcpts/h 17 sum msgs/h 8 total rcpts 52838 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, AWL=-0.008, RP_MATCHES_RCVD=-0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 4BE7A014C31F0E9B20067CE74CE4C68A8E0749E1
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 4 total 12656 max/h 21 blacklist 0 greylist 0 ratelimit 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/vD4fdYbQ_Hy6ePWVgCJXaYGbvQU>
Subject: Re: [aqm] WG status
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 17 Mar 2017 08:39:11 -0000

Hi all,

Please note that we also have a talk on TCP Prague scheduled in ICCRG:
https://datatracker.ietf.org/meeting/98/agenda/iccrg/

Cheers,
Michael


> On 16 Mar 2017, at 15:26, Wesley Eddy <wes@mti-systems.com> wrote:
> 
> I think there are no surprises here, but as there is an IETF meeting coming up, I wanted to make sure the AQM WG status is clear.
> 
> The final working group document (on CoDel) is now in IETF Last Call, on the main IETF list.
> 
> AQM does not plan to meet in Chicago, and should be closed down as the CoDel draft becomes published.  HOWEVER, the work on L4S and DualQ that has been discussed here is continuing in the TSVWG.  People that are interested in this should definitely be joining the TSVWG list and discussing it there:
> 
> https://www.ietf.org/mailman/listinfo/tsvwg
> 
> TSVWG has agenda time planned in Chicago for L4S, so you may wish to participate there.
> 
> For any additional or future work on AQM algorithms, implementation, etc., I think there will be several possible options that can apply depending on what the work is, including: ICCRG, TSVWG, AD-sponsoring, individual submissions, etc.  As usual, ask the ADs when in doubt :)
> 
> 
> 
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm