On Wednesday, October 7, 2015 2:00 PM, [email protected] wrote: > That's the real engineering challenge. Modularity is your friend when > engineering > large systems with very broad requirements. Focusing on a very narrow issue, > especially > one that assumes way too much about what should be allowed and what traffic > "must" > look like, misses the point.
This ACK thinning "optimization" obviously does not work with encrypted transports like QUIC. The network may see that some packets are short and some are long, but it cannot tell whether the short Packets are ACK or some other management data. Quite often, they will be both. According to our friends at Google, a fairly large part of the traffic from and to the Chrome browser now uses QUIC. If the uplink in DOCSIS networks is so limited that it would not work without ACK thinning, that would be a problem for QUIC -- and very much an illustration of Dave's "real engineering challenge." I wonder whether QUIC telemetry shows specific issues caused by congestions of the DOCSIS uplinks. -- Christian Huitema _______________________________________________ aqm mailing list [email protected] https://www.ietf.org/mailman/listinfo/aqm
