Re: [aqm] publishing algorithms
Dave Taht <dave.taht@gmail.com> Thu, 17 April 2014 21:58 UTC
Return-Path: <dave.taht@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12FA71A01F5 for <aqm@ietfa.amsl.com>; Thu, 17 Apr 2014 14:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 QKkcFq3TBDrz for <aqm@ietfa.amsl.com>; Thu, 17 Apr 2014 14:58:28 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5B14D1A01A5 for <aqm@ietf.org>; Thu, 17 Apr 2014 14:58:28 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id t60so965974wes.5 for <aqm@ietf.org>; Thu, 17 Apr 2014 14:58:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=0GA9FbWCVb5l7cSP0hwcBTcDK1YkeN/1lzORQRUiXFE=; b=fbUpJqocB2n2miAESt7JbWwxLfVRayljAqZsQHgWOc4RjCgj2BCKeymkSBDBahJ0eC KDT7T+YfrQ/asKDo6k5Bd0IURA5XFseGxiwSFFRSXpaDoVWJsyZlhPSjeKxx2KI9s5m8 K0RuTAnSFIjKDVSTX60XNO/J12CHJiLPy6cwkL1w3Rmp11fdRlgTpgVTwxoLH/2PYVVu DnEkNZm2qTN3kjpSehRop8g3lsYoyORqSMIR7vxSdWQE8T+O+s/gCI3oXBLrn4hkohKM FEHzAbKnQ1SJ5aPYSa8El+4DD3+wgCCCzgY+uL8TllEEk9Lk7jMiMeR36VLF+T+HMBmn JtOw==
MIME-Version: 1.0
X-Received: by 10.194.175.70 with SMTP id by6mr13657596wjc.3.1397771904185; Thu, 17 Apr 2014 14:58:24 -0700 (PDT)
Received: by 10.216.177.10 with HTTP; Thu, 17 Apr 2014 14:58:24 -0700 (PDT)
In-Reply-To: <533AAD07.103@mti-systems.com>
References: <533AAD07.103@mti-systems.com>
Date: Thu, 17 Apr 2014 14:58:24 -0700
Message-ID: <CAA93jw499EwJSMLT-+giS5+h0KHJoFEE2xVD8RizELoK4cEouQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Wesley Eddy <wes@mti-systems.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/K5alJfMbWjFh7Ez_UgCehldmUmQ
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] publishing algorithms
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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, 17 Apr 2014 21:58:34 -0000
On Tue, Apr 1, 2014 at 5:11 AM, Wesley Eddy <wes@mti-systems.com> wrote: > Hello AQMers. As chairs, Richard and I had been planning to let > the evaluation guidelines converge and then use those to guide > adoption of algorithm documents. > > However, we now think there may be value in not waiting so long, > and getting some algorithm documents moving along more quickly. I saw this came out on april 1, and have a tendency to ignore stuff that comes out that day. :) > We hope you can provide some feedback on the plan below: > > 1) Starting soon, we may look to adopt a small number of algorithm > drafts for Experimental, with the goal that by doing so, it will > increase the number of eyeballs and independent reviews of them, and > enhance the quality, since people may be implementing to the drafts > in order to test using the evaluation guidelines. Each algorithm > *must* clearly identify which types of use cases / scenarios it is > targeted for. We submitted the codel and fq_codel drafts for consideration prior to ietf 89, and have got no feedback from anyone as yet. The first went into tsvwg https://datatracker.ietf.org/doc/draft-nichols-tsvwg-codel/?include_text=1 and the second is seemingly homeless as yet: https://tools.ietf.org/html/draft-hoeiland-joergensen-aqm-fq-codel-00 As they were being developed independently, they have a few nits in relating to each other that need to be resolved, presently. If this is a new requirement, and it seems like it is, then those will need to be revised more fully, although each has caveats and use cases described already late in the document. (sections 6 and 9 in the first, section 10 in the second) Are you proposing an explicit use cases and scenarios section? > 2) Adoption of an algorithm spec as a working group draft will require > working group consensus that the algorithm looks attractive to > experiment with for the stated scenarios, and multiple parties will > plan to be looking at it, testing, analyzing, providing feedback, > etc. +1 I note that I have another draft in progress that I hope to complete before ietf-90 describing multiple deployed aqm + packet scheduling + classification systems in the hope to get the overall conversation on track. http://snapon.lab.bufferbloat.net/~d/draft-taht-home-gateway-best-practices-00.html and I'd like to talk to that at ietf 90 if I'm not too broke to go. Otherwise hawaii. > > 3) The evaluation guidelines / scenarios drafts being worked on > separately will guide the later selection of one or more Experimental > algorithms to become Proposed Standards with applicability > statements for the scenarios they have been evaluated in. At this point I must confess to being deeply dissatisfied with the progress in the AQM guidelines document. I don't know what to do about it, I've tried to talk about the issues being totally missed in things like this: http://www.bufferbloat.net/projects/cerowrt/wiki/Smart_Queue_Management and here on the list... and at the moment I'd prefer more folk have better models and understanding of actual traffic types on various media types before even trying to write anything down as to what valid tests are. I think I have finally come up for what I'd like this group to be doing, which is at least partially out of scope for the charter, but the acronym is nice: "CQM" - "Comprehensive Queue Management", and a goal is to try and design something that leverages the work other groups such as rmcat are doing. > We're interested to know if the working group thinks this sounds like > a good idea, bad idea, or any other thoughts. By all means, let's get folk fiddling with the working algorithms and code that exists today and is distributed now with every Linux box. Perhaps some more BSD support will show up soon, or hardware support in some other gear other than in what I describe above. I'm all in favor of new algorithms too, if anybody's got some... > > -- > Wes Eddy > MTI Systems > > _______________________________________________ > aqm mailing list > aqm@ietf.org > https://www.ietf.org/mailman/listinfo/aqm -- Dave Täht NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
- [aqm] publishing algorithms Wesley Eddy
- Re: [aqm] publishing algorithms Michael Welzl
- Re: [aqm] publishing algorithms Fred Baker (fred)
- Re: [aqm] publishing algorithms Wesley Eddy
- Re: [aqm] publishing algorithms Dave Taht