|
TCP Non-Contiguous Acknowledgment Handling and Selective Acknowledgment (SACK)
(Page 3 of 4)
There Is No Ideal Answer
Since TCP doesn't know whether these
other segments showed up, it cannot know which method is better. It
must simply make an executive decision to use one approach
or the other, and hope for the best. In the example of the previous
topic, as shown in Figure 223,
I demonstrated the conservative approachonly the lost
segment of the file was retransmitted. In contrast, Figure 224
shows the aggressive approach to retransmission.
Figure 224: TCP Aggressive Retransmission Example This example is the same as that of Figure 223 except that here the server is taking an aggressive approach to retransmitting lost segments. When segment #3 times out, both #3 and #4 are retransmitted and their retransmission timers restarted. (In this case #4 already arrived so this extra transmission was not useful.)

|
Key Concept: There are two approaches to handling retransmission in TCP. In the more conservative approach, only the segments whose timers expire are retransmitted; this saves bandwidth but may cause performance degradation if many segments in a row are lost. The alternative is that when a segments retransmission timer expires, both it and all subsequent unacknowledged segments are retransmitted. This provides better performance if many segments are lost but may waste bandwidth on unnecessary retransmissions. |
| If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |
|
|
Home -
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.
|