Protocols
Saved & recent

Selective acknowledgment

Also called: SACK, TCP SACK, SACK block

TCP selective acknowledgment, or SACK, lets a receiver report ranges of bytes that arrived beyond a gap in the ordered stream. Ordinary cumulative acknowledgments still identify the first byte not yet received in sequence. The extra range information helps the sender identify missing data and recover losses without unnecessarily retransmitting every later byte.

For example, if bytes 2,000–2,999 are missing but 3,000–3,999 arrived, the receiver can send cumulative ACK 2000 plus a SACK block [3000, 4000). The block’s right edge names the byte after the received range. SACK support is negotiated during connection setup. Acknowledging later bytes does not allow the application to bypass TCP’s in-order delivery requirement.

Read first
TCP
Related
TCP handshake, Head-of-line blocking, Congestion control
Further reading
IETF RFC 2018 — TCP Selective Acknowledgment Options
receiver byte ranges 1000–1999 2000–2999 3000–3999 missing bytes received beyond gap sender receiver ACK 2000 · SACK [3000, 4000) next expected byte · selective range 2000–2999 targeted retransmission SACK right edge exclusive
Illustrative TCP feedback: the cumulative ACK marks the gap, while a SACK block reports later bytes already received.

View in the full Protocols collection