Re: [aqm] updated draft charter

gorry@erg.abdn.ac.uk Fri, 12 July 2013 06:43 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 E3A0521F9D7B for <aqm@ietfa.amsl.com>; Thu, 11 Jul 2013 23:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.423
X-Spam-Level:
X-Spam-Status: No, score=-106.423 tagged_above=-999 required=5 tests=[AWL=-0.051, 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 0Q9Uky6Xtm5S for <aqm@ietfa.amsl.com>; Thu, 11 Jul 2013 23:43:45 -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 2AD6821F9D68 for <aqm@ietf.org>; Thu, 11 Jul 2013 23:43:45 -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 6B9FC2B44A7; Fri, 12 Jul 2013 07:43:42 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Fri, 12 Jul 2013 07:43:42 +0100
Message-ID: <e01420cbe6896620018048b95417a8c9.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <51DF9DE7.4030103@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>
Date: Fri, 12 Jul 2013 07:43:42 +0100
From: gorry@erg.abdn.ac.uk
To: grenville armitage <garmitage@swin.edu.au>
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: 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 06:43:50 -0000

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.

Gorry

>
>
> On 07/12/2013 11:56, Bob Briscoe wrote:
> 	[..]
>> 3/ "routers, ... include buffers or queues" Buffers and queues are
>> not members of the same set (IMO). I don't think this is a picky
>> terminology point. Can we adopt the convention that the buffer is the
>> fixed memory allocation (hardware or software), and the queue is the
>> software construct within the buffer?
>
> The distinction would be an interesting one to make, but hasn't
> horse bolted on this many years ago?  IMO, there's lots of history
> behind the notion that a buffer is the space used to absorb
> transient overloads (regardless of how implemented) and a queue
> is a either a synonym for buffer or a particular subset (e.g. a
> FIFO buffer).
>
> cheers,
> gja
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>