Re: [tcpm] RFC 2883 (D-SACK), Section 5.1 Replication by the network

Alexander Zimmermann spake unto us the following wisdom:
> RFC 2883, Section 5.1 states that without D-SACK a TCP sender would
> not know that a packet had been replicated in the network if the last  
> ACK was piggybacked on a data packet.
>
> According 2581(bis) a TCP receiver should send immediately an DUPACK
> when an out-of-order segment arrives. Furthermore, 2581bis says that a
> DUPACK carries no data.
>
> So, according to the DUPACK definition of 2581bis it seems to me that we
> have no problem to detect a packet replication in case D-SACK is not
> present. Right?

The problem here is that you have no idea whether the dupack was
generated by a packet already received (entirely below RCV.NXT), or a
packet following a lost or as yet un-received packet (entirely beyond
RCV.NXT).  Both of these conditions generate a duplicate
acknowledgment.

Ethan

-- 
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764

Re: [tcpm] RFC 2883 (D-SACK), Section 5.1 Replication by the network

Attachment: signature.asc