7. What is the length (header plus payload) of each of the first four data-carrying TCP segments? 8. What is the minimum amount of available buffer space advertised to the client by gaia.cs.umass.edu among these first four data-carrying TCP segments?? Does the lack of receiver buffer space ever throttle the sender for these first four data- carrying segments? 9. Are there any retransmitted segments in the trace file? What did you check for (in the trace) in order to answer this question? 10. How much data does the receiver typically acknowledge in an ACK among the first ten data-carrying segments sent from the client to gaia.cs.umass.edu? Can you identify cases where the receiver is ACKing every other received segment (see Table 3.2 in the text) among these first ten data-carrying segments? 11. What is the throughput (bytes transferred per unit time) for the TCP connection? Explain how you calculated this value. Answer the following question for the TCP segments in the packet trace tcp-wireshark- tracel-1 (sce carlier footnote) 12. Use the Time-Sequence-Graph(Stevens) plotting tool to view the sequence number versus time plot of segments being sent from the client to the gaia.cs.umass.edu server. Consider the flects of packets sent around t = 0.025,1 = 0.053, 1 = 0.082 and 1= 0.1. Comment on whether this looks as if TCP is in its slow start phase, congestion avoidance phase or some other phase. Figure 6 shows a slightly different view of this data. 13. These "fleets of segments appear to have some periodicity. What can you say about the period? 14. Answer each of two questions above for the trace that you have gathered when you transferred a file from your computer to gaia.cs.umass.edu