SHARE
SPREAD
HELP

The Tradition of Sharing

Help your friends and juniors by posting answers to the questions that you know. Also post questions that are not available.


To start with, Sr2Jr’s first step is to reduce the expenses related to education. To achieve this goal Sr2Jr organized the textbook’s question and answers. Sr2Jr is community based and need your support to fill the question and answers. The question and answers posted will be available free of cost to all.

Computer Networking : A Top-Down Approach

Computer Networking : A Top-down Approach

Authors:
James F. Kurose, Keith W. Ross
Exercise:
Problems
Chapter:
Transport Layer
Edition:
6
ISBN:
9780132856201
Question:
54

 

Question

In our discussion of TCP congestion control in Section 3.7, we implicitly assumed that the TCP sender always had data to send. Consider now the case that the TCP sender sends a large amount of data and then goes idle (since it has no more data to send) at t 1 . TCP remains idle for a relatively long period of time and then wants to send more data at t 2 . What are the advantages and disadvantages of having TCP use the cwnd and ssthresh values from t 1 when starting to send data at t 2 ? What alternative would you recommend? Why?

Answer

An advantage of using the earlier values of cwnd and ssthresh at t2 is that TCP would not have to go through slow start and congestion avoidance to ramp up to the throughput value obtained at t1. A disadvantage of using these values is that they may be no longer accurate. In particular, if the path has become more congested between t1 and t2, the sender will send a large window’s worth of segments into an already (more) congested path.

1 0

Discussions

Omar Hadeed

Advantages of using t1’s CWND & ssthresh

Disadvantages of using t1’s CWND & ssthresh

If the network was NOT caught in congestion between t1 and t2 then the user is able to restore the same performance of the network at t1

If the network was caught in congestion between t1 and t2, the sender will be presented with two scenarios. Scenario one is to wait for three duplicate ACKs (Reno) and go into Fast Recovery (ssthresh= cwnd/2, cwnd = ssthresh + 3 MSS). Scenario two is to timeout and go into slow-start (ssthresh =cwnd/2, cwnd = 1 MSS). The problem with both of these scenarios is that they are still based on cwnd from t1 which is not consistent with the changes that may have occurred between t1 and t2.

 

My solution: is to use Fast Recovery at t2, that is to send three packets and wait for three-duplicate ACKs. When the ACKs are received, proceed by setting ssthresh = cwnd/2 and cwnd = ssthresh + 3 MSS. This solution gurantees average performance regardless of congestion between t1 and t2.

Post the discussion to improve the above solution.