This document discusses the behavior of TCP Reno and TCP Tahoe protocols based on a plot of TCP window size over time. It identifies intervals of slow start and congestion avoidance, and analyzes how the congestion window and slow start threshold values change in response to detected packet losses via triple duplicate ACKs or timeouts. The key differences between TCP Reno and Tahoe's response to losses are also summarized.
Download as DOCX, PDF, TXT or read online on Scribd
100%(1)100% found this document useful (1 vote)
356 views
TUTORIAL 2 - CHAPTER 3 (TCP Congestion Control)
This document discusses the behavior of TCP Reno and TCP Tahoe protocols based on a plot of TCP window size over time. It identifies intervals of slow start and congestion avoidance, and analyzes how the congestion window and slow start threshold values change in response to detected packet losses via triple duplicate ACKs or timeouts. The key differences between TCP Reno and Tahoe's response to losses are also summarized.
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5
TUTORIAL 2 – CHAPTER 3
Consider the following plot of TCP window size as a function
of time
Assuming TCP Reno is the protocol experiencing the
behavior shown above, please answer the following questions. In all cases, you should provide a short discussion justifying your answer. a) Identify the intervals of time when TCP slow start is operating.
b) Identify the intervals of time when TCP congestion avoidance is
operating.
c) After the 16th transmission round, is segment loss detected by a
triple duplicate ACK or by a timeout?
d) After the 22nd transmission round, is segment loss detected by a
triple duplicate ACK or by a timeout?
e) What is the initial value of ssthresh (threshold) at the first
transmission round?
f) What is the value of ssthresh at the 18th transmission round?
g) What is the value of ssthresh at the 24th transmission round?
h) Assuming a packet loss is detected after the 26th round by the
receipt of a triple duplicate ACK, what will be the values of the congestion-window size and of ssthresh?
i) Suppose TCP Tahoe is used (instead of TCP Reno), and assume
that triple duplicate ACKs are received at the 16th round. What are the ssthresh and the congestion window size at the 19th round? Answer:
a) TCP slowstart is operating in the intervals [1,6] and [23,26]
b) TCP congestion advoidance is operating in the intervals [6,16]
and [17,22]
c) After the 16th transmission round, packet loss is recognized by
a triple duplicate ACK. If there was a timeout, the congestion window size would have dropped to 1.
d) After the 22nd transmission round, segment loss is detected
due to timeout, and hence the congestion window size is set to 1.
e) The threshold is initially 32, since it is at this window size that
slow start stops and congestion avoidance begins.
f) The threshold is set to half the value of the congestion
window when packet loss is detected. When loss is detected during transmission round 16, the congestion windows size is 42. Hence the threshold is 21 during the 18th transmission round. g) The threshold is set to half the value of the congestion window when packet loss is detected. When loss is detected during transmission round 22, the congestion windows size is 26. Hence the threshold is 13 during the 24th transmission round.
h) The threshold will be set to half the current value of the
congestion window (8) when the loss occurred and congestion window will be set to the new threshold value + 3 MSS . Thus the new values of the threshold and window will be 4 and 7 respectively.
i) At 19th transmission round, Threshold is 21, and congestion
window size is 4. [Note: An early version of TCP, known as TCP Tahoe, unconditionally cuts its congestion window to 1 MSS and enters the slow-start phase after either type of loss event. The newer version of TCP, TCP Reno, cancels the slowstart phase after a triple duplicate ACK. The philosophy behind cancelling slow start in this case is that even though a packet has been lost, the arrival of three duplicate ACKs indicates that some segments (specifically, three additional segments beyond the lost segment) have been received at the sender. Thus, unlike the case of a timeout, the network is showing itself to be capable of delivering at lease some segments, even if other segments are being lost to congestion.]