Understanding TCP/IP Model Internals and Interfaces
Understanding TCP/IP Model Internals and Interfaces
Understanding TCP/IP Model Internals and Interfaces
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
1508 <strong>Underst<strong>and</strong>ing</strong> <strong>TCP</strong>/<strong>IP</strong> <strong>Model</strong> <strong>Internals</strong> <strong>and</strong> <strong>Interfaces</strong><br />
___________<br />
4. How many times was a slow start performed during the session lifetime? ___________<br />
Retransmission Pattern<br />
Examine Sequence number of forwarded <strong>and</strong> dropped segments graph to answer the following.<br />
5. How many segments were retransmitted? ___________<br />
6. Were any segments retransmitted unnecessarily? ___________<br />
7. When was the last segment sent? ___________<br />
Detailed Analysis<br />
Sequence Numbers <strong>and</strong> ACK Numbers<br />
Note: Segments are identified by their segment sequence numbers (e.g., segment 1, 2…) In the<br />
following text, the term “ACK for segment X” means that segment X has been received successfully<br />
<strong>and</strong> the next expected segment is segment X + 1.<br />
The server retransmits segment 23 after it has received a third duplicate ACK <strong>and</strong> set its congestion<br />
window to one MSS. After the client receives the retransmitted segment, it also processes the<br />
previously received segments 24, 25, <strong>and</strong> 26 <strong>and</strong> sends an ACK acknowledging segments 23 through<br />
26. This allows the receiver to increase its congestion window to 2 <strong>and</strong> resend segments 27 <strong>and</strong> 28.<br />
The ACK for segment 27 increases the server’s congestion window to 3 <strong>and</strong> segments 29 <strong>and</strong> 30 can<br />
be resent. The ACK for segment 28 acknowledges all segments up through segment 46 (which has<br />
sequence number 24,121). (These segments had been sent before the server received the third<br />
duplicate ACK <strong>and</strong> cut the congestion window.) The server then continues sending unsent data, but<br />
with the reduced congestion window.<br />
Notice that segments 29 <strong>and</strong> 30 were unnecessarily retransmitted, <strong>and</strong> <strong>TCP</strong> Tahoe recovers from the<br />
packet lost without retransmission timeout expiration.<br />
CONFIDENTIAL – RESTRICTED ACCESS: This information may not be disclosed, copied, or transmitted in any format without the prior written consent of OPNET Technologies, Inc.<br />
© 2010 OPNET Technologies, Inc.<br />
25