All technical documents have errors, and The TCP/IP Guide is no exception. For your convenience, I list here any mistakes or issues that have been identified in published versions of the Guide. Any errata listed for the most recent version of The TCP/IP Guide will be corrected in the next version.

Note that only technical errors are listed here; typos and minor non-content errors are marked for correction in my source document, but not listed here (as they are not essential to know in order to understand the material, and would clutter the list.)

NOTE: These errata are for the electronic version of The TCP/IP Guide. For errata covering The TCP/IP Guide print book, please see this page instead.

Version 3.0

This is the latest version of the electronic edition. The following errata have been identified; the page number refers to the page in the downloadable TCP/IP Guide PDF; the link for the page number goes to the matching page in the online edition:

• Page 63: "concepts of seven stacked layers" should read "consists of seven stacked layers".
• Page 378: "The total number of hosts needed is thus 196" should read "The total number of hosts needed is thus 190".
• Page 399: In Figure 80, the last octet in the binary representation of Subnet #0, Host #2 is shown as "00000001" when it should be "00000010".
• Page 1025: "Finally, if an amount of time equal to Expires seconds elapses, the master name server will stop serving data from the zone until it re-establishes contact with the primary name server." should read "Finally, if an amount of time equal to Expires seconds elapses, the slave name server will stop serving data from the zone until it re-establishes contact with the primary name server.".
• Page 1109: "In fact, the successor to RFC 1497 is RFC 1533, which officially merges BOOTP vendor extensions and BOOTP options into the same standard." should read "In fact, the successor to RFC 1497 is RFC 1533, which officially merges BOOTP vendor extensions and DHCP options into the same standard.".
• Page 1117: In Table 187, in the row for the field "CHAddr", "address of the client sending a BOOTREPLY" should read "address of the client sending a BOOTREQUEST".
• Page 1291: In Table 224, the encoding "%26" is shown as corresponding to the "%" character; it really is for the "&" character.

NOTE: Versions 1.0 and 2.0 contained numerous errors and small problems, only some of which were documented here. Those who purchased those versions should contact me for a free download of version 3.0.

© 2003-2017 Charles M. Kozierok. All Rights Reserved.