draft-ietf-imapext-i18n-11.txt   draft-ietf-imapext-i18n-12.txt 
Network Working Group Chris Newman Network Working Group Chris Newman
Internet-Draft Sun Microsystems Internet-Draft Sun Microsystems
Intended Status: Proposed Standard Arnt Gulbrandsen Intended Status: Proposed Standard Arnt Gulbrandsen
Oryx Mail Systems GmhH Oryx Mail Systems GmhH
August 2007
Internet Message Access Protocol Internationalization Internet Message Access Protocol Internationalization
draft-ietf-imapext-i18n-11.txt draft-ietf-imapext-i18n-12.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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
skipping to change at page 1, line 30 skipping to change at page 1, line 32
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress". reference 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. The list of Internet- http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-
Draft Shadow Directories can be accessed at Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft expires in December 2007. This Internet-Draft expires in February 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
Internet Message Access Protocol (IMAP) version 4rev1 has basic Internet Message Access Protocol (IMAP) version 4rev1 has basic
support for non-ASCII characters in mailbox names and search support for non-ASCII characters in mailbox names and search
substrings. It also supports non-ASCII message headers and content substrings. It also supports non-ASCII message headers and content
encoded as specified by Multipurpose Internet Mail Extensions encoded as specified by Multipurpose Internet Mail Extensions
(MIME). This specification defines a collection of IMAP extensions (MIME). This specification defines a collection of IMAP extensions
which improve international support including comparator negotiation which improve international support including comparator negotiation
for search, sort and thread, language negotiation for international for search, sort and thread, language negotiation for international
Internet-draft August 2007
error text, and translations for namespace prefixes. error text, and translations for namespace prefixes.
Table of Contents Table of Contents
1. Conventions Used in this Document . . . . . . . . . . . . . . 2 1. Conventions Used in this Document . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
3. LANGUAGE Extension . . . . . . . . . . . . . . . . . . . . . 3 3. LANGUAGE Extension . . . . . . . . . . . . . . . . . . . . . 3
3.1 LANGUAGE Extension Requirements . . . . . . . . . . . . . . . 3 3.1 LANGUAGE Extension Requirements . . . . . . . . . . . . . . . 3
3.2 LANGUAGE Command . . . . . . . . . . . . . . . . . . . . . . 4 3.2 LANGUAGE Command . . . . . . . . . . . . . . . . . . . . . . 4
3.3 LANGUAGE Response . . . . . . . . . . . . . . . . . . . . . . 6 3.3 LANGUAGE Response . . . . . . . . . . . . . . . . . . . . . . 6
skipping to change at page 3, line 5 skipping to change at page 3, line 5
The formal syntax use the Augmented Backus-Naur Form (ABNF) The formal syntax use the Augmented Backus-Naur Form (ABNF)
[RFC4234] notation including the core rules defined in Appendix A. [RFC4234] notation including the core rules defined in Appendix A.
The UTF8-related productions are defined in [RFC3629]. The UTF8-related productions are defined in [RFC3629].
In examples, "C:" and "S:" indicate lines sent by the client and In examples, "C:" and "S:" indicate lines sent by the client and
server respectively. If a single "C:" or "S:" label applies to server respectively. If a single "C:" or "S:" label applies to
multiple lines, then the line breaks between those lines are for multiple lines, then the line breaks between those lines are for
editorial clarity only and are not part of the actual protocol editorial clarity only and are not part of the actual protocol
exchange. exchange.
Internet-draft August 2007
2. Introduction 2. Introduction
This specification defines two IMAP4rev1 [RFC3501] extensions to This specification defines two IMAP4rev1 [RFC3501] extensions to
enhance international support. These extensions can be advertised enhance international support. These extensions can be advertised
and implemented separately. and implemented separately.
The LANGUAGE extension allows the client to request a suitable The LANGUAGE extension allows the client to request a suitable
language for protocol error messages and in combination with the language for protocol error messages and in combination with the
NAMESPACE extension [RFC2342] enables namespace translations. NAMESPACE extension [RFC2342] enables namespace translations.
skipping to change at page 4, line 4 skipping to change at page 4, line 4
A server that advertises this extension MUST use the language "i- A server that advertises this extension MUST use the language "i-
default" as described in [RFC2277] as its default language until default" as described in [RFC2277] as its default language until
another supported language is negotiated by the client. A server another supported language is negotiated by the client. A server
MUST include "i-default" as one of its supported languages. MUST include "i-default" as one of its supported languages.
Clients and servers that support this extension MUST also support Clients and servers that support this extension MUST also support
the NAMESPACE extension [RFC2342]. the NAMESPACE extension [RFC2342].
The LANGUAGE command is valid in all states. Clients are urged to The LANGUAGE command is valid in all states. Clients are urged to
issue LANGUAGE before authentication, since some servers send issue LANGUAGE before authentication, since some servers send
Internet-draft August 2007
valuable user information as part of authentication (e.g. "password valuable user information as part of authentication (e.g. "password
is correct, but expired"). is correct, but expired").
3.2 LANGUAGE Command 3.2 LANGUAGE Command
Arguments: Optional language range arguments. Arguments: Optional language range arguments.
Response: A possible LANGUAGE response (see section 3.3). Response: A possible LANGUAGE response (see section 3.3).
A possible NAMESPACE response (see section 3.4). A possible NAMESPACE response (see section 3.4).
skipping to change at page 5, line 4 skipping to change at page 5, line 4
is unable to enumerate the list of languages it supports it MAY is unable to enumerate the list of languages it supports it MAY
return a tagged NO response to the enumeration request. return a tagged NO response to the enumeration request.
< The server defaults to using English i-default responses until < The server defaults to using English i-default responses until
the user explicitly changes the language. > the user explicitly changes the language. >
C: A001 LOGIN KAREN PASSWORD C: A001 LOGIN KAREN PASSWORD
S: A001 OK LOGIN completed S: A001 OK LOGIN completed
< Client requested MUL language, which no server supports. > < Client requested MUL language, which no server supports. >
Internet-draft August 2007
C: A002 LANGUAGE MUL C: A002 LANGUAGE MUL
S: A002 NO Unsupported language MUL S: A002 NO Unsupported language MUL
< A LANGUAGE command with no arguments is a request to enumerate < A LANGUAGE command with no arguments is a request to enumerate
the list of languages the server supports. > the list of languages the server supports. >
C: A003 LANGUAGE C: A003 LANGUAGE
S: * LANGUAGE (EN DE IT i-default) S: * LANGUAGE (EN DE IT i-default)
S: A003 OK Supported languages have been enumerated S: A003 OK Supported languages have been enumerated
skipping to change at page 6, line 5 skipping to change at page 6, line 5
S: * LANGUAGE (DE) S: * LANGUAGE (DE)
S: D003 OK Sprachwechsel durch LANGUAGE-Befehl ausgefuehrt S: D003 OK Sprachwechsel durch LANGUAGE-Befehl ausgefuehrt
< Server does not speak French, but does speak English. User < Server does not speak French, but does speak English. User
speaks Canadian French and Canadian English. > speaks Canadian French and Canadian English. >
C: E001 LANGUAGE FR-CA EN-CA C: E001 LANGUAGE FR-CA EN-CA
S: * LANGUAGE (EN) S: * LANGUAGE (EN)
S: E001 OK Now speaking English S: E001 OK Now speaking English
Internet-draft August 2007
3.3 LANGUAGE Response 3.3 LANGUAGE Response
Contents: A list of one or more language tags. Contents: A list of one or more language tags.
The LANGUAGE response occurs as a result of a LANGUAGE command. A The LANGUAGE response occurs as a result of a LANGUAGE command. A
LANGUAGE response with a list containing a single language tag LANGUAGE response with a list containing a single language tag
indicates that the server is now using that language. A LANGUAGE indicates that the server is now using that language. A LANGUAGE
response with a list containing multiple language tags indicates the response with a list containing multiple language tags indicates the
server is communicating a list of available languages to the client, server is communicating a list of available languages to the client,
and no change in the active language has been made. and no change in the active language has been made.
skipping to change at page 7, line 4 skipping to change at page 7, line 4
3.5 Formal Syntax 3.5 Formal Syntax
The following syntax specification inherits ABNF [RFC4234] rules The following syntax specification inherits ABNF [RFC4234] rules
from IMAP4rev1 [RFC3501], IMAP4 Namespace [RFC2342], Tags for the from IMAP4rev1 [RFC3501], IMAP4 Namespace [RFC2342], Tags for the
Identifying Languages [RFC4646], UTF-8 [RFC3629] and Collected Identifying Languages [RFC4646], UTF-8 [RFC3629] and Collected
Extensions to IMAP4 ABNF [RFC4466]. Extensions to IMAP4 ABNF [RFC4466].
command-any =/ language-cmd command-any =/ language-cmd
; LANGUAGE command is valid in all states ; LANGUAGE command is valid in all states
Internet-draft August 2007
language-cmd = "LANGUAGE" *(SP lang-range-quoted) language-cmd = "LANGUAGE" *(SP lang-range-quoted)
response-payload =/ language-data / comparator-data response-payload =/ language-data
language-data = "LANGUAGE" SP "(" lang-tag-quoted *(SP lang-tag- language-data = "LANGUAGE" SP "(" lang-tag-quoted *(SP
quoted) ")" lang-tag-quoted) ")"
namespace-trans = SP DQUOTE "TRANSLATION" DQUOTE SP "(" string ")" namespace-trans = SP DQUOTE "TRANSLATION" DQUOTE SP "(" string ")"
; the string is encoded in Modified UTF-7. ; the string is encoded in Modified UTF-7.
; this is a subset of the syntax permitted by ; this is a subset of the syntax permitted by
; the Namespace-Response-Extension rule in [RFC4466] ; the Namespace-Response-Extension rule in [RFC4466]
lang-range-quoted = astring lang-range-quoted = astring
; Once any literal wrapper or quoting is removed, this ; Once any literal wrapper or quoting is removed, this
; follows the language-range rule in [RFC4647] ; follows the language-range rule in [RFC4647]
skipping to change at page 8, line 4 skipping to change at page 8, line 4
This section defines an IMAP extension to negotiate use of This section defines an IMAP extension to negotiate use of
comparators [RFC4790] to internationalize IMAP SEARCH, SORT and comparators [RFC4790] to internationalize IMAP SEARCH, SORT and
THREAD. The IMAP extension consists of a new command to determine THREAD. The IMAP extension consists of a new command to determine
or change the active comparator and a new response to indicate the or change the active comparator and a new response to indicate the
active comparator and possibly other available comparators. active comparator and possibly other available comparators.
The term "default comparator" refers to the comparator which is used The term "default comparator" refers to the comparator which is used
by SEARCH and SORT absent any negotiation using the COMPARATOR by SEARCH and SORT absent any negotiation using the COMPARATOR
command. The term "active comparator" refers to the comparator command. The term "active comparator" refers to the comparator
Internet-draft August 2007
which will be used within a session e.g. by SEARCH and SORT. The which will be used within a session e.g. by SEARCH and SORT. The
COMPARATOR command is used to change the active comparator. COMPARATOR command is used to change the active comparator.
The active comparator applies to the following SEARCH keys: "BCC", The active comparator applies to the following SEARCH keys: "BCC",
"BODY", "CC", "FROM", "SUBJECT", "TEXT", "TO" and "HEADER". If the "BODY", "CC", "FROM", "SUBJECT", "TEXT", "TO" and "HEADER". If the
server also advertises the "SORT" extension, then the active server also advertises the "SORT" extension, then the active
comparator applies to the following SORT keys: "CC", "FROM", comparator applies to the following SORT keys: "CC", "FROM",
"SUBJECT" and "TO". If the server advertises THREAD=ORDEREDSUBJECT, "SUBJECT" and "TO". If the server advertises THREAD=ORDEREDSUBJECT,
then the active comparator applies to the ORDEREDSUBJECT threading then the active comparator applies to the ORDEREDSUBJECT threading
algorithm. If the server advertises THREAD=REFERENCES, then the algorithm. If the server advertises THREAD=REFERENCES, then the
skipping to change at page 9, line 4 skipping to change at page 9, line 4
SEARCH charset. SEARCH charset.
The COMPARATOR command is valid in authenticated and selected The COMPARATOR command is valid in authenticated and selected
states. states.
Note that since SEARCH uses the substring operation, IMAP servers Note that since SEARCH uses the substring operation, IMAP servers
can only implement collations that offer the substring operation can only implement collations that offer the substring operation
(see [RFC4790 section 4.2.2). Since SORT uses ordering operation (see [RFC4790 section 4.2.2). Since SORT uses ordering operation
(and by implication equality), IMAP servers which advertise the SORT (and by implication equality), IMAP servers which advertise the SORT
extension can only implement collations that offer all three extension can only implement collations that offer all three
Internet-draft August 2007
operations (see [RFC4790] sections 4.2.2-4). operations (see [RFC4790] sections 4.2.2-4).
If the active collation does not provide the operations needed by an If the active collation does not provide the operations needed by an
IMAP command, the server MUST respond with a tagged BAD. IMAP command, the server MUST respond with a tagged BAD.
4.2 Comparators and Character Encodings 4.2 Comparators and Character Encodings
When SEARCH, SORT, THREAD or another command needs to perform When SEARCH, SORT, THREAD or another command needs to perform
collation operations on messages (or on the command's arguments), collation operations on messages (or on the command's arguments),
the server MUST remove MIME encoding (see [RFC2047] for headers and the server MUST remove MIME encoding (see [RFC2047] for headers and
[RFC2045] for bodyparts) and convert character encodings compatibly [RFC2045] for bodyparts) and convert character encodings compatibly
before doing the collation operation. before doing the collation operation.
Strings encoded using unknown character encodings should never match Strings encoded using unknown character encodings should sort
when using the SEARCH command, and should sort together with invalid together with invalid input (as defined by the active collation) for
input (as defined by the active collation) for the SORT and THREAD the SORT and THREAD commands.
commands.
4.3 COMPARATOR Command 4.3 COMPARATOR Command
Arguments: Optional comparator order arguments. Arguments: Optional comparator order arguments.
Response: A possible COMPARATOR response (see Section 4.4). Response: A possible COMPARATOR response (see Section 4.4).
Result: OK - Command completed Result: OK - Command completed
NO - No matching comparator found NO - No matching comparator found
BAD - arguments invalid BAD - arguments invalid
skipping to change at page 10, line 4 skipping to change at page 10, line 4
matches the specified patterns. matches the specified patterns.
The argument "default" refers to the server's default comparator. The argument "default" refers to the server's default comparator.
Otherwise each argument is an collation specification as defined in Otherwise each argument is an collation specification as defined in
the Internet Application Protocol Comparator Registry [RFC4790]. the Internet Application Protocol Comparator Registry [RFC4790].
< The client requests activating a Czech comparator if possible, < The client requests activating a Czech comparator if possible,
or else a generic international comparator which it considers or else a generic international comparator which it considers
suitable for Czech. The server picks the first supported suitable for Czech. The server picks the first supported
comparator. > comparator. >
Internet-draft August 2007
C: A001 COMPARATOR "cz;*" i;basic C: A001 COMPARATOR "cz;*" i;basic
S: * COMPARATOR i;basic S: * COMPARATOR i;basic
S: A001 OK Will use i;basic for collation S: A001 OK Will use i;basic for collation
4.4 COMPARATOR Response 4.4 COMPARATOR Response
Contents: The active comparator. Contents: The active comparator.
An optional list of available matching comparators An optional list of available matching comparators
The COMPARATOR response occurs as a result of a COMPARATOR command. The COMPARATOR response occurs as a result of a COMPARATOR command.
skipping to change at page 10, line 31 skipping to change at page 10, line 34
The following syntax specification inherits ABNF [RFC4234] rules The following syntax specification inherits ABNF [RFC4234] rules
from IMAP4rev1 [RFC3501], and Internet Application Protocol from IMAP4rev1 [RFC3501], and Internet Application Protocol
Comparator Registry [RFC4790]. Comparator Registry [RFC4790].
command-auth =/ comparator-cmd command-auth =/ comparator-cmd
resp-text-code =/ "BADCOMPARATOR" / "BADMATCH" resp-text-code =/ "BADCOMPARATOR" / "BADMATCH"
comparator-cmd = "COMPARATOR" *(SP comp-order-quoted) comparator-cmd = "COMPARATOR" *(SP comp-order-quoted)
response-payload =/ comparator-data
comparator-data = "COMPARATOR" SP comp-sel-quoted [SP "(" comparator-data = "COMPARATOR" SP comp-sel-quoted [SP "("
comp-id-quoted *(SP comp-id-quoted) ")"] comp-id-quoted *(SP comp-id-quoted) ")"]
comp-id-quoted = astring comp-id-quoted = astring
; Once any literal wrapper or quoting is removed, this ; Once any literal wrapper or quoting is removed, this
; follows the collation-id rule from [RFC4790] ; follows the collation-id rule from [RFC4790]
comp-order-quoted = astring comp-order-quoted = astring
; Once any literal wrapper or quoting is removed, this ; Once any literal wrapper or quoting is removed, this
; follows the collation-order rule from [RFC4790] ; follows the collation-order rule from [RFC4790]
comp-sel-quoted = astring comp-sel-quoted = astring
; Once any literal wrapper or quoting is removed, this ; Once any literal wrapper or quoting is removed, this
; follows the collation-selected rule from [RFC4790] ; follows the collation-selected rule from [RFC4790]
Internet-draft August 2007
5. Other IMAP Internationalization Issues 5. Other IMAP Internationalization Issues
The following sections provide an overview of various other IMAP The following sections provide an overview of various other IMAP
internationalization issues. These issues are not resolved by this internationalization issues. These issues are not resolved by this
specification, but could be resolved by other standards work, such specification, but could be resolved by other standards work, such
as that being done by the EAI group (see [IMAP-EAI]). as that being done by the EAI group (see [IMAP-EAI]).
5.1 Unicode Userids and Passwords 5.1 Unicode Userids and Passwords
IMAP4rev1 presently restricts the userid and password fields of the IMAP4rev1 presently restricts the userid and password fields of the
skipping to change at page 12, line 4 skipping to change at page 12, line 4
we're ever going to be able to deploy UTF-8 mailbox names. Servers we're ever going to be able to deploy UTF-8 mailbox names. Servers
are encouraged to enforce them. are encouraged to enforce them.
5.3 UTF-8 Domains, Addresses and Mail Headers 5.3 UTF-8 Domains, Addresses and Mail Headers
There is now an IETF standard for Internationalizing Domain Names in There is now an IETF standard for Internationalizing Domain Names in
Applications [RFC3490]. While IMAP clients are free to support this Applications [RFC3490]. While IMAP clients are free to support this
standard, an argument can be made that it would be helpful to simple standard, an argument can be made that it would be helpful to simple
clients if the IMAP server could perform this conversion (the same clients if the IMAP server could perform this conversion (the same
argument would apply to MIME header encoding [RFC2047]). However, argument would apply to MIME header encoding [RFC2047]). However,
Internet-draft August 2007
it would be unwise to move forward with such work until the work in it would be unwise to move forward with such work until the work in
progress to define the format of international email addresses is progress to define the format of international email addresses is
complete. complete.
6. IANA Considerations 6. IANA Considerations
The IANA is requested to add LANGUAGE and COMPARATOR to the IMAP4 The IANA is requested to add LANGUAGE and COMPARATOR to the IMAP4
Capabilities Registry. [Note to IANA: Capabilities Registry. [Note to IANA:
http://www.iana.org/assignments/imap4-capabilities] http://www.iana.org/assignments/imap4-capabilities]
skipping to change at page 13, line 4 skipping to change at page 13, line 4
The LANGUAGE extension is based on a previous Internet draft by Mike The LANGUAGE extension is based on a previous Internet draft by Mike
Gahrns and Alexey Melnikov, a substantial portion of the text in Gahrns and Alexey Melnikov, a substantial portion of the text in
that section was written by them. Many people have participated in that section was written by them. Many people have participated in
discussions about an IMAP Language extension in the various fora of discussions about an IMAP Language extension in the various fora of
the IETF and Internet working groups, so any list of contributors is the IETF and Internet working groups, so any list of contributors is
bound to be incomplete. However, the authors would like to thank bound to be incomplete. However, the authors would like to thank
Andrew McCown for early work on the original proposal, John Myers Andrew McCown for early work on the original proposal, John Myers
for suggestions regarding the namespace issue, along with Jutta for suggestions regarding the namespace issue, along with Jutta
Degener, Mark Crispin, Mark Pustilnik, Larry Osterman, Cyrus Daboo Degener, Mark Crispin, Mark Pustilnik, Larry Osterman, Cyrus Daboo
and Martin Duerst for their many suggestions that have been and Martin Duerst for their many suggestions that have been
Internet-draft August 2007
incorporated into this document. incorporated into this document.
Initial discussion of the COMPARATOR extension involved input from Initial discussion of the COMPARATOR extension involved input from
Mark Crispin and other participants of the IMAP Extensions WG. Mark Crispin and other participants of the IMAP Extensions WG.
9. Relevant Standards for i18n IMAP Implementations 9. Relevant Standards for i18n IMAP Implementations
This is a non-normative list of standards to consider when This is a non-normative list of standards to consider when
implementing i18n aware IMAP software. implementing i18n aware IMAP software.
skipping to change at page 14, line 4 skipping to change at page 14, line 4
[RFC2342] Gahrns, Newman, "IMAP4 Namespace", RFC 2342, May 1998. [RFC2342] Gahrns, Newman, "IMAP4 Namespace", RFC 2342, May 1998.
[RFC3501] Crispin, "INTERNET MESSAGE ACCESS PROTOCOL - VERSION [RFC3501] Crispin, "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
4rev1", RFC 3501, March 2003. 4rev1", RFC 3501, March 2003.
[RFC3629] Yergeau, "UTF-8, a transformation format of ISO 10646", [RFC3629] Yergeau, "UTF-8, a transformation format of ISO 10646",
STD 63, RFC 3629, November 2003. STD 63, RFC 3629, November 2003.
[RFC4234] Crocker, Overell, "Augmented BNF for Syntax [RFC4234] Crocker, Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, Brandenburg Specifications: ABNF", RFC 4234, Brandenburg
Internet-draft August 2007
Internetworking, Demon Internet Ltd, October 2005. Internetworking, Demon Internet Ltd, October 2005.
[RFC4422] Melnikov, Zeilenga, "Simple Authentication and Security [RFC4422] Melnikov, Zeilenga, "Simple Authentication and Security
Layer (SASL)", RFC 4422, June 2006. Layer (SASL)", RFC 4422, June 2006.
[RFC4466] Melnikov, Daboo, "Collected Extensions to IMAP4 ABNF", [RFC4466] Melnikov, Daboo, "Collected Extensions to IMAP4 ABNF",
RFC 4466, Isode Ltd., April 2006. RFC 4466, Isode Ltd., April 2006.
[RFC4646] Philips, Davis, "Tags for Identifying Languages", BCP 47, [RFC4646] Philips, Davis, "Tags for Identifying Languages", BCP 47,
RFC 4646, September 2006. RFC 4646, September 2006.
skipping to change at page 15, line 4 skipping to change at page 15, line 4
Continuations", RFC 2231, November 1997. Continuations", RFC 2231, November 1997.
[RFC3490] Faltstrom, Hoffman, Costello, "Internationalizing Domain [RFC3490] Faltstrom, Hoffman, Costello, "Internationalizing Domain
Names in Applications (IDNA)", RFC 3490, March 2003. Names in Applications (IDNA)", RFC 3490, March 2003.
[RFC3492] Costello, "Punycode: A Bootstring encoding of Unicode for [RFC3492] Costello, "Punycode: A Bootstring encoding of Unicode for
Internationalized Domain Names in Applications (IDNA)", Internationalized Domain Names in Applications (IDNA)",
RFC 3492, March 2003. RFC 3492, March 2003.
[METADATA] Daboo, C., "IMAP METADATA Extension", draft-daboo-imap- [METADATA] Daboo, C., "IMAP METADATA Extension", draft-daboo-imap-
Internet-draft August 2007
annotatemore-10 (work in progress), November 2006. annotatemore-10 (work in progress), November 2006.
[IMAP-EAI] Resnick, Newman, "IMAP Support for UTF-8", draft-ietf- [IMAP-EAI] Resnick, Newman, "IMAP Support for UTF-8", draft-ietf-
eai-imap-utf8 (work in progress), May 2006. eai-imap-utf8 (work in progress), May 2006.
Authors' Addresses Authors' Addresses
Chris Newman Chris Newman
Sun Microsystems Sun Microsystems
3401 Centrelake Dr., Suite 410 3401 Centrelake Dr., Suite 410
skipping to change at page 16, line 5 skipping to change at page 16, line 5
Arnt Gulbrandsen Arnt Gulbrandsen
Oryx Mail Systems GmbH Oryx Mail Systems GmbH
Schweppermannstr. 8 Schweppermannstr. 8
D-81671 Muenchen D-81671 Muenchen
Germany Germany
Email: arnt@oryx.com Email: arnt@oryx.com
Fax: +49 89 4502 9758 Fax: +49 89 4502 9758
Internet-draft August 2007
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology described to pertain to the implementation or use of the technology described
in this document or the extent to which any license under such in this document or the extent to which any license under such
rights might or might not be available; nor does it represent that rights might or might not be available; nor does it represent that
it has made any independent effort to identify any such rights. it has made any independent effort to identify any such rights.
Information on the procedures with respect to rights in RFC Information on the procedures with respect to rights in RFC
documents can be found in BCP 78 and BCP 79. documents can be found in BCP 78 and BCP 79.
 End of changes. 22 change blocks. 
9 lines changed or deleted 53 lines changed or added

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