IETF Logo Mail Archive

Re: [aqm] floating a draft charter

Yuchung Cheng <ycheng@google.com> Thu, 30 May 2013 16:17 UTC

Return-Path: <ycheng@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 EE74821F95FC for <aqm@ietfa.amsl.com>; Thu, 30 May 2013 09:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, 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 01sDr6QnkdNp for <aqm@ietfa.amsl.com>; Thu, 30 May 2013 09:17:17 -0700 (PDT)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 40DD121F96E5 for <aqm@ietf.org>; Thu, 30 May 2013 09:17:12 -0700 (PDT)
Received: by mail-la0-f41.google.com with SMTP id ee20so458124lab.0 for <aqm@ietf.org>; Thu, 30 May 2013 09:17:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kSGd8pgFRw0xE9xoZ34bJGjp0Wq0x2BJD40/Sy1HDQA=; b=If9DuHBaRuriEmgpmvDZtJvT2vHf41lmbPz8TXLhO9VGc22LFKi8mGELct7OcvWrza dEGzaB+XUKs2MOj1TJARnM2z+tlyLkjObp5PLqWKCuubCeOFNwKA18x1OkyfrXaqArR2 YbIjOVIQOjPz3bSA6bZzF/P6N3TT6zZCY0pPKxreL7tyWe0iGlCcIj5a6/FpKKKogQMa +etalLSqbEbKraikbb1xck6bVXtvJOC52Hmww9JYiZlCHR2CKyiZ92m3qiDCF6xria77 q/3xhT1PhTtFvvB5Ddrvguqqcj3nI1HMTATTbTQj7DuAJIG+7Vr0yeN5RTL3vRs8EEn+ CvrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=kSGd8pgFRw0xE9xoZ34bJGjp0Wq0x2BJD40/Sy1HDQA=; b=Ny48c+yZ6m3g5yVihADpATDBdki5QywTPHYtBTW1swD3Vr3MdQpl5GKspXg226ZZvS j1Kx6ihA4W0RNIRRQBCIKV/Asm2UX51/Hxs/NGhZqQkYSrNRUJUqfWKeq93H2SzeadKV ANpfVLja+bgFSTkLkhIgD9BoUhoihDsOiELRX5lE0comlseZr1OAG62j0cbk/E249Ami VL5aut7np+lGxM6LJgD26pbe8eWLmacGuuh+l2Z5DRGBURTOgJF8o/DUv3yHDhGXXMF6 Zl0V9QvKbTtlHKzg9xKLuPT1vswoWr+lLGSiEWL1DLqhPzZqfDyjSyS/YgiXIt0HT9S9 zh/Q==
X-Received: by 10.112.21.234 with SMTP id y10mr4113537lbe.53.1369930631134; Thu, 30 May 2013 09:17:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.80.227 with HTTP; Thu, 30 May 2013 09:16:51 -0700 (PDT)
In-Reply-To: <51A77AB5.9040302@mti-systems.com>
References: <5190FB21.5080100@mti-systems.com> <201305301420.51606.mirja.kuehlewind@ikr.uni-stuttgart.de> <51A77AB5.9040302@mti-systems.com>
From: Yuchung Cheng <ycheng@google.com>
Date: Thu, 30 May 2013 09:16:51 -0700
Message-ID: <CAK6E8=dzgwr02EBU8eN6yU88LVLTZZmopyRA1G1Y1P+k27CqKA@mail.gmail.com>
To: Wesley Eddy <wes@mti-systems.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQn+70e4wLTzQVWP5WvI8tpFpxQSlk/ckLAcQqfYhUj0BR/WZdvefe6OTrtUIGBFRpVKVvm31WiQXBqN23yKabUje4GxriFYYmHZWRMF4z523j1AGlOIaTHsmC3cId8USCw2WYD/fBy1UlhQ8o4Fy5P7PSHP8eMJVjmzc1sLudg2cH1MILoBtdb4rRYEta0f2ZHsbP7h
Cc: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>, 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:17:18 -0000

On Thu, May 30, 2013 at 9:13 AM, Wesley Eddy <wes@mti-systems.com> 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
I would suggest changing "A goal" to "the goal"

>   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 mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm

v2.23.0 | Report a Bug | By Email