Re:Why TCP Timers Don’t Work Well (1986) [pdf]
by fanf2 on Sunday November 08, 2020 @09:04AM
(#25025880)
Traditionally in TCP the receiver ACKs the last sequence number before any missing packets. When it receives packets out of order it responds by sending duplicate ACKs. This causes the sender to retransmit the packets after the ACK’s sequence number. If there’s no loss, just reordering, then this retransmission is a waste.
There is a SACK (selective acknowledgement) TCP extension which allows a receiver to say in more detail which packets have been received, to handle reordering more efficiently. But even so, network engineers try hard to avoid anything that can cause reordering: for instance, ECMP (equal cost multipath) balances traffic load across multiple links using a hash of the TCP quadruple to ensure that each flow follows a consistent path.
This really falls down not to TCP but IP and the protocols below it. TCP if for when a packet get’s lost somewhere along the line not for transmission errors over a wireless channel.