RFC 6532: Internationalized Email Headers
In plain English — editorial summary, not part of the RFC
Internet mail was originally limited to 7-bit ASCII. MIME added support for the use of 8-bit character sets in body parts, and also defined an encoded-word construct so other character sets could be used in certain header field values. However, full internationalization of electronic mail requires additional enhancements to allow the use of Unicode, including characters outside the ASCII repertoire, in mail addresses as well as direct use of Unicode in header fields like "From:", "To:", and "Subject:", without requiring the use of complex encoded-word constructs. This document specifies an enhancement to the Internet Message Format and to MIME that allows use of Unicode in mail addresses and most header field content. This specification updates Section 6.4 of RFC 2045 to eliminate the restriction prohibiting the use of non-identity content-transfer- encodings on subtypes of "message/". [STANDARDS-TRACK]
Document record
- Document ID
- RFC6532
- Published
- February 2012
- Authors
- A. Yang; S. Steele; N. Freed
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6533Internationalized Delivery Status and Disposition NotificationsCurrent
February 2012
- RFC 6531SMTP Extension for Internationalized EmailCurrent
February 2012
- RFC 6530Overview and Framework for Internationalized EmailCurrent
February 2012
- RFC 6558Sieve Extension for Converting Messages before DeliveryCurrent
March 2012
- RFC 6590Redaction of Potentially Sensitive Data from Mail Abuse ReportsCurrent
April 2012
- RFC 6474vCard Format Extensions: Place of Birth, Place and Date of DeathCurrent
December 2011
- RFC 6473vCard KIND:applicationCurrent
December 2011
- RFC 6591Authentication Failure Reporting Using the Abuse Reporting FormatUpdated
April 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?