Improving fairness of TCP Vegas
International Journal of Network Management
FAST TCP: motivation, architecture, algorithms, performance
IEEE/ACM Transactions on Networking (TON)
TCP Vegas-A: Improving the Performance of TCP Vegas
Computer Communications
Exploiting adaptive window techniques to reduce TCP congestion in mobile peer networks
WCNC'09 Proceedings of the 2009 IEEE conference on Wireless Communications & Networking Conference
CODE TCP: A competitive delay-based TCP
Computer Communications
TCP-New veno: the energy efficient congestion control in mobile ad-hoc networks
EUC'06 Proceedings of the 2006 international conference on Embedded and Ubiquitous Computing
eHSTCP: enhanced congestion control algorithm of TCP over high-speed networks
IWDC'05 Proceedings of the 7th international conference on Distributed Computing
RoVegas: a router-based congestion avoidance mechanism for TCP Vegas
Computer Communications
On the fair coexistence of loss- and delay-based TCP
IEEE/ACM Transactions on Networking (TON)
| Hi-index | 0.00 |
Despite research showing the superiority of TCP Vegasover TCP Reno, Reno is still the most widely deployed variantof TCP. This predicament is due primarily to the allegedincompatibility of Vegas with Reno. While Vegas in isolationperforms better with respect to overall network utilization,stability, fairness, throughput and packet loss, and burstiness;its performance is generally mediocre in any environmentwhere Reno connections exist. Hence, there exists noincentive for any operating system to adopt TCP Vegas.In this paper, we show that the accepted (default) configurationof Vegas is indeed incompatible with TCP Reno. However,with a careful analysis of how Reno and Vegas use bufferspace in routers, Reno and Vegas can be compatible withone another if Vegas is configured properly. Furthermore,we show that overall network performance actually improveswith the addition of properly configured Vegas flows competinghead-to-head with Reno flows.