Re: [aqm] updated draft charter

Wesley Eddy <wes@mti-systems.com> Fri, 12 July 2013 14:42 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 3584421F9BD8 for <aqm@ietfa.amsl.com>; Fri, 12 Jul 2013 07:42:21 -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 p1S-Du7RNpVO for <aqm@ietfa.amsl.com>; Fri, 12 Jul 2013 07:42:15 -0700 (PDT)
Received: from atl4mhob08.myregisteredsite.com (atl4mhob08.myregisteredsite.com [209.17.115.46]) by ietfa.amsl.com (Postfix) with ESMTP id 539D121F91CC for <aqm@ietf.org>; Fri, 12 Jul 2013 07:42:15 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.203]) by atl4mhob08.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r6CEgDqe018898 for <aqm@ietf.org>; Fri, 12 Jul 2013 10:42:13 -0400
Received: (qmail 9960 invoked by uid 0); 12 Jul 2013 14:42:13 -0000
X-TCPREMOTEIP: 107.46.120.178
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.46.120.178) by 0 with ESMTPA; 12 Jul 2013 14:42:12 -0000
Message-ID: <51E015AE.8080006@mti-systems.com>
Date: Fri, 12 Jul 2013 10:41:50 -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/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: grenville armitage <garmitage@swin.edu.au>
References: <51DE398B.2090103@mti-systems.com> <CAGhGL2BnTXuZejwf5C38MndMKbm+eM2ANWjJt+pwQFp89ECpFg@mail.gmail.com> <91b91547d0e717bf6376929bb55bf81f.squirrel@www.erg.abdn.ac.uk> <02FA5F0F-C331-4000-A716-D074734F56D0@telecom-bretagne.eu> <CAGhGL2ADOzEbDxCnOSa0saSYJ_iQ4MFNLYjz+VyCmnFq8x3b=w@mail.gmail.com> <201307120156.r6C1uCC8026410@bagheera.jungle.bt.co.uk> <51DF9DE7.4030103@swin.edu.au> <e01420cbe6896620018048b95417a8c9.squirrel@www.erg.abdn.ac.uk> <51DFCCD8.604@swin.edu.au>
In-Reply-To: <51DFCCD8.604@swin.edu.au>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: 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: Fri, 12 Jul 2013 14:42:21 -0000

On 7/12/2013 5:31 AM, grenville armitage wrote:
> 
> 
> On 07/12/2013 16:43, gorry@erg.abdn.ac.uk wrote:
>> I think Bob's proposal is a useful one as we move to active queue
>> management.
>>
>>   I suspect we will need to make the distinction between the two terms
>> every document / presentation though to make sure people see the
>> distinction.
> 
> Conceded. Certainly worth trying if it helps clarity of understanding.
> I was primarily wondering if trying to say "..the buffer is the fixed
> memory allocation..." stands much chance against years of classroom
> dialogue like "What does a queue do? It provides buffering....". But
> I don't hold a strong opinion wrt the proposed charter wording on
> this point.
> 


I think I agree.  This is definitely a good idea to make clear in
a "terminology" section or something in one of our WG documents, if
we then use the words consistently following that, but given that
the existing documentation in the field muddles terms, it only makes
sense for the charter to define and use them with precision, if it
makes a difference to the scoping and understanding of the work.

That said ... in the next revision, we should try to use the right
words in relevant places, but I don't think the charter is the place
we want to carve any terminology in stone.

-- 
Wes Eddy
MTI Systems