What happens to the TCP congestion window size immediately after a packet loss is detected by triple duplicate acknowledgments?
Think about how TCP reacts to moderate congestion signals without restarting completely.
When triple duplicate ACKs are received, TCP performs fast retransmit and fast recovery. It halves the congestion window size to reduce load and enters congestion avoidance to cautiously increase the window again.
During the TCP slow start phase, how does the congestion window size change with each round-trip time (RTT)?
Slow start aims to quickly find the network capacity by rapidly increasing the window.
In slow start, the congestion window doubles every RTT because it increases by one segment for every ACK received, effectively doubling the window each round.
How does an increase in network round-trip time (RTT) affect the TCP congestion control performance?
Consider how RTT influences the feedback loop speed in TCP.
TCP relies on acknowledgments to adjust its congestion window. Higher RTT means acknowledgments arrive slower, so window growth slows, reducing throughput.
Which key difference distinguishes TCP Reno from TCP Tahoe in handling packet loss?
Think about how each version recovers from packet loss without restarting completely.
TCP Reno improves on Tahoe by using fast recovery to avoid slow start after triple duplicate ACKs, halving the window instead of resetting it.
Consider two TCP connections: one detects packet loss via timeout, the other via triple duplicate ACKs. Which connection typically achieves higher throughput and why?
Think about how quickly each method allows TCP to resume sending data after loss.
Triple duplicate ACKs allow fast retransmit and fast recovery, reducing the congestion window less and resuming transmission faster than timeout-based detection, which causes slow start.