Re: [aqm] updated draft charter

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.

cheers,
gja

>
> 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
>>
>
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>

-- 
Professor Grenville Armitage
Director, Centre for Advanced Internet Architectures
Faculty of Information and Communication Technologies
Swinburne University of Technology, Australia
http://caia.swin.edu.au