Episode 85: Bufferbloat

Katherine Druckman and Doc Searls talk to Dave Taht about bufferbloat, latency, and the issues plaguing our networks.

Reality 2.0 around the web:
Site/Blog/Newsletter
FaceBook
Twitter
YouTube
Mastodon

Special Guest: Dave Taht.

Support Reality 2.0

Links:

• dtaht (Dave Täht) · GitHub
• Postcards from the Bleeding Edge — David Täht writes about politics, space, copyright, the internet, audio software, operating systems and surfing.
• Does my modem have Active Queue Management (AQM) for low latency? | Xfinity Community Forum — Does my modem have Active Queue Management (AQM) for low latency?
• RFC 8290 - The Flow Queue CoDel Packet Scheduler and Active Queue Management Algorithm
• Bufferbloat.net - Bufferbloat.net — Bufferbloat is the undesirable latency that comes from a router or other network equipment buffering too much data.
• Cerowrt Wiki - Bufferbloat.net — The CeroWrt Project is complete. The last build (3.10.50-1) was released in July 2014. The principles learned from that research project have been transferred to the Linux kernel and OpenWrt.
• The congestion-notification conflict [LWN.net] — Most of the time, the dreary work of writing protocol standards at organizations like the IETF and beyond happens in the background, with most of us being blissfully unaware of what is happening. Recently, though, a disagreement over protocols for congestion notification and latency reduction has come to a head in a somewhat messy conflict. The outcome of this discussion may well affect how well the Internet of the future works — and whether Linux systems can remain first-class citizens of that net.
• Objections to L4S WGLC — This document is a companion to a pair of slides presented at the IETF-111 TSVWG session. Due to time and space constraints, the slides could only contain a bare listing of the most pertinent, purely technical issues. This document illustrates and links to concrete data supporting the relevance of those issues, and amplifies them with further relevant issues. The bullet points from the slides are quoted, followed by supporting material.
• Edward Bernays - Wikipedia
• Operational Guidance for Deployment of L4S in the Internet — This document is intended to provide guidance in order to ensure successful deployment of Low Latency Low Loss Scalable throughput (L4S) in the Internet. Other L4S documents provide guidance for running an L4S experiment, but this document is focused solely on potential interactions between L4S flows and flows using the original ('Classic') ECN over a Classic ECN bottleneck link. The document discusses the potential outcomes of these interactions, describes mechanisms to detect the presence of Classic ECN bottlenecks, and identifies opportunities to prevent and/or detect and resolve fairness problems in such networks. This guidance is aimed at operators of end-systems, operators of networks, and researchers.