Re: [aqm] floating a draft charter
Wesley Eddy <wes@mti-systems.com> Thu, 30 May 2013 16:13 UTC
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 3071421F96CC for <aqm@ietfa.amsl.com>; Thu, 30 May 2013 09:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level:
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 P2Yo4vDN7HI8 for <aqm@ietfa.amsl.com>; Thu, 30 May 2013 09:13:48 -0700 (PDT)
Received: from atl4mhob10.myregisteredsite.com (atl4mhob10.myregisteredsite.com [209.17.115.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3F41421F96AC for <aqm@ietf.org>; Thu, 30 May 2013 09:13:48 -0700 (PDT)
Received: from mail.hostingplatform.com ([10.30.71.207]) by atl4mhob10.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r4UGDlOQ018209 for <aqm@ietf.org>; Thu, 30 May 2013 12:13:47 -0400
Received: (qmail 7241 invoked by uid 0); 30 May 2013 16:13:47 -0000
Received: from unknown (HELO ?172.27.250.182?) (wes@mti-systems.com@63.226.32.150) by 0 with ESMTPA; 30 May 2013 16:13:47 -0000
Message-ID: <51A77AB5.9040302@mti-systems.com>
Date: Thu, 30 May 2013 12:13:41 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
References: <5190FB21.5080100@mti-systems.com> <201305301420.51606.mirja.kuehlewind@ikr.uni-stuttgart.de>
In-Reply-To: <201305301420.51606.mirja.kuehlewind@ikr.uni-stuttgart.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Thu, 30 May 2013 16:13:54 -0000
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? -- Wes Eddy MTI Systems
- [aqm] floating a draft charter Wesley Eddy
- Re: [aqm] floating a draft charter Mirja Kuehlewind
- Re: [aqm] floating a draft charter Scheffenegger, Richard
- Re: [aqm] floating a draft charter Wesley Eddy
- Re: [aqm] floating a draft charter Yuchung Cheng
- Re: [aqm] floating a draft charter Mirja Kühlewind
- Re: [aqm] floating a draft charter Jim Gettys
- Re: [aqm] floating a draft charter Rong Pan (ropan)
- Re: [aqm] floating a draft charter Dave Taht
- Re: [aqm] floating a draft charter Andrew Mcgregor
- Re: [aqm] floating a draft charter Luca MUSCARIELLO
- Re: [aqm] floating a draft charter Jim Gettys
- Re: [aqm] floating a draft charter MUSCARIELLO Luca OLNC/OLN