IPv6 Essentials

Errata for IPv6 Essentials

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
PDF
Page xiv
second last paragraph

Sentence: "... create the foundation for a real nex-generation network." should be replaced by ... create the foundation for a real next-generation network.

tenzoo  Sep 17, 2015 
Printed
Page 159
Note

The link to the DHCP Working Group changed. old: www.ietf.org/html.charters/dhc-charter.html NEW please update: http://datatracker.ietf.org/wg/dhc

Silvia Hagen
 
Apr 19, 2015 
Printed
Page 164
second last paragraph

Sentence: "... and the router is configured to set the O-Flag (other Stateful configuration) in the Router Advertisement....." there are three opening and closing brackets around O-Flag and the term appears twice. Delete the one with the three brackets.

Silvia Hagen
 
Apr 26, 2015 
Printed
Page 167
last paragraph

second line of paragraph "..... has been accordingly configured, (O-Flag) the client ....." there are three opening and three closing brackets around the O-Flag

Silvia Hagen
 
Apr 19, 2015 
Printed
Page 181
after RFC 2492 (that is the first line)

an IPv6-relevant RFC missing. Please add the following line (in correct number sequence, so after RFC 2492: RFC 2545 - Ā«Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain RoutingĀ», 1999

Silvia Hagen
 
Apr 10, 2015 
Printed
Page 191
Paragraph on ISAKMP

RFC 5996 must be RFC 7296

Silvia Hagen
 
Aug 15, 2015 
Printed
Page 192
Paragraph just below title IKEv2

RFC 5996 must be replaced by RFC 7296 RFC 4306 must be replaced by RFC 5996

Silvia Hagen
 
Aug 15, 2015 
Printed
Page 193
introduction paragraph to list in lower part

RFC 5996 must be replaced by RFC 7296

Silvia Hagen
 
Aug 15, 2015 
Printed
Page 203
first paragraph

RFC 5996 must be replaced by RFC 7296

Silvia Hagen
 
Aug 15, 2015 
Printed
Page 207
First full paragraph, line 2

Identifies "Local Network Protection for IPv6" as RFC 4846 but it is actually RFC 4864. This is a minor typo, but it quotes the RFC and anyone who looks up the printed RFC for further information will be confused.

Note from the Author or Editor:
"RFC 4846" must be replaced by "RFC 4864"

Bo Grimes  Nov 24, 2015 
Printed
Page 216
fourth item in list

RFC 5996 must be renumbered to RFC 7296 and then reordered in list (last item)

Silvia Hagen
 
Aug 15, 2015 
Printed
Page 257
Last paragraph

65,636 should be 65.536

Note from the Author or Editor:
The comment is correct, the number in the last paragraph is "65,636" and should be "65,536".

Graham Breed  Jan 13, 2015 
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 257
3rd paragraph

The draft of 4rd has now been published as an RFC. So please change the following text: 4rd is in draft status at the time of writing. The draft is called "IPv4 Residual Deployment via IPv6 - a Stateless Solution (4rd)" (draft-ietf-softwire-4rd-08). Please replace this with the following: 4rd is defined in RFC 7600.

Silvia Hagen
 
Jan 03, 2016 
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 269
3rd paragraph

Draft has become RFC, so please adjust as follows: old sentence in current version of book (all editions): 3rd paragraph, 2nd line ...., please refer to RFC xxxx (draft-ietf-v6ops-nat64-experience-10.txt). with this sentence: (delete the draft name in brackets and replace xxxx with number) ..., please refer to RFC 7269.

Silvia Hagen
 
Jan 04, 2016 
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 270
last paragraph

Draft has become RFC, so please replace draft name with RFC number as follows: Replace current sentence Draft "draft-ietf-softwire-map,", called MAP-E, specifies..... with the follwing sentence RFC 7597, called MAP-E, specifies.....

Silvia Hagen
 
Jan 06, 2016 
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 270/271
last paragraph and first line of first paragraph on page 271

update draft name to RFC number as follows: Replace current sentence "The other draft, "draft-ietf-softwire-map-t," specifies...... with RFC 7599, called MAP-T, specifies....

Silvia Hagen
 
Jan 06, 2016 
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 272
third paragraph

Replace the whole paragraph starting with "MAP-E is going to be a standards track RFC........" and ending in "..........information needed for the address-mapping algorithm (draft-ietf-softwire-map-dhcp-07)." with the following: RFC 7598 defines DHCPv6 options for address mapping, so a DHCP server can provision the configuration information for the address mapping.

Silvia Hagen
 
Jan 07, 2016 
Printed
Page 291
2nd paragraph

RFC 4140 must be changed to RFC 5380

Silvia Hagen
 
Aug 15, 2015 
Printed
Page 312
5th entry in list

RFC 4140 must be deleted

Silvia Hagen
 
Aug 15, 2015 
Printed
Page 312
middle of list

Delete list item RFC 4306

Silvia Hagen
 
Aug 15, 2015 
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 340
Note at bottom of page (2nd note)

The number of the RIPE document has changed. Please change www.ripe.net/ripe/docs/ripe-589 to www.ripe.net/ripe/docs/ripe-655 And also change the sentence below the note by deleting "March 2014" and replacing with "January 2016".

Silvia Hagen
 
Jan 17, 2016 
Printed
Page 361
just below middle of list

Delete list item RFC 4306

Silvia Hagen
 
Aug 15, 2015 
Printed
Page 365
list sorted by numbers of RFCs

RFC 5996 must be renumbered to RFC 7296 and put in right position in list (along numbers)

Silvia Hagen
 
Aug 15, 2015