How does TCP Reno and TCP Vegas compare in terms of fairness?

How does TCP Reno and TCP Vegas compare in terms of fairness?

TCP Vegas enhances the congestion avoidance algorithm of TCP Reno. In essence, TCP Vegas dynamically increases/decreases its sending window size according to observed RTTs (Round Trip Times) of sending packets, whereas TCP Tahoe/Reno continues increasing its window size until packet loss is detected.

What TCP congestion control does Windows use?

Compound TCP
Compound TCP maintains two congestion windows: a regular AIMD window and a delay-based window.

What’s the difference between TCP and TCP Vegas?

While TCP Vegas senses the congestion in the network before any packet loss occurs and instantly it decreases the window size. So, TCP Vegas handles the congestion without any packet loss occur. TCP Vegas uses round trip time for the increase or decrease of the congestion window.

Who is the creator of TCP Las Vegas?

TCP Vegas is a TCP congestion avoidance algorithm that emphasizes packet delay, rather than packet loss, as a signal to help determine the rate at which to send packets. It was developed at the University of Arizona by Lawrence Brakmo and Larry L. Peterson and introduced in 1994.

How is congestion detected in TCP Las Vegas?

TCP Vegas detects congestion at an incipient stage based on increasing Round-Trip Time (RTT) values of the packets in the connection unlike other flavors such as Reno, New Reno, etc., which detect congestion only after it has actually happened via packet loss. The algorithm depends heavily on accurate calculation of the Base RTT value.

How does TCP Reno and TCP Tahoe work?

TCP Reno and TCP Tahoe models can determine the congestion in the network only when there some packet loss occurred in the system. So in these models, we have compensated for the packet to sense the congestion in the network. In these models when packet loss occurs the window size is decreased and the system enters the congestion avoidance phase.