Re: [aqm] updated draft charter
gorry@erg.abdn.ac.uk Thu, 11 July 2013 16:07 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
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 CAA8021F9F80 for <aqm@ietfa.amsl.com>; Thu, 11 Jul 2013 09:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.427
X-Spam-Level:
X-Spam-Status: No, score=-106.427 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 j6cqtLfVMtON for <aqm@ietfa.amsl.com>; Thu, 11 Jul 2013 09:07:22 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id A694E21F9BB2 for <aqm@ietf.org>; Thu, 11 Jul 2013 09:07:22 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 5274C2B40D1; Thu, 11 Jul 2013 17:06:53 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Thu, 11 Jul 2013 17:06:53 +0100
Message-ID: <91b91547d0e717bf6376929bb55bf81f.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <CAGhGL2BnTXuZejwf5C38MndMKbm+eM2ANWjJt+pwQFp89ECpFg@mail.gmail.com>
References: <51DE398B.2090103@mti-systems.com> <CAGhGL2BnTXuZejwf5C38MndMKbm+eM2ANWjJt+pwQFp89ECpFg@mail.gmail.com>
Date: Thu, 11 Jul 2013 17:06:53 +0100
From: gorry@erg.abdn.ac.uk
To: Jim Gettys <jg@freedesktop.org>
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: Wesley Eddy <wes@mti-systems.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] updated 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, 11 Jul 2013 16:07:35 -0000
I agreed that AQM has to some extent already been deployed in some places and this could be confusing to then redefine or obsolete this. For what it's worth I don't like "smart" queueing as a name - implying it's sounds like a marketing term rather than a combination of "AQM" mark/drop and flow scheduling. If SQM was short for scheduling and queue management I may have liked the abbreviation more, ... let's see where this discussion ends. Gorry > On Thu, Jul 11, 2013 at 12:50 AM, Wesley Eddy <wes@mti-systems.com> wrote: > >> I think the attached updated draft charter reflects most of the >> feedback that we've heard so far. >> >> Note that Dave Taht suggested we might want to go with something >> like "Smarter Queue Management" (SQM) for the WG name, because >> purely AQM as a name may not capture FQ type of mechanisms that we >> may want to have in-scope. I think that scoping discussion may >> still be going on into Berlin, but it's a good point, and likely >> some other people have cute ideas for a name that could capture >> the potential broader scope. >> > > Both Dave's and my experience as relative newcomers to this area is that > the term AQM is pretty tightly bound to mark/drop algorithms in the minds > of many people in the IETF, who also categorize other algorithms as > queuing > algorithms. and make a pretty strong mental distinction between them. > > As my blog post this week > http://gettys.wordpress.com/2013/07/10/low-latency-requires-smart-queuing-traditional-aqm-is-not-enough/#more-1091argues, > the killer combination is a cross between rapidly autotuning > mark/drop algorithms with what we're calling flow queueing (since it isn't > "fair" in the also traditional sense of TCP fair queueing at all, and may > not involve TCP flows necessarily either). > > So while I'd be happy to lump this all into the AQM name bucket > personally, > I do think that a name that makes clear we're considering algorithms that > may marry both lines of intellectual thought together will avoid confusion > among many who have worked in one area or the other, but not both. "Smart > queue management" or SQM is the best we've come up with for a term. > - Jim > > >> -- >> Wes Eddy >> MTI Systems >> >> _______________________________________________ >> aqm mailing list >> aqm@ietf.org >> https://www.ietf.org/mailman/listinfo/aqm >> >> > _______________________________________________ > aqm mailing list > aqm@ietf.org > https://www.ietf.org/mailman/listinfo/aqm >
- [aqm] updated draft charter Wesley Eddy
- Re: [aqm] updated draft charter grenville armitage
- Re: [aqm] updated draft charter Jim Gettys
- Re: [aqm] updated draft charter gorry
- Re: [aqm] updated draft charter David Ros
- Re: [aqm] updated draft charter Jim Gettys
- Re: [aqm] updated draft charter grenville armitage
- Re: [aqm] updated draft charter Bob Briscoe
- Re: [aqm] updated draft charter Rong Pan (ropan)
- Re: [aqm] updated draft charter Dave Taht
- Re: [aqm] updated draft charter Dave Taht
- Re: [aqm] updated draft charter grenville armitage
- Re: [aqm] updated draft charter gorry
- Re: [aqm] updated draft charter grenville armitage
- Re: [aqm] updated draft charter Wesley Eddy
- Re: [aqm] updated draft charter Bob Briscoe
- Re: [aqm] updated draft charter Gorry
- [aqm] AQM jabber scribe? Janet P Gunn