RFC 5504: Downgrading Mechanism for Email Address Internationalization
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
Traditional mail systems handle only ASCII characters in SMTP envelope and mail header fields. The Email Address Internationalization (UTF8SMTP) extension allows UTF-8 characters in SMTP envelope and mail header fields. To avoid rejecting internationalized email messages when a server in the delivery path does not support the UTF8SMTP extension, some sort of converting mechanism is required. This document describes a downgrading mechanism for Email Address Internationalization. Note that this is a way to downgrade, not tunnel. There is no associated up-conversion mechanism, although internationalized email clients might use original internationalized addresses or other data when displaying or replying to downgraded messages. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5504
- Published
- March 2009
- Authors
- K. Fujiwara; Y. Yoneya
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 24
- Also known as
- —
- Obsoleted by:
- RFC 6530
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 →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5825Displaying Downgraded Messages for Email Address InternationalizationObsoleted
April 2010
- RFC 6857Post-Delivery Message Downgrading for Internationalized Email MessagesCurrent
March 2013
- RFC 5336SMTP Extension for Internationalized Email AddressesObsoleted
September 2008
- RFC 5337Internationalized Delivery Status and Disposition NotificationsObsoleted
September 2008
- RFC 5721POP3 Support for UTF-8Obsoleted
February 2010
- RFC 6783Mailing Lists and Non-ASCII AddressesCurrent
November 2012
- RFC 3950Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationCurrent
February 2005
- RFC 3949File Format for Internet FaxCurrent
February 2005
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?