Internet Core Protocols by Eric A. Hall The following changes were made in the 5/00 reprint: Here's a key to the markup: [page-number]: serious technical mistake {page-number}: minor technical mistake : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification {xvi} The symbol used to represent a router in figure P-1 was replaced by the router symbol in P-2. (40) In the first paragraph, the sentence that read: "neither of these protocols work well enough to support a significant number of networks," now reads: "neither of these protocols works well enough..." {47} The symbol used to represent a router in figure 2-7 was replaced by the router symbol in P-2. (129) In the last paragraph, the sentence that read: "one of the biggest problems that come from devices that maintain..." now reads: "one of the biggest problems that comes from devices...". {151} In the last paragraph of p. 151, the author stated, "In addition, all IGMPv2 messages must use the Router Alert Option in the header of the IP datagram." "must" was changed to "should", and the following text was added: "according to RFC 2236, although many implementations do not follow this suggestion." {152} The first paragraph on p. 152 stated, "Figure 4-6 shows an IGMPv2 Membership Query message..." The following text was added: "Note that this IP packet does not have the Router Alert Option, as suggested by RFC 2236 for IGMPv2 messages." {180} The symbol used to represent a router in figure 5-3 was replaced by the router symbol in P-2. {185} The symbol used to represent a router in figure 5-5 was replaced by the router symbol in P-2. {190} The symbol used to represent a router in figure 5-7 was replaced by the router symbol in P-2. {204} The two occurances of port "1051" on page 204 were replaced with "port "1112." Note that there were separate occurrances of this error in the last two paragraphs. {215} Figure 5-21 showed a an ICMP error message when it was supposed to show an ICMP query message. The changes are as follows: The line above the horizontal scroll bar now reads: 000000 102 Krill Greywolf ICMP Echo Req ID=49153 SN=0 The Internet Protocol section now reads: ... Total Packet Length 84 bytes Packet Id 1577 ... Time to Live 64 seconds/hops ... Checksum 0xDEC1 (Correct) Source Address Greywolf Destination Address Krill No IP Options 64 bytes of data The Internet Control Message Protocol section now reads: Type 8 (Echo Request) Code 0 Checksum 0x8907 (Correct) Id 49153 Sequence 0 [56 byte(s) of data] The hex values have also changed. {233} Figure 5-32 was changed as follows: At the end of the line above the first horizontal scroll bar, "SN=0" was changed to "SN=512". The Internet Control Message Protocol section now reads: ... Checksum 0xB318 ... Sequence 512 [56 byte(s) of data] The hex values in this figure have also changed. {384} Table 7-11 was changed to the following: Table 7-11. Possible Window sizes, based on the maximum number of bits in flight and the available MTU Bits-per-Second Latency Bits Bytes MTU Window 19.2 kb/s (modem) .060 sec. 1,180 148 1460 * 4 5,840 19.2 kb/s (modem) .120 2,360 295 1460 * 4 5,840 53 kb/s (modem) .060 3,257 408 1460 * 4 5,840 53 kb/s (modem) .120 6,513 815 1460 * 4 5,840 64 kb/s (satellite) .200 13,108 1,639 536 * 4 2,144 (fast) 64 kb/s (satellite) .400 26,215 3,277 536 * 8 4,288 (normal) 384 kb/s (DSL) .060 23,593 2,950 1468 * 4 5,840 384 kb/s (DSL) .120 47,186 5,899 1460 * 6 8,760 1.5 mb/s (T-1) .060 94,372 11,797 1460 * 10 14,600 1.5 mb/s (T-1) .120 188,744 23,593 1460 * 18 26,280 10 mb/s (Ethernet) .002 20,972 2,622 1024 * 4 4,192 (local) 10 mb/s (Ethernet) .010 104,858 13,108 1460 * 10 14,600 (multi-hop) 100 mb/s (Ethernet) .002 209,716 26,215 1460 * 18 26,280 (local) 100 mb/s (Ethernet) .010 1,048,577 131,073 1460 * 90 131,400 (multi-hop)