The outline of topics we’d like to address more fully is below:
Demonstration recipes for demonstrating/testing for bufferbloat
Servers
Home routers
Wifi routers
Wifi clients
Ethernet
Broadband gear
Core internet
3G wireless
Mitigations
Set end-node transmit buffers to something sane
Set QOS knobs on routers to keep broadband gear’s buffer
from filling.
Full Solutions
Fixes for routers involve AQM of some sort - Van’s modified RED
(or similar) is really necessary in wireless situations, as classic
RED isn’t easily dynamic, though one could kludge it, of course
Proper solutions for end-nodes involve some intelligence in
buffering; at a minimum control of transmit buffers and
device rings.
httping - latest version has
support for persistent connections, and therefore it is easy to test
against any web server over TCP, to defuse the (overblown) issues
around ICMP ping. Also available now in the Android marketplace.
Needed tools
a “push here to make your network become loaded” test, to drive this
home to people
a tool like pingplotter
for Linux and Mac (at least), to help identify bloated links. This
might be an elaboration of mtr:http://www.bitwizard.nl/mtr/ that
works properly.
For super, duper extra bonus points, a tool that uses the techniques
of reverse
traceroute
to identify problems on the reverse path, since many/most paths in
the Internet are asymmetric