Consider an application has 100 bytes to send. The application generates 10 byte
ID: 3864050 • Letter: C
Question
Consider an application has 100 bytes to send. The application generates 10 bytes of data at a time in each 10 milliseconds interval and passes them to the TCP layer. To simplify the analysis, assume:
Draw a diagram to show when TCP sends the (data and ACK) segments and how many bytes each data segment carries. Does any segment carry the Maximum Segment Size?
Explanation / Answer
Our TCP Options are Maximum Segment Size, Window Scale, SACK permitted, and Timestamps. Each of these Options is used in both directions. There are also the NOP and End of Option List formatting options. Here is an example of a FIN teardown: Figure 6: Time sequence diagram for FIN teardown Points to note: The teardown is initiated by the computer; it might also be initiated by the server. Like the SYN, the FIN flag occupies one sequence number. Thus when the sequence number of the FIN is 192, the corresponding Ack number is 193. Your sequence numbers will vary. Our numbers are relative (as computed by Wireshark) but clearly depend on the resource that is fetched. You can tell that it is around 1 MB long. The RTT in the FIN exchange is similar to that in the SYN exchange, as it should be. Your RTT will vary depending on the distance between the computer and server as before.