Found 2 records.

Status: Verified (1)

RFC 2526, "Reserved IPv6 Subnet Anycast Addresses", March 1999

Errata ID: 7659
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Marc Muehlfeld
Date Reported: 2023-09-28
Verifier Name: RFC Editor
Date Verified: 2023-09-28

Section 2 says:

Specifically, for IPv6 address types required to have to have 64-bit
interface identifiers in EUI-64 format, these reserved subnet anycast
addresses are constructed as follows:

It should say:

Specifically, for IPv6 address types required to have 64-bit
interface identifiers in EUI-64 format, these reserved subnet anycast
addresses are constructed as follows:

Notes:

There is a duplicate "to have" in the sentence.

Status: Rejected (1)

RFC 2526, "Reserved IPv6 Subnet Anycast Addresses", March 1999

Errata ID: 7807
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Phu Dang Kim
Date Reported: 2024-02-10
Rejected by: Eric Vyncke
Date Rejected: 2024-04-23

Section 2 says:

In particular, for IPv6 address
   types required to have 64-bit interface identifiers in EUI-64 format,
   the universal/local bit MUST be set to 0 (local)

It should say:

In particular, for IPv6 address
   types required to have 64-bit interface identifiers in EUI-64 format,
   the universal/local bit MUST be set to 1 (local)

Notes:

local 1 not 0 (https://datatracker.ietf.org/doc/html/rfc4291#section-2.6)
--VERIFIER NOTES--
The section 4 also repeats that the value is 0, notably to make a difference with other IPv6 address types (cfr section 2).

Report New Errata