UDP fills the same (overlarge) buffers before it can be sent over a link; it can be stalled by misbehaving TCP. Since TCP still dominates bandwidth usage, TCP b

UDP fills the same (overlarge) buffers before it can be sent over a link; it can be stalled by misbehaving TCP. Since TCP still dominates bandwidth usage, TCP bufferbloat needs to be fixed for UDP to have a chance at low latency. Also, if a UDP application can possibly use a significant share of the bottleneck bandwidth, it will need its own latency feedback to avoid being another cause of bufferbloat. Whatever fills the buffer has no bearing on the outcome in most cases (most buffers are just for ethernet retransmission and routers don't manage them; the exceptions I know are with AQM and QoS).