RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

RFC 6857, "Post-Delivery Message Downgrading for Internationalized Email Messages", March 2013

Source of RFC: eai (app)

Errata ID: 6930
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: John Klensin
Date Reported: 2022-04-10

Section 3.1.8 says:

The <addr-spec> element that contains non-ASCII strings may appear in two forms as:

   "<" addr-spec ">"



   Rewrite both as:


It should say:

The <addr-spec> element that contains non-ASCII strings may appear in two forms as:

   "<"  local-part "@" domain ">"


   local-part "@" domain

   If the <local-part> contains non-ASCII characters, rewrite both to:

   ENCODED-WORD "@" domain

   If the <domain> contains non-ASCII characters in any of its labels, they MUST appear in A-label form as described in Section 3.1.6.

If the <addr-spec> is part of a <mailbox> specification that contains a <display-name>, the display name should be handled as per the discussion in Section 3.1.5 and the <mailbox> and <addr-spec> containing non-ASCII characters  MUST appear as

   DISPLAY-NAME "<" ENCODED-WORD "@" domain ">"

for consistency with RFC 5322.


Recommend "Hold for document update" and see the extensive comments on Erratum 6573.

The text above, while correct, is fairly horrible and might make the confusion between the requirements of Sections 3.1.5 and 3.1.8 even worse. A complete rewrite of this section and possibly 3.1.5 would be a better fix. Note the prohibition on Encoded Words in <addr-spec> in RFC 2047, which requires updating. Also note that the " :;" construction, which is correct in Section 3.1.7, does not belong in the above.

It also not clear to me why, under some principle of minimal change, the brackets should not be just left alone if they appear in the original with no adjacent display-name.

Report New Errata

Advanced Search