RFC Errata
Found 3 records.
Status: Reported (2)
RFC 4862, "IPv6 Stateless Address Autoconfiguration", September 2007
Note: This RFC has been updated by RFC 7527
Source of RFC: ipv6 (int)
Errata ID: 7509
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Jonathan Johnson
Date Reported: 2023-05-05
Section 5.3 says:
A link-local address is formed by combining the well-known link-local prefix FE80::0 [RFC4291] (of appropriate length) with an interface identifier as follows:
It should say:
A link-local address is formed by combining the well-known link-local prefix FE80::/10 [RFC4291] (of appropriate length) with an interface identifier as follows:
Notes:
The prefix text should be in CIDR notation, as the referenced RFC4921 sec. 2.4 lists it in CIDR notation. Further, FE80::0 describes an address, not a prefix.
Errata ID: 6709
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mark Smith
Date Reported: 2021-10-14
Throughout the document, when it says:
Abstract This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link-local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link.
It should say:
Abstract This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link-local address, generating global addresses via stateless address autoconfiguration (SLAAC), and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link.
Notes:
IPv6 Stateless Address Autoconfiguration is very widely known by the acronym SLAAC, yet surprisingly that acronym doesn't appear anywhere in RFC4862. It would be best to include and use it in a future update to RFC4862.
Status: Held for Document Update (1)
RFC 4862, "IPv6 Stateless Address Autoconfiguration", September 2007
Note: This RFC has been updated by RFC 7527
Source of RFC: ipv6 (int)
Errata ID: 4305
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Erik Nordmark
Date Reported: 2015-03-17
Held for Document Update by: Brian Haberman
Date Held: 2015-09-14
Section Appendix C says:
o Clarified that on failure of Duplicate Address Detection, IP network operation should be disabled and that the rule should apply when the hardware address is supposed to be unique.
It should say:
o Clarified that on failure of Duplicate Address Detection, IP network operation for the interface should be disabled if and only if: - the duplicate check is performed on the IP link-local address, - the link-local address is based on an EUI-64 or other hardware address, and - the hardware address is supposed to be unique on the link.