Internet Core Protocols: The Definitive Guide by Eric A. Hall The following corrections were made to the 2/04 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 (14) At the end of the 1st paragraph: 00:00:c0:c8:b2:27 NOW READS: 00:00:c0:c8:b3:27 <41> The paragraph above the heading "Datagram Independence" previously read: For more information about hierarchical routing, refer to "Classless Inter-Domain Routing (CIDR)" in Appendix B, IP Addressing Fundamentals. NOW READS: For more information about hierarchical routing, refer to "Subnet Masks and CIDR Networks" in Appendix B, IP Addressing Fundamentals. {45} In the end of the first paragraph under the heading "Fragmentation and Reassembly," "16-megabit Token Ring" NOW READS: "16-Mb/s Token Ring." {45-46} In the first column of Table 2-5, "16 MB/s Token Ring" NOW READS "16-Mb/s Token Ring" and "4 MBs Token Ring" NOW READS "4-Mb/s Token Ring". {52} In the last paragraph, change "256 KB/s" NOW READS "256 Kb/s." {54-55} Values in Table 2-9 were inverted. The numbers HAVE BEEN CHANGED and the rows RE-ARRANGED so that the order and values are as follows: Value Service ____________________________ 0 Normal 1 Minimize Cost 2 Maximize Reliability 4 Maximize Throughput 8 Minimize Delay The descriptive text associated with the labels remain the same, but have been RE-ORDERED according to the replacement list above. {71} Table 2-12; "2 | Internet Group Message Protocol (IGMP)" NOW READS: "2 | Internet Group Management Protocol (IGMP)" {89} In the first paragraph under "Notes on Fragmentation," "16 MB/s" NOW READS "16 Mb/s". {98} The first sentence of the sixth paragraph: "ARP packets work at the data-link layer, the same as IP packets." NOW READS: "ARP packets communicate with the data-link layer directly, the same as IP packets." <184-185> The following text NOW REPLACES the previously existing paragraph under the heading "Redirect for Destination Network": This message is used when all traffic for the destination network should go through another router. This has historically been the most common form of the Redirect error message on networks that rely on Router Discovery for dynamic routing. However, this particular message was deprecated by RFC 1812, which mandated that network- wide redirect messages not be sent. <185> The following sentence HAS BEEN ADDED to the end of the description for "Redirect for Destination Network Based on Type-of-Service": "This message was also deprecated by RFC 1812." [196] The last sentence in the 2nd paragraph: "Note that RFC 1122 states that if a system receives an ICMP message with type or code that it does not understand, it must ignore the message." NOW READS: "Note that RFC 1122 states that if a system receives an ICMP message with an unknown type, it must ignore the message. Systems that implement a specific message type are expected to implement all of the codes for that type." <210> Table 5-6:. The phrase "(deprecated)" HAS BEEN ADDED to the end of the sentences describing Code 0 and Code 2. <220> The "Additional Fields" entry just above Table 5-12: "Both the Echo Request and Echo Reply query messages use four additional fields." NOW READS: "...three additional fields." {278} In Table 7-1, the descriptions for ports 20 and 21 were backwards. They NOW READ: 20 File Transfer Protocol, Data Channel (FTP-Data) 21 File Transfer Protocol, Control Channel (FTP) {290} In the 2nd paragraph under "MTU and MRU Size Considerations,": "MTU/MRU for Ethernet networks is only 1.5 kilobytes." NOW READS: "MTU/MRU for Ethernet networks is only 1500 bytes." {292} In the last sentence of the 2nd paragraph above "Path MTU Discovery,": "capable of supporting MTU sizes of 1.5 kilobytes would use..." NOW READS: "capable of supporting MTU sizes of 1500 bytes would use..." {293} In the first full paragraph on the page, the two occurrances of "1.5 kilobyte" NOW READ "1500 byte." (299) In the 4th line of the first full paragraph, "kilo398byte" NOW READS "kilobyte." (309) The second sentence in the second paragraph under the Congestion Avoidance heading: "As such, RFC 1112 states that..." NOW READS: "As such, RFC 1122 states that..." {370} Item 1 under "Interactive Data Exchange": "the Discard server's well-known port" NOW READS: "the Echo server's well-known port" {370} The last sentence of the first paragraph in item 7: "This allows the acknowledgment to the shutdown request to be trackedindependently of the request itself." NOW READS: "Since the acknowledgement is a zero-length command segment, it is using the sequence number for the next byte of data that it would normally send (although it won't be sending any more data)." {374} The first sentence in item 2: "the Chargen server on Greywolf immediately starts sending data to the Chargen client on Arachnid." NOW READS: "the Chargen server on Arachnid immediately starts sending data to the Chargen client on Greywolf." {377} The next-to-last sentence in item 26: "Although Greywolf cannot currently accept any data, it will be able to send a shutdown message, which Greywolf must be able to accept." NOW READS: "Although Greywolf cannot currently accept any data, it will be able to send a shutdown message." {380} In the last paragraph, both occurrences of "100 MB/s" NOW READ "100 Mb/s". {381} In the Note, "19.2 KB/s" NOW READS "19.2 Kb/s" and "1.5 MB/s" NOW READS "1.5 Mb/s". {381} In the paragraph below the Note, "19.2 KB/s" NOW READS "19.2 Kb/s". {381-382} In Table 7-10, all occurrences of "KB/s" NOW READ "Kb/s" and all occurrences of "MB/s" NOW READ "Mb/s". {382} In the first paragraph, "19.2 KB/s" NOW READS "19.2 Kb/s". {382} In the second paragraph, "100 mb/s" NOW READS "100Mb/s" and "10 MB/s" NOW READS "10 Mb/s". {382} In the third paragraph, "19.2 KB/s" NOW READS "19.2 Kb/s" and "10 MB/s" NOW READS "10 Mb/s". {384} In Table 7-11, all occurrences of "KB/s" NOW READ "Kb/s" and all occurrences of "MB/s" NOW READ "Mb/s". {384} In the paragraph under Table 7-11, "100 MB/s" NOW READS "100Mb/s". <388> The fifth paragraph down, beginning: "The HTTP problem is illustrated in Figure 7-47. In that example, the HTTP client is sending 1500 bytes of data to the HTTP server, but because the client is using the Nagle algorithm, the sixty bytes of overflow data are delayed until the first segment has been acknowledged." NOW READS: "The HTTP problem is illustrated in Figure 7-47. In that example, the HTTP client is sending 1500 bytes of data to the HTTP server, but because the client is using the Nagle algorithm, the forty bytes of overflow data are delayed until the first segment has been acknowledged."