< draft-ietf-eai-smtpext-12.txt   draft-ietf-eai-smtpext-13.txt >
Network Working Group J. Yao, Ed. Network Working Group J. Yao, Ed.
Internet-Draft W. Mao, Ed. Internet-Draft W. Mao, Ed.
Updates: RFC4952, 2821 and 2822 CNNIC Updates: RFC4952, 2821 and 2822 CNNIC
(if approved) April 8, 2008 (if approved) July 8, 2008
Intended status: Experimental Intended status: Experimental
Expires: October 10, 2008 Expires: January 9, 2009
SMTP extension for internationalized email address SMTP extension for internationalized email address
draft-ietf-eai-smtpext-12.txt draft-ietf-eai-smtpext-13.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 October 10, 2008. This Internet-Draft will expire on January 9, 2009.
Abstract Abstract
This document specifies an SMTP extension for transport and delivery This document specifies an SMTP extension for transport and delivery
of email messages with internationalized email addresses or header of email messages with internationalized email addresses or header
information. Communication with systems that do not implement this information. Communication with systems that do not implement this
specification is specified in another document. specification is specified in another document. This document
updates some syntaxes and rules defined in RFC 2821 and RFC 2822, and
has some material updating RFC 4952.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Role of this specification . . . . . . . . . . . . . . . . 3 1.1. Role of this specification . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview of Operation . . . . . . . . . . . . . . . . . . . . 4 2. Overview of Operation . . . . . . . . . . . . . . . . . . . . 4
3. Mail Transport-level Protocol . . . . . . . . . . . . . . . . 4 3. Mail Transport-level Protocol . . . . . . . . . . . . . . . . 4
3.1. Framework for the Internationalization Extension . . . . . 4 3.1. Framework for the Internationalization Extension . . . . . 4
3.2. The UTF8SMTP Extension . . . . . . . . . . . . . . . . . . 5 3.2. The UTF8SMTP Extension . . . . . . . . . . . . . . . . . . 5
3.3. Extended Mailbox Address Syntax . . . . . . . . . . . . . 7 3.3. Extended Mailbox Address Syntax . . . . . . . . . . . . . 7
3.4. The ALT-ADDRESS Parameter . . . . . . . . . . . . . . . . 8 3.4. The ALT-ADDRESS Parameter . . . . . . . . . . . . . . . . 8
3.5. ALT-ADDRESS Parameter Usage and Response Codes . . . . . . 9 3.5. ALT-ADDRESS Parameter Usage and Response Codes . . . . . . 10
3.6. Body Parts and SMTP Extensions . . . . . . . . . . . . . . 10 3.6. Body Parts and SMTP Extensions . . . . . . . . . . . . . . 10
3.7. Additional ESMTP Changes and Clarifications . . . . . . . 11 3.7. Additional ESMTP Changes and Clarifications . . . . . . . 11
3.7.1. The Initial SMTP Exchange . . . . . . . . . . . . . . 11 3.7.1. The Initial SMTP Exchange . . . . . . . . . . . . . . 11
3.7.2. Mail eXchangers . . . . . . . . . . . . . . . . . . . 11 3.7.2. Mail eXchangers . . . . . . . . . . . . . . . . . . . 12
3.7.3. Trace Information . . . . . . . . . . . . . . . . . . 11 3.7.3. Trace Information . . . . . . . . . . . . . . . . . . 12
3.7.4. UTF-8 Strings in Replies . . . . . . . . . . . . . . . 12 3.7.4. UTF-8 Strings in Replies . . . . . . . . . . . . . . . 13
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
5. Security Considerations . . . . . . . . . . . . . . . . . . . 16 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
7. Change History . . . . . . . . . . . . . . . . . . . . . . . . 17 7. Change History . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1. draft-ietf-eai-smtpext: Version 00 . . . . . . . . . . . . 17 7.1. draft-ietf-eai-smtpext: Version 00 . . . . . . . . . . . . 17
7.2. draft-ietf-eai-smtpext: Version 01 . . . . . . . . . . . . 17 7.2. draft-ietf-eai-smtpext: Version 01 . . . . . . . . . . . . 17
7.3. draft-ietf-eai-smtpext: Version 02 . . . . . . . . . . . . 17 7.3. draft-ietf-eai-smtpext: Version 02 . . . . . . . . . . . . 18
7.4. draft-ietf-eai-smtpext: Version 03 . . . . . . . . . . . . 17 7.4. draft-ietf-eai-smtpext: Version 03 . . . . . . . . . . . . 18
7.5. draft-ietf-eai-smtpext: Version 04 . . . . . . . . . . . . 17 7.5. draft-ietf-eai-smtpext: Version 04 . . . . . . . . . . . . 18
7.6. draft-ietf-eai-smtpext: Version 05 . . . . . . . . . . . . 17 7.6. draft-ietf-eai-smtpext: Version 05 . . . . . . . . . . . . 18
7.7. draft-ietf-eai-smtpext: Version 06 . . . . . . . . . . . . 18 7.7. draft-ietf-eai-smtpext: Version 06 . . . . . . . . . . . . 18
7.8. draft-ietf-eai-smtpext: Version 07 . . . . . . . . . . . . 18 7.8. draft-ietf-eai-smtpext: Version 07 . . . . . . . . . . . . 18
7.9. draft-ietf-eai-smtpext: Version 08 . . . . . . . . . . . . 18 7.9. draft-ietf-eai-smtpext: Version 08 . . . . . . . . . . . . 19
7.10. draft-ietf-eai-smtpext: Version 09 . . . . . . . . . . . . 18 7.10. draft-ietf-eai-smtpext: Version 09 . . . . . . . . . . . . 19
7.11. draft-ietf-eai-smtpext: Version 10 . . . . . . . . . . . . 18 7.11. draft-ietf-eai-smtpext: Version 10 . . . . . . . . . . . . 19
7.12. draft-ietf-eai-smtpext: Version 11 . . . . . . . . . . . . 18 7.12. draft-ietf-eai-smtpext: Version 11 . . . . . . . . . . . . 19
7.13. draft-ietf-eai-smtpext: Version 12 . . . . . . . . . . . . 19 7.13. draft-ietf-eai-smtpext: Version 12 . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7.14. draft-ietf-eai-smtpext: Version 13 . . . . . . . . . . . . 19
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2. Informative References . . . . . . . . . . . . . . . . . . 20 8.1. Normative References . . . . . . . . . . . . . . . . . . . 20
8.2. Informative References . . . . . . . . . . . . . . . . . . 21
Appendix A. Material Updating RFC 4952 . . . . . . . . . . . . . 21 Appendix A. Material Updating RFC 4952 . . . . . . . . . . . . . 21
A.1. Conventional Message and Internationalized Message . . . . 21 A.1. Conventional Message and Internationalized Message . . . . 22
A.2. LMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 A.2. LMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
A.3. SMTP Service Extension for DSNs . . . . . . . . . . . . . 21 A.3. SMTP Service Extension for DSNs . . . . . . . . . . . . . 22
A.4. Implementation Advice . . . . . . . . . . . . . . . . . . 22 A.4. Implementation Advice . . . . . . . . . . . . . . . . . . 22
A.5. Applicability of SMTP Extension to Additional Uses . . . . 22 A.5. Applicability of SMTP Extension to Additional Uses . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . . . 24 Intellectual Property and Copyright Statements . . . . . . . . . . 24
1. Introduction 1. Introduction
An internationalized email address includes two parts, the local part An internationalized email address includes two parts, the local part
and the domain part. The ways email addresses are used by protocols and the domain part. The ways email addresses are used by protocols
are different from the ways domain names are used. The most critical are different from the ways domain names are used. The most critical
difference is that emails are delivered through a chain of clients difference is that emails are delivered through a chain of clients
and servers while domain names are resolved by name servers looking and servers while domain names are resolved by name servers looking
up those names in their own tables. In addition to this, the simple up those names in their own tables. In addition to this, the simple
skipping to change at page 7, line 39 skipping to change at page 7, line 39
; MAY be case-sensitive ; MAY be case-sensitive
; Replace Local-part in RFC 2821, section 4.1.2 ; Replace Local-part in RFC 2821, section 4.1.2
uDot-string = uAtom *("." uAtom) uDot-string = uAtom *("." uAtom)
; Replace Dot-string in RFC 2821, section 4.1.2 ; Replace Dot-string in RFC 2821, section 4.1.2
uAtom = 1*ucharacter uAtom = 1*ucharacter
; Replace Atom in RFC 2821, section 4.1.2 ; Replace Atom in RFC 2821, section 4.1.2
ucharacter = atext / UTF8-non-ascii ucharacter = atext / UTF8-non-ascii
; atext is defined in RFC 2822
atext = <See section 3.2.4 of RFC 2822>
uQuoted-string = DQUOTE *uqcontent DQUOTE uQuoted-string = DQUOTE *uqcontent DQUOTE
; Replace Quoted-string in RFC 2821, section 4.1.2 ; Replace Quoted-string in RFC 2821, section 4.1.2
; DQUOTE is Double Quote defined in RFC 5234
DQUOTE = <See appendix B.1 of RFC 5234>
uqcontent = qcontent / UTF8-non-ascii uqcontent = qcontent / UTF8-non-ascii
; qcontent is defined in RFC 2822, section 3.2.5
qcontent = <See section 3.2.5 of RFC 2822>
uDomain = (sub-udomain 1*("." sub-udomain)) / address-literal uDomain = (sub-udomain 1*("." sub-udomain)) / address-literal
; Replace Domain in RFC 2821, section 4.1.2 ; Replace Domain in RFC 2821, section 4.1.2
; address-literal is defined in RFC2821 section 4.1.2
address-literal = <See section 4.1.2 of RFC 2822>
sub-udomain = uLet-dig [uLdh-str] sub-udomain = uLet-dig [uLdh-str]
; Replace sub-domain in RFC 2821, section 4.1.2 ; Replace sub-domain in RFC 2821, section 4.1.2
uLet-dig = Let-dig / UTF8-non-ascii uLet-dig = Let-dig / UTF8-non-ascii
; Let-dig is defined in RFC 2821, section 4.1.3
Let-dig = <See section 4.1.3 of RFC 2821>
uLdh-str = *( ALPHA / DIGIT / "-" / UTF8-non-ascii) uLet-dig uLdh-str = *( ALPHA / DIGIT / "-" / UTF8-non-ascii) uLet-dig
; Replace Ldh-str in RFC 2821, section 4.1.3 ; Replace Ldh-str in RFC 2821, section 4.1.3
UTF8-non-ascii = UTF8-2 / UTF8-3 / UTF8-4 UTF8-non-ascii = UTF8-2 / UTF8-3 / UTF8-4
; UTF8-2, UTF8-3 and UTF8-4 are two, three, or four
; octet UTF-8 characters, as defined in RFC 3629 UTF8-2 = <See section 4 of RFC 3629>
UTF8-3 = <See section 4 of RFC 3629>
UTF8-4 = <See section 4 of RFC 3629>
The value of "uDomain" SHOULD be verified by applying the tests The value of "uDomain" SHOULD be verified by applying the tests
specified as part of IDNA [RFC3490]. If that verification fails, the specified as part of IDNA [RFC3490]. If that verification fails, the
email address with that uDomain MUST NOT be regarded as a valid email email address with that uDomain MUST NOT be regarded as a valid email
address. address.
3.4. The ALT-ADDRESS Parameter 3.4. The ALT-ADDRESS Parameter
If the UTF8SMTP extension is offered, the syntax of the SMTP MAIL and If the UTF8SMTP extension is offered, the syntax of the SMTP MAIL and
RCPT commands is extended to support the optional esmtp-keyword "ALT- RCPT commands is extended to support the optional esmtp-keyword "ALT-
skipping to change at page 9, line 27 skipping to change at page 9, line 43
; uDomain is defined in section 3.3 of this document ; uDomain is defined in section 3.3 of this document
uReverse-path = uPath uReverse-path = uPath
; Replace Reverse-path in RFC 2821, section 4.1.2 ; Replace Reverse-path in RFC 2821, section 4.1.2
uForward-path = uPath uForward-path = uPath
; Replace Forward-path in RFC 2821, section 4.1.2 ; Replace Forward-path in RFC 2821, section 4.1.2
uPath = "<" [ A-d-l ":" ] uMailbox ">" uPath = "<" [ A-d-l ":" ] uMailbox ">"
; Replace Path in RFC 2821, section 4.1.2 ; Replace Path in RFC 2821, section 4.1.2
; A-d-l is defined in RFC 2821, section 4.1.2
; uMailbox is defined in section 3.3 of this document ; uMailbox is defined in section 3.3 of this document
A-d-l = <See section 4.1.2 of RFC 2821>
ALT-ADDRESS-parameter="ALT-ADDRESS=" ALT-ADDRESS-value ALT-ADDRESS-parameter="ALT-ADDRESS=" ALT-ADDRESS-value
ALT-ADDRESS-value=xtext ALT-ADDRESS-value= xtext
; The value is a mailbox name encoded as xtext. ; The value is a mailbox name encoded as xtext.
; xtext is defined in RFC 3461, section 4.2
xtext= <See section 4.2 of RFC 3461>
The ALT-ADDRESS-parameter MUST NOT appear more than once in any MAIL The ALT-ADDRESS-parameter MUST NOT appear more than once in any MAIL
or RCPT command. ALT-ADDRESS-esmtp-value MUST be an all-ASCII email or RCPT command. ALT-ADDRESS-esmtp-value MUST be an all-ASCII email
address before xtext encoding. address before xtext encoding.
3.5. ALT-ADDRESS Parameter Usage and Response Codes 3.5. ALT-ADDRESS Parameter Usage and Response Codes
An "internationalized message" as defined in the appendix of this An "internationalized message" as defined in the appendix of this
specification MUST NOT be sent to an SMTP server that does not specification MUST NOT be sent to an SMTP server that does not
support UTF8SMTP. Such a message MAY be rejected by a server if it support UTF8SMTP. Such a message MAY be rejected by a server if it
skipping to change at page 12, line 23 skipping to change at page 12, line 43
uReturn-path-line = "Return-Path:" FWS uReverse-path <CRLF> uReturn-path-line = "Return-Path:" FWS uReverse-path <CRLF>
; Replaces Return-path-line in section 4.4 of RFC2821 ; Replaces Return-path-line in section 4.4 of RFC2821
; uReverse-path is defined in Section 3.3 of this document ; uReverse-path is defined in Section 3.3 of this document
uTime-stamp-line = "Received:" FWS uStamp <CRLF> uTime-stamp-line = "Received:" FWS uStamp <CRLF>
; Replaces Time-stamp-line in section 4.4 of RFC2821 ; Replaces Time-stamp-line in section 4.4 of RFC2821
uStamp = From-domain By-domain uOpt-info ";" FWS date-time uStamp = From-domain By-domain uOpt-info ";" FWS date-time
; Replaces Stamp in section 4.4 of RFC2821 ; Replaces Stamp in section 4.4 of RFC2821
uOpt-info = [Via] [With] [ID] [uFor] uOpt-info = [Via] [With] [ID] [uFor]
; Replaces Opt-info in section 4.4 of RFC2821 ; Replaces Opt-info in section 4.4 of RFC2821
; The protocol value for With will allow a UTF8SMTP value ; The protocol value for With will allow a UTF8SMTP value
uFor = "FOR" ( FWS (uPath / uMailbox) ) CFWS uFor = "FOR" ( FWS (uPath / uMailbox) ) CFWS
; Replaces For in section 4.4 of RFC2821 ; Replaces For in section 4.4 of RFC2821
; uPath and uMailbox are defined in Sections 2.4 and ; uPath and uMailbox are defined in Sections 2.4 and
; 2.3, respectively, of this document ; 2.3, respectively, of this document
[[anchor10: Note: The FOR parameter has been changed to match the Note: The FOR parameter has been changed to match the definition in
definition in RFC2821bis, permitting only one address in the For [RFC2821bis], permitting only one address in the For clause. The
clause. The group working on that document reached mailing list group working on that document reached mailing list consensus that
consensus that the syntax in RFC 2821 that permitted more than one the syntax in [RFC2821] that permitted more than one address was
address was simply a mistake.]] simply a mistake.
Except in the 'uFor' clause and 'uReverse-path' value where non-ASCII Except in the 'uFor' clause and 'uReverse-path' value where non-ASCII
domain names may be used, internationalized domain names in Received domain names may be used, internationalized domain names in Received
fields MUST be transmitted in the form of ACE labels. The protocol fields MUST be transmitted in the form of ACE labels. The protocol
value of the WITH clause when this extension is used is one of the value of the WITH clause when this extension is used is one of the
UTF8SMTP values specified in the "IANA Considerations" section of UTF8SMTP values specified in the "IANA Considerations" section of
this document. this document.
3.7.4. UTF-8 Strings in Replies 3.7.4. UTF-8 Strings in Replies
3.7.4.1. MAIL and RCPT Commands 3.7.4.1. MAIL and RCPT Commands
If the client issues a RCPT command containing non-ASCII characters, If the client issues a RCPT command containing non-ASCII characters,
the SMTP server is permitted to use UTF-8 characters in the email the SMTP server is permitted to use UTF-8 characters in the email
address associated with 251 and 551 response codes. address associated with 251 and 551 response codes.
If an SMTP client follows this specification and sends any RCPT If an SMTP client follows this specification and sends any RCPT
commands containing non-ASCII addresses, it MUST be able to accept commands containing non-ASCII addresses, it MUST be able to accept
and process 251 or 551 replies containing UTF-8 email addresses. If and process 251 or 551 replies containing UTF-8 email addresses. If
a given RCPT command does not include a non-ASCII envelope address, a given RCPT command does not include a non-ASCII envelope address,
skipping to change at page 13, line 39 skipping to change at page 14, line 11
such replies by transmitting this parameter. Most replies do not such replies by transmitting this parameter. Most replies do not
require that a mailbox name be included in the returned text and require that a mailbox name be included in the returned text and
therefore UTF-8 is not needed in them. Some replies, notably those therefore UTF-8 is not needed in them. Some replies, notably those
resulting from successful execution of the VRFY and EXPN commands, do resulting from successful execution of the VRFY and EXPN commands, do
include the mailbox, making the provisions of this section important. include the mailbox, making the provisions of this section important.
VERIFY (VRFY) and EXPAND (EXPN) command syntaxes are changed to: VERIFY (VRFY) and EXPAND (EXPN) command syntaxes are changed to:
"VRFY" SP (uLocal-part / uMailbox) [SP "UTF8REPLY"] CRLF "VRFY" SP (uLocal-part / uMailbox) [SP "UTF8REPLY"] CRLF
; uLocal-part and uMailbox are defined in ; uLocal-part and uMailbox are defined in
; Section 3.3 of this document ; Section 3.3 of this document
"EXPN" SP ( uLocal-part / uMailbox ) [ SP "UTF8REPLY" ] CRLF "EXPN" SP ( uLocal-part / uMailbox ) [ SP "UTF8REPLY" ] CRLF
; uLocal-part and uMailbox are defined in ; uLocal-part and uMailbox are defined in
; Section 3.3 of this document ; Section 3.3 of this document
The "UTF8REPLY" parameter does not use a value. If the reply to a The "UTF8REPLY" parameter does not use a value. If the reply to a
VERIFY (VRFY) or EXPAND (EXPN) command requires UTF-8, but the SMTP VERIFY (VRFY) or EXPAND (EXPN) command requires UTF-8, but the SMTP
client does not use the "UTF8REPLY" parameter, then the server MUST client does not use the "UTF8REPLY" parameter, then the server MUST
use either the reply code 252 or 550. Response code 252, defined in use either the reply code 252 or 550. Response code 252, defined in
[RFC2821], means "Cannot VRFY user, but will accept the message and [RFC2821], means "Cannot VRFY user, but will accept the message and
attempt the delivery". Response code 550, also defined in [RFC2821], attempt the delivery". Response code 550, also defined in [RFC2821],
means "Requested action not taken: mailbox unavailable". When the means "Requested action not taken: mailbox unavailable". When the
server supports enhanced mail system status codes [RFC3463], the server supports enhanced mail system status codes [RFC3463], the
enhanced response code as specified below is used. Using the enhanced response code as specified below is used. Using the
skipping to change at page 14, line 31 skipping to change at page 15, line 4
If the SMTP reply requires UTF-8 strings, but UTF-8 is not allowed in If the SMTP reply requires UTF-8 strings, but UTF-8 is not allowed in
the reply, and the server supports enhanced mail system status codes the reply, and the server supports enhanced mail system status codes
[RFC3463], the enhanced response code is either "5.6.y" or "2.6.y" [RFC3463], the enhanced response code is either "5.6.y" or "2.6.y"
[SMTP-codes], meaning "A reply containing a UTF-8 string is required [SMTP-codes], meaning "A reply containing a UTF-8 string is required
to show the mailbox name, but that form of response is not permitted to show the mailbox name, but that form of response is not permitted
by the client". by the client".
If the SMTP Client does not support the UTF8SMTP extension, but If the SMTP Client does not support the UTF8SMTP extension, but
receives a UTF-8 string in a reply, it may not be able to properly receives a UTF-8 string in a reply, it may not be able to properly
report the reply to the user, and some clients might crash. report the reply to the user, and some clients might crash.
Internationalized messages in replies are only allowed in the Internationalized messages in replies are only allowed in the
commands under the situations described above. Under any other commands under the situations described above. Under any other
circumstances, UTF-8 text MUST NOT appear in the reply. circumstances, UTF-8 text MUST NOT appear in the reply.
Although UTF-8 is needed to represent email addresses in responses Although UTF-8 is needed to represent email addresses in responses
under the rules specified in this section, this extension does not under the rules specified in this section, this extension does not
permit the use of UTF-8 for any other purposes. SMTP servers MUST permit the use of UTF-8 for any other purposes. SMTP servers MUST
NOT include non-ASCII characters in replies except in the limited NOT include non-ASCII characters in replies except in the limited
cases specifically permitted in this section. cases specifically permitted in this section.
[[anchor12: RFC Editor: please insert the proper error codes for [[anchor11: RFC Editor: please insert the proper error codes for
"5.6.y" and "2.6.y" after IANA has made the relevant assignments.]] "5.6.y" and "2.6.y" after IANA has made the relevant assignments.]]
4. IANA Considerations 4. IANA Considerations
IANA is requested to add a new value "UTF8SMTP" to the SMTP Service IANA is requested to add a new value "UTF8SMTP" to the SMTP Service
Extension subregistry of the Mail Parameters registry, according to Extension subregistry of the Mail Parameters registry, according to
the following data: the following data:
+----------+---------------------------------+-----------+ +----------+---------------------------------+-----------+
| Keywords | Description | Reference | | Keywords | Description | Reference |
skipping to change at page 16, line 50 skipping to change at page 17, line 26
derived or copied from [Klensin-emailaddr] with the permission of the derived or copied from [Klensin-emailaddr] with the permission of the
author. Significant comments and suggestions were received from author. Significant comments and suggestions were received from
Xiaodong LEE, Nai-Wen Hsu, Yangwoo KO, Yoshiro YONEYA, and other Xiaodong LEE, Nai-Wen Hsu, Yangwoo KO, Yoshiro YONEYA, and other
members of the JET team and were incorporated into the specification. members of the JET team and were incorporated into the specification.
Additional important comments and suggestions, and often specific Additional important comments and suggestions, and often specific
text, were contributed by many members of the WG and design team. text, were contributed by many members of the WG and design team.
Those contributions include material from John C Klensin, Charles Those contributions include material from John C Klensin, Charles
Lindsey, Dave Crocker, Harald Tveit Alvestrand, Marcos Sanz, Chris Lindsey, Dave Crocker, Harald Tveit Alvestrand, Marcos Sanz, Chris
Newman, Martin Duerst, Edmon Chung, Tony Finch, Kari Hurtta, Randall Newman, Martin Duerst, Edmon Chung, Tony Finch, Kari Hurtta, Randall
Gellens, Frank Ellermann, Alexey Melnikov, Pete Resnick, S. Gellens, Frank Ellermann, Alexey Melnikov, Pete Resnick, S.
Moonesamy, Soobok Lee, Shawn Steele, Alfred Hoenes and Miguel Garcia. Moonesamy, Soobok Lee, Shawn Steele, Alfred Hoenes Miguel Garcia,
Magnus Westerlund and Lars Eggert. Of course, none of the
Of course, none of the individuals are necessarily responsible for individuals are necessarily responsible for the combination of ideas
the combination of ideas represented here. represented here.
7. Change History 7. Change History
[[anchor16: RFC Editor: Please remove this section.]] [[anchor15: RFC Editor: Please remove this section.]]
7.1. draft-ietf-eai-smtpext: Version 00 7.1. draft-ietf-eai-smtpext: Version 00
This version supercedes draft-yao-ima-smtpext-03.txt. It refines the This version supercedes draft-yao-ima-smtpext-03.txt. It refines the
ABNF definition of the internationalized email address. It ABNF definition of the internationalized email address. It
represents as the EAI working group document. represents as the EAI working group document.
7.2. draft-ietf-eai-smtpext: Version 01 7.2. draft-ietf-eai-smtpext: Version 01
o Upgraded to reflect discussions during IETF 66. o Upgraded to reflect discussions during IETF 66.
skipping to change at page 19, line 4 skipping to change at page 19, line 30
modifications to the XML to produce a version that has better odds modifications to the XML to produce a version that has better odds
of getting through the various checkers and validators. of getting through the various checkers and validators.
7.11. draft-ietf-eai-smtpext: Version 10 7.11. draft-ietf-eai-smtpext: Version 10
o Refine the text o Refine the text
o Add some text about "ALT-ADDRESS" in the section 2.4 o Add some text about "ALT-ADDRESS" in the section 2.4
o Add the appendix A.5 o Add the appendix A.5
7.12. draft-ietf-eai-smtpext: Version 11 7.12. draft-ietf-eai-smtpext: Version 11
o Refine the text o Refine the text
o Reference updating o Reference updating
7.13. draft-ietf-eai-smtpext: Version 12 7.13. draft-ietf-eai-smtpext: Version 12
o Remove the section 1.2 about Proposal Context and merge the text o Remove the section 1.2 about Proposal Context and merge the text
into new section 2 into new section 2
o Add the new section 2 about overview of operation o Add the new section 2 about overview of operation
o Update the IANA consideration o Update the IANA consideration
o Refine the text o Refine the text
8. References 7.14. draft-ietf-eai-smtpext: Version 13
o Update the Abstract
o Refine the syntax about the equivalent of import clause
8. References
8.1. Normative References 8.1. Normative References
[ASCII] American National Standards Institute (formerly United [ASCII] American National Standards Institute (formerly United
States of America Standards Institute), "USA Code for States of America Standards Institute), "USA Code for
Information Interchange", ANSI X3.4-1968, 1968. Information Interchange", ANSI X3.4-1968, 1968.
[EAI-dsn] Newman, C. and A. Melnikov, "SMTP extensions for DSNs", [EAI-dsn] Newman, C. and A. Melnikov, "SMTP extensions for DSNs",
draft-ietf-eai-dsn-06.txt (work in progress), draft-ietf-eai-dsn-06.txt (work in progress),
January 2008. January 2008.
[EAI-utf8header] [EAI-utf8header]
Abel, Y., "Transmission of Email Headers in UTF-8 Abel, Y., "Transmission of Email Headers in UTF-8
Encoding", draft-ietf-eai-utf8headers-09.txt (work in Encoding", draft-ietf-eai-utf8headers-12.txt (work in
progress), January 2008. progress), July 2008.
[RFC1652] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. [RFC1652] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D.
Crocker, "SMTP Service Extension for 8bit-MIMEtransport", Crocker, "SMTP Service Extension for 8bit-MIMEtransport",
RFC 1652, July 1994. RFC 1652, July 1994.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2821] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821, [RFC2821] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821,
April 2001. April 2001.
skipping to change at page 20, line 36 skipping to change at page 21, line 22
Hansen , T. and J. Klensin, "A Registry for SMTP Enhanced Hansen , T. and J. Klensin, "A Registry for SMTP Enhanced
Mail System Status Codes", Mail System Status Codes",
draft-hansen-4468upd-mailesc-registry-03 (work in draft-hansen-4468upd-mailesc-registry-03 (work in
progress), January 2008. progress), January 2008.
8.2. Informative References 8.2. Informative References
[EAI-downgrading] [EAI-downgrading]
YONEYA, Y., Ed. and K. Fujiwara, Ed., "Downgrading YONEYA, Y., Ed. and K. Fujiwara, Ed., "Downgrading
mechanism for Internationalized eMail Address", mechanism for Internationalized eMail Address",
draft-ietf-eai-downgrade-06 (work in progress), 1 2008. draft-ietf-eai-downgrade-07 (work in progress), 3 2008.
[Klensin-emailaddr] [Klensin-emailaddr]
Klensin, J., "Internationalization of Email Addresses", Klensin, J., "Internationalization of Email Addresses",
draft-klensin-emailaddr-i18n-03 (work in progress), draft-klensin-emailaddr-i18n-03 (work in progress),
July 2005. July 2005.
[RFC0974] Partridge, C., "Mail routing and the domain system", [RFC0974] Partridge, C., "Mail routing and the domain system",
RFC 974, January 1986. RFC 974, January 1986.
[RFC2033] Myers, J., "Local Mail Transfer Protocol", RFC 2033, [RFC2033] Myers, J., "Local Mail Transfer Protocol", RFC 2033,
October 1996. October 1996.
[RFC2821bis]
Klensin, J., "Simple Mail Transfer Protocol",
draft-klensin-rfc2821bis-10 (work in progress), 4 2008.
[RFC3030] Vaudreuil, G., "SMTP Service Extensions for Transmission [RFC3030] Vaudreuil, G., "SMTP Service Extensions for Transmission
of Large and Binary MIME Messages", RFC 3030, of Large and Binary MIME Messages", RFC 3030,
December 2000. December 2000.
[RFC3207] Hoffman, P., "SMTP Service Extension for Secure SMTP over [RFC3207] Hoffman, P., "SMTP Service Extension for Secure SMTP over
Transport Layer Security", RFC 3207, February 2002. Transport Layer Security", RFC 3207, February 2002.
[RFC4954] Siemborski, R. and A. Melnikov, "SMTP Service Extension [RFC4954] Siemborski, R. and A. Melnikov, "SMTP Service Extension
for Authentication", RFC 4954, July 2007. for Authentication", RFC 4954, July 2007.
skipping to change at page 23, line 4 skipping to change at page 23, line 34
Authors' Addresses Authors' Addresses
Jiankang YAO (editor) Jiankang YAO (editor)
CNNIC CNNIC
No.4 South 4th Street, Zhongguancun No.4 South 4th Street, Zhongguancun
Beijing Beijing
Phone: +86 10 58813007 Phone: +86 10 58813007
Email: yaojk@cnnic.cn Email: yaojk@cnnic.cn
Wei MAO (editor) Wei MAO (editor)
CNNIC CNNIC
No.4 South 4th Street, Zhongguancun No.4 South 4th Street, Zhongguancun
Beijing Beijing
Phone: +86 10 58813055 Phone: +86 10 58812230
Email: maowei_ietf@cnnic.cn Email: maowei_ietf@cnnic.cn
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
 End of changes. 41 change blocks. 
59 lines changed or deleted 84 lines changed or added

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