Re: [aqm] floating a draft charter

Mirja Kühlewind <mirja.kuehlewind@ikr.uni-stuttgart.de> Tue, 04 June 2013 14:58 UTC

Return-Path: <mirja.kuehlewind@ikr.uni-stuttgart.de>
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 40A0321F9EB1 for <aqm@ietfa.amsl.com>; Tue, 4 Jun 2013 07:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.707
X-Spam-Level:
X-Spam-Status: No, score=-0.707 tagged_above=-999 required=5 tests=[AWL=1.015, BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c2wfoahbw-ar for <aqm@ietfa.amsl.com>; Tue, 4 Jun 2013 07:57:47 -0700 (PDT)
Received: from mailsrv.ikr.uni-stuttgart.de (mailsrv.ikr.uni-stuttgart.de [129.69.170.2]) by ietfa.amsl.com (Postfix) with ESMTP id B916221F99F3 for <aqm@ietf.org>; Tue, 4 Jun 2013 06:11:16 -0700 (PDT)
Received: from netsrv1.ikr.uni-stuttgart.de (netsrv1-c [10.11.12.12]) by mailsrv.ikr.uni-stuttgart.de (Postfix) with ESMTP id 27BBB601FA; Tue, 4 Jun 2013 15:11:15 +0200 (CEST)
Received: from vpn-2-cl195 (vpn-2-cl195 [10.41.21.195]) by netsrv1.ikr.uni-stuttgart.de (Postfix) with ESMTP id 220AE601F8; Tue, 4 Jun 2013 15:11:15 +0200 (CEST)
From: Mirja Kühlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
To: Wesley Eddy <wes@mti-systems.com>
Date: Tue, 04 Jun 2013 15:11:14 +0200
User-Agent: KMail/1.9.10 (enterprise35 0.20101217.1207316)
References: <5190FB21.5080100@mti-systems.com> <201305301420.51606.mirja.kuehlewind@ikr.uni-stuttgart.de> <51A77AB5.9040302@mti-systems.com>
In-Reply-To: <51A77AB5.9040302@mti-systems.com>
X-KMail-QuotePrefix: >
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201306041511.14779.mkuehle@ikr.uni-stuttgart.de>
Cc: aqm@ietf.org
Subject: Re: [aqm] floating a draft charter
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 04 Jun 2013 14:58:01 -0000

Hi Wes,

thanks, that's already very helpful. I was maybe even thinking about a 
milestone on something like 'requirements for initial deployment'... don't 
know if this makes sense though.

Mirja


On Thursday 30 May 2013 18:13:41 Wesley Eddy wrote:
> On 5/30/2013 8:20 AM, Mirja Kuehlewind wrote:
> > But my point is, we should not only to standardize more and more AQM
> > mechanisms because that's a large research area which maybe even should
> > be homed in the IRTF, but we need to find actually deployment strategies.
> > Having a working group on AQM will already help to make people aware of
> > the topic and maybe think about using AQM. But only standardizing more
> > and more AQM queue, might end up in investing a lot of working that
> > no-one will ever use.
>
> I suggest appending something like this to the charter:
>
>   Many AQM algorithms have been proposed in academic literature, but
>   very few are widely implemented and deployed.  A goal of the working
>   group is to produce recommendations that will actually be used, and
>   algorithms that will actually be implemented, deployed in equipment,
>   and enabled.  Towards these ends, the group actively encourages
>   participation from operators and implementers, and will coordinate
>   with the IETF OPS area and other relevant parts of the IETF and
>   Internet community.  Wider research and evaluation of AQM mechanisms
>   shall be coordinated with the IRTF/ICCRG, and significant
>   participation in this WG from the academic and research community is
>   highly desirable, when it is directly relevant to implementation and
>   deployment.
>
>
> We will definitely need to get engagement from some of the operators
> that participate in the IETF, and should solicit participation more
> widely outside as well (e.g. advertise to NANOG list, bufferbloat
> list, etc.) in order to attract operators and implementers that aren't
> already aware of this activity.
>
> Would this help to address your concern?