QoS for system critical packets on wireless

Dave Taht dave.taht at gmail.com
Wed Jun 22 20:00:20 PDT 2011


On Wed, Jun 22, 2011 at 8:48 PM, Jim Gettys <jg at freedesktop.org> wrote:
> On 06/22/2011 11:17 AM, Dave Taht wrote:
>>
>> The biggest fallout of the diffserv work I was trying was observing
>> that most packets fell into one of 3 buckets:
>>
>> 1) System control and 'MICE' are<  less than 1% of all packets. Mice
>> includes a bunch of messages like ARP, NTP, UDP, and most of the icmp6
>> portion of the stack, in what I'm doing currently. Mice are
>> desperately needed for the network to continue to function.
>
> I'd not use this term: please call it something else.
>
> Van and Kathy have talked about HTTP "mice" and "elephant" TCP flows for a
> long time, and you'll terminally confuse everyone if you call these items
> "mice".

I totally agree that overloading 'mice' is the wrong thing to do. mice
is a very useful category defined as 'short tcp streams', and well
discussed that way in the existing TCP literature.

I think I've settled on ANT, but lack a suitable backronym. Ants do
useful stuff, taking care of cleaning up and organizing the universe.
They are orderly, and hard to see,
and can lift enormous things despite their size.

Given my radio background I dislike it because it's short for antenna,
but 'bee is confusing, and hard to spell, bird is the name of a
routing daemon, and I'm plumb out of ideas lacking other analogies...



>                - Jim
>
> _______________________________________________
> Bloat-devel mailing list
> Bloat-devel at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat-devel
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com


More information about the Bloat-devel mailing list