RFC 5952, "A Recommendation for IPv6 Address Text Representation", August 2010

Errata ID: 2872
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Richard J. Smith
Date Reported: 2011-07-28
Rejected by: Brian Haberman
Date Rejected: 2012-06-01

Section 5 says:

   For these addresses, mixed notation is
   RECOMMENDED if the following condition is met: the address can be
   distinguished as having IPv4 addresses embedded in the lower 32 bits
   solely from the address field through the use of a well-known prefix.

It should say:

   For these addresses, mixed notation is 
   RECOMMENDED if the following conditions are met: the address can be
   distinguished as having IPv4 addresses embedded in the lower 32 bits 
   solely from the address field through the use of a well-known prefix, 
   and the entire address is not either the unspecified IPv6 address 
   "::" or the loopback IPv6 address "::1".

Notes:

RFC-4291 defines the 80-bit all-zeros prefix as indicating an "IPv4-compatible IPv6 address". Without further clarification in section 5 of RFC-5952, the recommended formatting of the IPv6 unspecified address would be "::0.0.0.0", and the recommended formatting of the IPv6 loopback address would be "::0.0.0.1". Neither of these recommended representations is desirable.
--VERIFIER NOTES--
::1 and :: are more specific and not part of the reserved block for IPv4 compatible addresses.

Report New Errata