> The classic solution, from X.25, was an accumulation timer with a human > response time sized delay. That's a bad idea, but unfortunately the > people who put in delayed ACKs didn't know that. They were trying to > fix TELNET responsiveness at Berkeley, which was using a large number of > dumb terminals connected to terminal servers at the time. Delayed ACKs > with a fixed timer are useful in that situation, and in few others.
Nagle has made this point repeatedly, and it's a convincing one. Is anyone working on improving the delack algorithm? > Bufferbloat is only bad if the queuing is FIFO-dumb. It's fine to have > lots of queue space if you manage it well. Noted. -- Juliusz _______________________________________________ Bloat mailing list [email protected] https://lists.bufferbloat.net/listinfo/bloat
