Cheatsheet: Difference between revisions

Content added Content deleted
Line 235: Line 235:
* Both consider RTO and Duplicate ACKs as packet loss events.
* Both consider RTO and Duplicate ACKs as packet loss events.
* Behavior of Tahoe and Reno differ primarily in how they react to duplicate ACKs.
* Behavior of Tahoe and Reno differ primarily in how they react to duplicate ACKs.

Tahoe:
If three duplicate ACKs are received Tahoe performs a fast retransmit
Sets the slow start threshold to half of the current congestion window
Reduces the congestion window to 1 MSS
Resets to slow start state


Reno:
Reno:
If three duplicate ACKs are received, Reno will perform a fast retransmit
If three duplicate ACKs are received, Reno will
Skip the slow start phase by instead halving the congestion window (instead of setting it to 1 MSS like Tahoe),
Skip the slow start phase by instead halving the congestion window (instead of setting it to 1 MSS like Tahoe),
Setting the slow start threshold equal to the new congestion window
Setting the slow start threshold equal to the new congestion window
Line 250: Line 244:
* In both Tahoe and Reno, if an ACK times out (RTO timeout), slow start is used, and both algorithms reduce congestion window to 1 MSS.
* In both Tahoe and Reno, if an ACK times out (RTO timeout), slow start is used, and both algorithms reduce congestion window to 1 MSS.
* Four ACKs acknowledging the same packet, which are not piggybacked on data and do not change the receiver's advertised window.
* Four ACKs acknowledging the same packet, which are not piggybacked on data and do not change the receiver's advertised window.


{| class="wikitable"
|-
! Event !! Tahoe !! Reno
|-
| 3 Dup Acks || performs a fast retransmit<br> Sets the slow start threshold to half of the current congestion window<br>Reduces the congestion window to 1 MSS<br>Resets to slow start state|| perform a fast retransmit
|-
| RTOs || Example || Example
|-
| Example || Example || Example
|}


----
----