[Bloat] The bigger picture: whats components are used together to fight bloat

[Jeroen Balduyck]

I hope I can get a bit more information on what comprises the total
solution. But knitting it together proves a bit hard (for me at least).
Without this, it is hard to follow the discussions on the list. Has anyone
made a summary of how all of this works together?

So:

1. In order to move the bottleneck to a device under our administrative
control, we need to shape traffic (we need to become the bottleneck).
2. Next, we have the AQM-algorithms that manage the (or a) queue.
3. And then there are still issues with multiple flows and with UDP?

>From what I understand, we need to shape traffic, and then drop packets
taking into account that the most aggressive flow (the flow that
contributes the most to filling a buffer), is the flow that will get the
most packets dropped. This to prevent the aggressive flow from impacting
flows that behave better.

Now for UDP, is the problem here that we cannot identify flows, and hence,
only have one queue for UDP whereas for TCP we can have multiple?

Any good resources are more than welcome:-)!

Thanks,
Jeroen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20130502/91354b48/attachment-0002.html>