Fast retransmit: Difference between revisions

Content deleted Content added

Inline

Revision as of 18:22, 15 August 2011

Fast Retransmit is an enhancement to TCP which reduces the time a sender waits before retransmitting a lost segment.

A TCP sender uses a timer to recognize lost segments. If an acknowledgement is not received for a particular segment within a specified time (a function of the estimated Round-trip delay time), the sender will assume the segment was lost in the network, and will retransmit the segment.

Duplicate acknowledgement is the basis for fast retransmit mechanism which works as follows: after receiving a packet (i.e., sequence number 1), the receiver usually sends an acknowledgement adding 1 with the sequence number (i.e., sequence number 2) which means that the receiver receives the packet number 1 and it expects packet number 2 from the sender. Lets assume that three packets have been lost. In the meantime the receiver receives the packet number 5. After receiving packet number 5, the receiver sends an acknowledgement with the sequence number 3 and 6. When the receiver receives packet number 6, it sends acknowledgement with the sequence number 3 and 7. In this way, the sender receives more than one acknowledgement with the same sequence number which is called duplicate acknowledgement.

The fast retransmit enhancement works as follows: if a TCP sender receives a specified number of acknowledgements which is usually set to three duplicate acknowledgements with the same acknowledge number (that is, a total of four acknowledgements with the same acknowledgement number), the sender can be reasonably confident that the segment with the next higher sequence number was dropped, and will not arrive out of order. The sender will then retransmit the packet that was presumed dropped before waiting for its timeout.

External links

Mark Allman, Vern Paxson, W. Richard Stevens (1999). "Fast Retransmit/Fast Recovery". TCP Congestion Control. IETF. sec. 3.2. doi:10.17487/RFC2581. RFC 2581. Retrieved 2010-05-01. {{citation}}: Unknown parameter |month= ignored (help)CS1 maint: multiple names: authors list (link)
TCP Congestion Handling and Congestion Avoidance Algorithms — The TCP/IP Guide

This computer networking article is a stub. You can help Wikipedia by expanding it.

@@ Line 5: / Line 5: @@
 A TCP sender uses a timer to recognize lost segments. If an acknowledgement is not received for a particular segment within a specified time (a function of the estimated [[Round-trip delay time]]), the sender will assume the segment was lost in the [[Computer network| network]], and will retransmit the segment.
+Duplicate acknowledgement is the basis for fast retransmit mechanism which works as follows: after receiving a packet (i.e., sequence number 1), the receiver usually sends an acknowledgement adding 1 with the sequence number (i.e., sequence number 2) which means that the receiver receives the packet number 1 and it expects packet number 2 from the sender. Lets assume that three packets have been lost. In the meantime the receiver receives the packet number 5. After receiving packet number 5, the receiver sends an acknowledgement with the sequence number 3 and 6. When the receiver receives packet number 6, it sends acknowledgement with the sequence number 3 and 7. In this way, the sender receives more than one acknowledgement with the same sequence number which is called duplicate acknowledgement.
-The fast retransmit enhancement works as follows: if a TCP sender receives three duplicate acknowledgements with the same acknowledge number (that is, a total of four acknowledgements with the same acknowledgement number), the sender can be reasonably confident that the segment with the next higher sequence number was dropped, and will not arrive out of order. The sender will then retransmit the packet that was presumed dropped before waiting for its timeout.
+The fast retransmit enhancement works as follows: if a TCP sender receives a specified number of acknowledgements which is usually set to three duplicate acknowledgements with the same acknowledge number (that is, a total of four acknowledgements with the same acknowledgement number), the sender can be reasonably confident that the segment with the next higher sequence number was dropped, and will not arrive out of order. The sender will then retransmit the packet that was presumed dropped before waiting for its timeout.
 == External links ==