TCP Selective Acknowledgment Options (1996)
| Citations: | 250 - 11 self |
BibTeX
@MISC{Mathis96tcpselective,
author = {M. Mathis and J. Mahdavi and Sally Floyd and S. Floyd and A. Romanow},
title = {TCP Selective Acknowledgment Options},
year = {1996}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
TCP may experience poor performance when multiple packets are lost from one window of data. With the limited information available from cumulative acknowledgments, a TCP sender can only learn about a single lost packet per round trip time. An aggressive sender could choose to retransmit packets early, but such retransmitted segments may have already been successfully received. A Selective Acknowledgment (SACK) mechanism, combined with a selective repeat retransmission policy, can help to overcome these limitations. The receiving TCP sends back SACK packets to the sender informing the sender of data that has been received. The sender can then retransmit only the missing data segments. This memo proposes an implementation of SACK and discusses its performance and related issues. Acknowledgements Much of the text in this document is taken directly from RFC1072 "TCP Extensions for Long-Delay Paths" by Bob Braden and Van Jacobson. The authors would like to thank Kevin Fall (LBNL), Christian...
Keyphrases
tcp selective acknowledgment option multiple packet aggressive sender kevin fall selective acknowledgment poor performance retransmitted segment round trip time selective repeat retransmission policy limited information van jacobson bob braden related issue tcp sender cumulative acknowledgment rfc1072 tcp extension single lost packet sack packet long-delay path data segment
