Hello All,
In the network traces that I have seen which record spurious retransmissions there is another characteristic that I mentioned as an aside, namely that "ack only" packets tend to appear in "bunches" with sub-microsecond spacing between the packets. I did not place too much emphasis on this because the process of capturing trace data can introduce "artefacts" (characteristics that would not be present if one could monitor the low-level signalling of the messages).
Whilst doing some background reading, I found this article by Christian Huitema: Implementing Cubic congestion control in Quic. In the section on "Spurious retransmissions", he writes:
If you look closely at the graph of RTT above, you will see a number of vertical bars with multiple measurements happening at almost the same time. This is a classic symptom of “ACK compression”. Some mechanism in the path causes ACK packets to be queued and then all released at the same time.
This gives a name ("ACK compression") to the bunching that can be researched in the Web. Christian was writing about apply Cubic to HTTP/3 (UDP), but it is equally relevant to its use with TCP.
The use of the expression "Some mechanism in the path" is compatible with my belief that the source of the problem being discussed in this thread is beyond our control and that additional mechanisms are needed in the Windows implementation to compensate for it (e.g. undoing reductions in the congestion window caused by spurious retransmissions).
Gary