errata logo graphic

Found 2 records.

Status: Verified (2)

RFC5335, "Internationalized Email Headers", September 2008

Note: This RFC has been obsoleted by RFC6532

Source of RFC: eai (app)

Errata ID: 1509

Status: Verified
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-09-15
Verifier Name: Alexey Melnikov
Date Verified: 2009-07-06

Section 4.5, 2nd par says:

|  The "Return-Path" header provides the email return address in the
|  mail delivery.  Thus, the header is augmented to carry UTF-8
   addresses (see the revised syntax of <angle-addr> in Section 4.4 of
   this document).  This will not break the rule of trace field
|  integrity, because the header is added at the last MTA and described
   in [RFC2821].

It should say:

|  The "Return-Path" header field provides the email return address in
|  the mail delivery.  Thus, the header field is augmented to carry
   UTF-8 addresses (see the revised syntax of <angle-addr> in Section
   4.4 of this document).  This will not break the rule of trace field
|  integrity, because the header field is added at the last MTA and
   described in [RFC2821].

Notes:

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

Most parts of this RFC do this job correctly; this paragraph is an
exception.


Errata ID: 2322

Status: Verified
Type: Editorial

Reported By: John Klensin
Date Reported: 2010-07-12
Verifier Name: Alexey Melnikov
Date Verified: 2010-07-13

Section Author info says:

Y. Abel   (in first-page header block)

Abel      (in page footers)

It should say:

A. Yang

Yang

Notes:

The author is listed in the Author's Address section as "Abel Yang (editor)", which is correct although "Abel YANG (editor)" might have been preferable. In any event, the family name is "Yang", not "Abel", so the page 1 header block, page footers, and RFC Index entries are in error.

This is fixed in draft-ietf-eai-rfc5335bis-02 and later. A successor to that document will eventually obsolete RFC 5335.


Report New Errata