Question: Most IP datagram reassembly
Most IP datagram reassembly algorithms have a timer to avoid having a lost fragment tie up reassembly buffers forever. Suppose that a datagram is fragmented into four fragments. The first three fragments arrive, but the last one is delayed. Eventually, the timer goes off and the three fragments in the receiver's memory are discarded. A little later, the last fragment stumbles in. What should be done with it?
Answer to relevant QuestionsIn both IP and ATM, the checksum covers only the header and not the data. Why do you suppose this design was chosen?In our example transport primitives of Fig. 6-2, LISTEN is a blocking call. Is this strictly necessary? If not, explain how a non-blocking primitive could be used. What advantage would this have over the scheme described in ...Consider the problem of recovering from host crashes (i.e., Fig. 6-18). If the interval between writing and sending an acknowledgement, or vice versa, can be made relatively small, what are the two best sender-receiver ...A client sends a 128-byte request to a server located 100 km away over a 1-gigabit optical fiber. What is the efficiency of the line during the remote procedure call?The maximum payload of a TCP segment is 65,495 bytes. Why was such a strange number chosen?
Post your question