draft-ietf-eai-popimap-downgrade-00.txt   draft-ietf-eai-popimap-downgrade-01.txt 
Email Address Internationalization K. Fujiwara Email Address Internationalization K. Fujiwara
(EAI) JPRS (EAI) JPRS
Internet-Draft Oct 15, 2010 Internet-Draft Apr 18, 2011
Intended status: Standards Track Intended status: Standards Track
Expires: April 18, 2011 Expires: October 20, 2011
Post-delivery Message Downgrading for Internationalized Email Messages Post-delivery Message Downgrading for Internationalized Email Messages
draft-ietf-eai-popimap-downgrade-00.txt draft-ietf-eai-popimap-downgrade-01.txt
Abstract Abstract
The Email Address Internationalization (UTF8SMTP) extension allows The Email Address Internationalization (UTF8SMTP) extension allows
UTF-8 characters in mail header fields. POP and IMAP servers support UTF-8 characters in mail header fields. POP and IMAP servers support
internationalized email messages. If a POP/IMAP client does not internationalized email messages. If a POP/IMAP client does not
support Email Address Internationalization, POP/IMAP servers cannot support Email Address Internationalization, POP/IMAP servers cannot
send Internationalized Email Headers to the client and cannot remove send Internationalized Email Headers to the client and cannot remove
the message. To avoid the situation, this document describes a the message. To avoid the situation, this document describes a
conversion mechanism for internationalized Email messages to be conversion mechanism for internationalized Email messages to be
skipping to change at page 1, line 44 skipping to change at page 1, line 44
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 18, 2011. This Internet-Draft will expire on October 20, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 7, line 33 skipping to change at page 7, line 33
rule is given above, encapsulate it in a "Downgraded-" header field rule is given above, encapsulate it in a "Downgraded-" header field
as described in Section 3.1 as a last resort. as described in Section 3.1 as a last resort.
Applying this procedure to "Received:" header field is prohibited. Applying this procedure to "Received:" header field is prohibited.
4.1.9. TYPED-ADDRESS Downgrading 4.1.9. TYPED-ADDRESS Downgrading
If the header field contains <utf-8-type-addr> and the <utf-8-type- If the header field contains <utf-8-type-addr> and the <utf-8-type-
addr> contains raw non-ASCII characters, it is in utf-8-address form. addr> contains raw non-ASCII characters, it is in utf-8-address form.
Convert it to utf-8-addr-xtext form. Those forms are described in Convert it to utf-8-addr-xtext form. Those forms are described in
[RFC5337]. COMMENT downgrading is also performed in this case. If [I-D.ietf-eai-rfc5337bis-dsn]. COMMENT downgrading is also performed
the address type is unrecognized and the header field contains non- in this case. If the address type is unrecognized and the header
ASCII characters, then fall back to using ENCAPSULATION downgrading field contains non-ASCII characters, then fall back to using
on the entire header field. ENCAPSULATION downgrading on the entire header field.
4.2. Downgrading Method for Each Header Field 4.2. Downgrading Method for Each Header Field
Header fields are listed in [RFC4021]. This section describes the Header fields are listed in [RFC4021]. This section describes the
downgrading method for each header field. downgrading method for each header field.
If the whole mail header field does not contain non-ASCII characters, If the whole mail header field does not contain non-ASCII characters,
email header field downgrading is not required. Each header field's email header field downgrading is not required. Each header field's
downgrading method is described below. downgrading method is described below.
skipping to change at page 12, line 14 skipping to change at page 12, line 14
10.1. Normative References 10.1. Normative References
[I-D.ietf-eai-frmwrk-4952bis] Klensin, J. and Y. Ko, "Overview and [I-D.ietf-eai-frmwrk-4952bis] Klensin, J. and Y. Ko, "Overview and
Framework for Internationalized Framework for Internationalized
Email", Email",
draft-ietf-eai-frmwrk-4952bis-10 (work draft-ietf-eai-frmwrk-4952bis-10 (work
in progress), September 2010. in progress), September 2010.
[I-D.ietf-eai-rfc5335bis] Yang, A. and S. Steele, [I-D.ietf-eai-rfc5335bis] Yang, A. and S. Steele,
"Internationalized Email Headers", "Internationalized Email Headers",
draft-ietf-eai-rfc5335bis-02 (work in draft-ietf-eai-rfc5335bis-10 (work in
progress), August 2010. progress), March 2011.
[I-D.ietf-eai-rfc5337bis-dsn] Hansen, T., Newman, C., and A.
Melnikov, "Internationalized Delivery
Status and Disposition Notifications",
draft-ietf-eai-rfc5337bis-dsn-02 (work
in progress), April 2011.
[RFC2045] Freed, N. and N. Borenstein, [RFC2045] Freed, N. and N. Borenstein,
"Multipurpose Internet Mail Extensions "Multipurpose Internet Mail Extensions
(MIME) Part One: Format of Internet (MIME) Part One: Format of Internet
Message Bodies", RFC 2045, Message Bodies", RFC 2045,
November 1996. November 1996.
[RFC2047] Moore, K., "MIME (Multipurpose [RFC2047] Moore, K., "MIME (Multipurpose
Internet Mail Extensions) Part Three: Internet Mail Extensions) Part Three:
Message Header Extensions for Non- Message Header Extensions for Non-
ASCII Text", RFC 2047, November 1996. ASCII Text", RFC 2047, November 1996.
[RFC2119] Bradner, S., "Key words for use in
RFCs to Indicate Requirement Levels",
BCP 14, RFC 2119, March 1997.
[RFC2183] Troost, R., Dorner, S., and K. Moore, [RFC2183] Troost, R., Dorner, S., and K. Moore,
"Communicating Presentation "Communicating Presentation
Information in Internet Messages: The Information in Internet Messages: The
Content-Disposition Header Field", Content-Disposition Header Field",
RFC 2183, August 1997. RFC 2183, August 1997.
[RFC2231] Freed, N. and K. Moore, "MIME [RFC2231] Freed, N. and K. Moore, "MIME
Parameter Value and Encoded Word Parameter Value and Encoded Word
Extensions: Character Sets, Languages, Extensions: Character Sets, Languages,
and Continuations", RFC 2231, and Continuations", RFC 2231,
November 1997. November 1997.
[RFC2979] Freed, N., "Behavior of and [RFC5322] Resnick, P., Ed., "Internet Message
Requirements for Internet Firewalls", Format", RFC 5322, October 2008.
RFC 2979, October 2000.
[RFC3629] Yergeau, F., "UTF-8, a transformation [RFC3629] Yergeau, F., "UTF-8, a transformation
format of ISO 10646", STD 63, format of ISO 10646", STD 63,
RFC 3629, November 2003. RFC 3629, November 2003.
[RFC3864] Klyne, G., Nottingham, M., and J.
Mogul, "Registration Procedures for
Message Header Fields", BCP 90,
RFC 3864, September 2004.
[RFC4021] Klyne, G. and J. Palme, "Registration [RFC4021] Klyne, G. and J. Palme, "Registration
of Mail and MIME Header Fields", of Mail and MIME Header Fields",
RFC 4021, March 2005. RFC 4021, March 2005.
[RFC5322] Resnick, P., Ed., "Internet Message [RFC2119] Bradner, S., "Key words for use in
Format", RFC 5322, October 2008. RFCs to Indicate Requirement Levels",
BCP 14, RFC 2119, March 1997.
[RFC5337] Newman, C. and A. Melnikov,
"Internationalized Delivery Status and
Disposition Notifications", RFC 5337,
September 2008.
10.2. Informative References 10.2. Informative References
[RFC5504] Fujiwara, K. and Y. Yoneya, [RFC5504] Fujiwara, K. and Y. Yoneya,
"Downgrading Mechanism for Email "Downgrading Mechanism for Email
Address Internationalization", Address Internationalization",
RFC 5504, March 2009. RFC 5504, March 2009.
Appendix A. Examples Appendix A. Examples
 End of changes. 11 change blocks. 
30 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/