Internationalized Email Headers
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 11
- Abstract
- 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]
- Publication Date
- 2012-02-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC6532- Link
- https://doi.org/10.17487/RFC6532
- Author(s)
- Abel YangShawn SteeleNed Freed
Latest version of IETF RFC 6532
Document Versions — IETF RFC 6532
-
▶ IETF RFC 6532 (2012-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- ANSI/INCITS X3.4:1986 (R1997) [Active]
- Davis, M. and K. Whistler, "Unicode Standard Annex #15: Unicode Normalization Forms", September 2010, < http://www.unicode.org/reports/tr15/ >. EXTERNAL
- IETF RFC 2119 [Active*]
- IETF RFC 3629 [Active*]
- IETF RFC 5198 [Active*]
- IETF RFC 5234 [Active, Amended*]
- IETF RFC 5321 [Active*]
- IETF RFC 5322 [Active, Amended*]
- IETF RFC 6530 [Active*]
- IETF RFC 6531 [Active*]
Bibliographic Reference(s)
- IETF RFC 2045 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2047 [Active*]
- IETF RFC 3156 [Active*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5335 [Superseded*]
- IETF RFC 6152 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6532.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 6532, Internationalized Email Headers. Available at https://doi.org/10.17487/RFC6532
Snippet:
IETF RFC 6532, Internationalized Email Headers. Available at https://doi.org/10.17487/RFC6532
HTML (ISO 690 compliant)
Preview:
IETF RFC 6532, Internationalized Email Headers. Available at https://doi.org/10.17487/RFC6532
Snippet:
<span class="citation"><cite>IETF RFC 6532</cite>, Internationalized Email Headers. Available at <a href="https://doi.org/10.17487/RFC6532" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6532</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6532, Internationalized Email Headers
doi: 10.17487/RFC6532
url: https://doi.org/10.17487/RFC6532
doi: 10.17487/RFC6532
url: https://doi.org/10.17487/RFC6532
Snippet:
<li> <cite id="bib-rfc6532">IETF RFC 6532</cite>, Internationalized Email Headers <span class="doi">10.17487/RFC6532</span> </li>
Referenced By
- IETF RFC 6530 [Active*]
- IETF RFC 6531 [Active*]
- IETF RFC 6533 [Active*]
- IETF RFC 6838 [Active*]
- IETF RFC 6943 [Active*]
- IETF RFC 7296 [Active*]
- IETF RFC 7542 [Active*]
- IETF RFC 8398 [Superseded*]