RFC Errata
RFC 2152, "UTF-7 A Mail-Safe Transformation Format of Unicode", May 1997
Source of RFC: LegacyArea Assignment: app
Errata ID: 5475
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Peter Occil
Date Reported: 2018-08-22
Rejected by: Barry Leiba
Date Rejected: 2019-04-30
Section Discussion says:
Content-type: multipart/mixed; boundary=foo Content-Disposition: inline --foo Content-type: text/plain; charset=us-ascii Hi Mom --foo Content-type: text/plain; charset=UNICODE-2-0 Content-transfer-encoding: base64 Jjo= --foo Content-type: text/plain; charset=us-ascii ! --foo--
It should say:
Content-type: multipart/mixed; boundary=foo Content-Disposition: inline --foo Content-type: text/plain; charset=us-ascii Hi Mom --foo Content-type: text/plain; charset=UTF-7 Content-transfer-encoding: base64 Jjo= --foo Content-type: text/plain; charset=us-ascii ! --foo--
Notes:
The charset name for this RFC is UTF-7, not UNICODE-2-0.
--VERIFIER NOTES--
This is an example that's specifically introduced with, "As an alternative to use of UTF-7," and quite intentionally uses a charset other than UTF-7.