Re: [aqm] updated draft charter

grenville armitage <> Thu, 11 July 2013 10:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B3B4821F9D59 for <>; Thu, 11 Jul 2013 03:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.782
X-Spam-Status: No, score=-1.782 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, SARE_SUB_OBFU_Q1=0.227]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JdZUeO61rocA for <>; Thu, 11 Jul 2013 03:11:48 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id BDC1B21F9C8E for <>; Thu, 11 Jul 2013 03:11:43 -0700 (PDT)
Received: from [] ( []) by (8.14.3/8.14.3) with ESMTP id r6BABQrs001934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Jul 2013 20:11:40 +1000
Message-ID: <>
Date: Thu, 11 Jul 2013 20:11:26 +1000
From: grenville armitage <>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121107 Thunderbird/16.0.2
MIME-Version: 1.0
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [aqm] updated draft charter
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Jul 2013 10:11:53 -0000

On 07/11/2013 14:50, Wesley Eddy wrote:
>  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.

I don't see "SQM" adding clarity (and risks bike-shedding over
what constitutes 'Smarter...' and whether that implies scheduling
algorithms any more than 'Active..." does).

The (draft) full name "Active Queue Management and Packet Scheduling"
seems entirely reasonable, even if unpronounceable as an acronym.

(But if we're interested in alternative names: since pkt scheduling
usually implies N>1 queues, which implies classification prior
to queue-ification, perhaps the "CQS" working group instead? For
"classification, queuing and scheduling". 'Cos we might want to
also say a few words about how traffic is classified into these
actively managed and scheduled queue(s)...)