RFC 6532, "Internationalized Email Headers", February 2012Source of RFC: eai (app)
Errata ID: 6036
Publication Format(s) : TEXT
Reported By: Alessandro Vesely
Date Reported: 2020-04-01
Throughout the document, when it says:
A section 3.2bis, "Syntax Extensions to RFC 2045", is missing.
It should say:
In particular, Section 5.1 of RFC 2045, "Syntax of the Content-Type Header Field", deserves an extension: token /= UTF8-non-ascii similar to the extensions given to various text types given in Section 3.2.
Various header fields are defined in terms of the grammar defined in RFC 2045. In particular, the missing extension of token was reported for Authentication-Results: