An Extension to the Selective Acknowledgement (SACK) Option for TCP

By Sally Floyd, J. Mahdavi, M. Mathis, Matthew Podolsky. Request for Comments, 2000

505 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

A measurement-based study of MultiPath TCP performance over wireless networks (2013, methodology): “We use Linux’s default initial window size of 10 packets and apply TCP Selective Acknowledgement (SACK) [7].”
Scalable TCP: improving performance in highspeed wide area networks (2003, methodology): “This kernel implements a sophisticated TCP stack supporting the following relevant standards: TCP extensions for high performance11 [10], SACK [7], and D-SACK [8].”
Low-rate TCP-targeted denial of service attacks and counter strategies (2003, methodology): “Further improvements are obtained by TCP SAC K [13] when a large number of packets are dropped from a window of data [7] because when a SACK receiver holds non-contiguou s data, it sends duplicate ACKs bearing the SACK option to info rm the sender of the segments that have been correctly received .”
The Eifel algorithm: making TCP robust against spurious retransmissions (2000, background): “Waiting for the receiver signal in DUPACKs that is has correctly received duplica segments, as proposed in [6], would be too late (see Figure and is thus not an alternative.”