Related questions with answers


In our discussion of TCP congestion control in earlier Section, 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 t1t_1. TCP remains idle for a relatively long period of time and then wants to send more data at t2t_2. What are the advantages and disadvantages of having TCP use the cwnd and ssthresh values from t1t_1 when starting to send data at t2t_2 ? What alternative would you recommend? Why?


Answered 1 year ago
Answered 1 year ago
Step 1
1 of 2

In this case, we can say that since our system is not memoryless, which saves us time for realizing the limitation of the cwnd by slow-start phase. The drawback here is that the value which is true for t1t_{1} may not be true for t2t_{2} which can cause the system overload or system underperformance.

Create an account to view solutions

Create an account to view solutions

More related questions