Found 2 records.

Status: Held for Document Update (1)

RFC 4952, "Overview and Framework for Internationalized Email", July 2007

Note: This RFC has been obsoleted by RFC 6530

Note: This RFC has been updated by RFC 5336

Errata ID: 1507
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-09-15
Held for Document Update by: Alexey Melnikov

Section 1 (and 1.*) says:

                                                 [...].  However, it
   does not permit the use of email addresses that include non-ASCII
   characters.  Without the extensions defined here, or some equivalent
   set, the only way to incorporate non-ASCII characters in any part of
   email addresses is to use RFC 2047 coding to embed them in what RFC
   2822 [RFC2822] calls the "display name" (known as a "name phrase" or
|  by other terms elsewhere) of the relevant headers.  Information coded
   into the display name is invisible in the message envelope and, for
   many purposes, is not part of the address at all.

It should say:

                                                 [...].  However, it
   does not permit the use of email addresses that include non-ASCII
   characters.  Without the extensions defined here, or some equivalent
   set, the only way to incorporate non-ASCII characters in any part of
   email addresses is to use RFC 2047 coding to embed them in what RFC
   2822 [RFC2822] calls the "display name" (known as a "name phrase" or
|  by other terms elsewhere) of the relevant header fields.
   Information coded into the display name is invisible in the message
   envelope and, for many purposes, is not part of the address at all.

Notes:

Conformance to terminology established in the IETF requires
making the precise distinction between a header and the
header fields it is comprised of.

This same issue recurs in the first paragraph of Section 1.1
and in the 3rd line of the last paragraph of Section 1.2.

Status: Rejected (1)

RFC 4952, "Overview and Framework for Internationalized Email", July 2007

Note: This RFC has been obsoleted by RFC 6530

Note: This RFC has been updated by RFC 5336

Errata ID: 1508
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-09-15
Rejected by: Lisa Dusseault
Date Rejected: 2008-09-15

Section 1.3, pg.5 says:

   An "i18mail user" has one or more non-ASCII email addresses.  [...]

Notes:

This unusual term, "i18mail user" does not appear anywhere else in
the RFC besides the quoted paragraph in the Terminology section.
--VERIFIER NOTES--
The term is used in draft-ietf-eai-mailinglist-03.txt, which refers to rfc4952.

Report New Errata