metasystema.org
ObsoletedINFORMATIONALIETF stream

RFC 4952: Overview and Framework for Internationalized Email

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6530.

Current document in this lineage: 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 people be able to use 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 memo provides information for the Internet community.

Document record

Document ID
RFC4952
Published
July 2007
Authors
J. Klensin; Y. Ko
Status
INFORMATIONAL
Stream
IETF
Area
app
Pages
20
Also known as
—
Obsoleted by:
RFC 6530
Updated by:
RFC 5336

Topics

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 4952 (2007)
  2. RFC 5504 (2009)
  3. RFC 5825 (2010)
  4. RFC 6530 (2012) ✓

Read the full history of Overview and Framework for Internationalized Email →

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4952-overview-and-framework-for-internationalized-email