RFC 6530: Overview and Framework for Internationalized Email
In plain English — editorial summary, not part of the RFC
Full use of electronic mail throughout the world requires that (subject to other constraints) people be able to use close variations on their own names (written correctly in their own languages and scripts) as mailbox names in email addresses. This document introduces a series of specifications that define mechanisms and protocol extensions needed to fully support internationalized email addresses. These changes include an SMTP extension and extension of email header syntax to accommodate UTF-8 data. The document set also includes discussion of key assumptions and issues in deploying fully internationalized email. This document is a replacement for RFC 4952; it reflects additional issues identified since that document was published. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6530
- Published
- February 2012
- Authors
- J. Klensin; Y. Ko
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 26
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 4952 (2007)
- RFC 5504 (2009)
- RFC 5825 (2010)
- RFC 6530 (2012)
Read the full history of Overview and Framework for Internationalized Email →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6531SMTP Extension for Internationalized EmailCurrent
February 2012
- RFC 6409Message Submission for MailUpdated
November 2011
- RFC 6783Mailing Lists and Non-ASCII AddressesCurrent
November 2012
- RFC 6009Sieve Email Filtering: Delivery Status Notifications and Deliver-By ExtensionsCurrent
October 2010
- RFC 5784Sieve Email Filtering: Sieves and Display Directives in XMLCurrent
March 2010
- RFC 5721POP3 Support for UTF-8Obsoleted
February 2010
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5463Sieve Email Filtering: Ihave ExtensionCurrent
March 2009
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?