Sync-TCP in high-speed environments
Ayoob Khan, Dhaval M. Shah, Zhenyu Xu
Abstract
Ayoob Khan, Dhaval M. Shah, Zhenyu Xu
Abstract
The congestion control mechanism in TCP was first introduced by Jacobson in [7], which was later developed into TCP Tahoe. Since then, various end-to-end congestion control protocols have been proposed, including Reno [2], NewReno [6], SACK [4], and Vegas [3]. Among these protocols, TCP Reno is the standard congestion control algorithm for TCP traffic, according to [2]. However, TCP Reno detects congestion only when a packet loss occurs, i.e., when the sender receives duplicate acknowledgements (ACKs) or experiences a timeout. Hence, there are no explicit congestion notifications to end systems.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
The congestion control mechanism in TCP was first introduced by Jacobson in [7], which was later developed into TCP Tahoe. Since then, various end-to-end congestion control protocols have been proposed, including Reno [2], NewReno [6], SACK [4], and Vegas [3]. Among these protocols, TCP Reno is the standard congestion control algorithm for TCP traffic, according to [2]. However, TCP Reno detects congestion only when a packet loss occurs, i.e., when the sender receives duplicate acknowledgements (ACKs) or experiences a timeout. Hence, there are no explicit congestion notifications to end systems.
Key concepts: TCP Vegas, TCP Westwood plus, Compound TCP, TCP Friendly Rate Control, TCP global synchronization, Computer science, Computer network, TCP acceleration