Internet Core Protocols: The Definitive Guide
by Eric A. Hall


The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

If you have technical questions or error reports, you can send them to 
booktech@oreilly.com. (Please specify the printing date of your copy.)


This page was last updated March 26, 2007. 


Here's a key to the markup:

        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification


UNCONFIRMED errors and comments from readers:


{VI}  UDP Header Checksum calculation;
You tell about the checksum field of UDP (and IP /TCP as well), but you
donīt report how this field is calculated.


{99}  first complete paragraph;
An ARP request packet contains all F's in the target hardware address field, thus
indicating a broadcast, instead of all zeroes as the author indicates.


{128}  4th paragraph;
"...., any device that was using the IP address specified in the Destination Hardware Address field could respond to the request wi
th a unicast ARP response packet."  
 
It should be as follows:
 
"..., any device that was using the IP address specified in the Destination PROTOCOL Address field could....."


(131)  Table 3-1;
The usage notes for Source IP Address and Destination IP Address
state
 "This field's value will be 4 when IP is in use"

It should state

 "This fields' value will be 4 bytes long when IP is in use
  and contain the <source | dest> IP address"


(135)  Relevant RFCs;
"2236 (IMGP v2)" should be written as 
"2236 (IGMP v2)"


{215}  Figure 5-21;
Figure 5-21 is supposed to show a simple ICMP query message, instead it 
shows the ICMP error message from the examples before.


{230}  last paragraph (above Fig. 5-29);
"For example, Figure 5-29 shows an ICMP Destination Unreachable: Host 
Unreachable Error message..." should either read "For example, Figure 5-29 
shows an ICMP Destination Unreachable: Port Unreachable Error message..." 
or the Figure 5-29 needs to be changed accordingly.


{258}  4th paragraph;
In second paragraph in the UDP Header section, the first sentence reads:

"A UDP message is made up of six fields (counting the data portion of the message)."

It should read (my emphasis):

"A UDP message is made up of *five* fields (counting the data portion of the
message)."


(274)  2nd paragraph from bottom of page;
"Application are assigned 16-bit port numbers..."

should read:

"Applications are assigned 16-bit port numbers..."


{381}  Note;
This note is plain wrong. Kbps and Mbps are based on 1000 and
1000000 bits, respectively, not 1024 and 1024*1024. The decimal
interpretation is certainly true for 10 and 100 Mbps Ethernet.
I don't know of any media for which the binary interpretation
would be correct.