There are a LOT of assumptions made when QoS systems based on marked packets is used:

- That traffic X can starve others

- That traffic X is more/most important

Our test tools are not particularly good at anything other than hammering the network (UDP or TCP).  At least TCP has a built-in congestion control.  I've seen many UDP (or even raw IP) test setups that didn't look anything like "real" traffic.

I know Dave has wanted an isochronous traffic tool that could simulate voip traffic (with in-band one-way latency/jitter/loss measurement capabilities).  

What other tools do we need, for replicating traffic types that match how these QoS types in wifi are meant to be used?  I think we're doing an excellent job of showing how they can be abused.  Abusing is pretty easy, at this point (rrul, iPerf, etc).

-Aaron Wood