draft-ietf-imapext-i18n-07.txt   draft-ietf-imapext-i18n-08.txt 
Network Working Group Chris Newman Network Working Group Chris Newman
Request for Comments: DRAFT Sun Microsystems Request for Comments: DRAFT Sun Microsystems
Arnt Gulbrandsen Arnt Gulbrandsen
Oryx Mail Systems GmhH Oryx Mail Systems GmhH
November 2006 December 2006
Internet Message Access Protocol Internationalization Internet Message Access Protocol Internationalization
draft-ietf-imapext-i18n-07.txt draft-ietf-imapext-i18n-08.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 2, line 5 skipping to change at page 2, line 5
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
error text, and translations for namespace prefixes. error text, and translations for namespace prefixes.
Internet-draft November 2006 Internet-draft December 2006
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 . . . . . . . . . . . . . . . . . . . . . . 5 3.3 LANGUAGE Response . . . . . . . . . . . . . . . . . . . . . . 5
3.4 TRANSLATION Extension to the NAMESPACE Response . . . . . . . 6 3.4 TRANSLATION Extension to the NAMESPACE 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 November 2006 Internet-draft December 2006
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 3, line 49 skipping to change at page 3, line 49
IMAP servers that support this extension MUST list the keyword IMAP servers that support this extension MUST list the keyword
LANGUAGE in their CAPABILITY response as well as in the greeting LANGUAGE in their CAPABILITY response as well as in the greeting
CAPABILITY data. CAPABILITY data.
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.
A client that supports this extension MUST be prepared for a Clients and servers that support this extension MUST also support
possible NAMESPACE response [RFC2342] from the server. the NAMESPACE extension [RFC2342].
The LANGUAGE command is valid in all states. The LANGUAGE command is valid in all states.
Internet-draft November 2006 Internet-draft December 2006
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).
Result: OK - Command completed Result: OK - Command completed
NO - Could not complete command NO - Could not complete command
BAD - arguments invalid BAD - arguments invalid
The LANGUAGE command requests that human-readable text emitted by The LANGUAGE command requests that human-readable text emitted by
the server be localized to a language matching one of the language the server be localized to a language matching one of the language
range argument as described by section 2.5 of RFC 3066. range argument as described by section 2.5 of RFC 3066.
If the command succeeds, the server will return human-readable If the command succeeds, the server will return human-readable
responses in the first supported language specified. The first responses in the first supported language specified. These
response affected by the change is the tagged OK response to the responses will be in UTF-8 [RFC3629]. The server MUST send a
LANGUAGE command. These responses will be in UTF-8 [RFC3629]. LANGUAGE response specifying the language used, and the change takes
effect immediately after the LANGUAGE response.
If the command fails, the server will continue to return human- If the command fails, the server continues to return human-readable
readable responses in the language it was previously using. responses in the language it was previously using.
The client MUST NOT use MUL (Multiple languages) or UND The special "*" language range argument indicates a request to use a
(Undetermined) language tags and the server MUST return BAD if language designated as preferred by the server administrator. The
either tag is used, even if other, legal, arguments are also preferred language MAY vary based on the currently active user.
supplied. The special "*" language range argument indicates a
request to use a language designated as preferred by the server
administrator. The preferred language MAY vary based on the
currently active user.
If a language range does not match a known language tag exactly but If a language range does not match a known language tag exactly but
does match a language by the rules of [RFC4647], the server MUST does match a language by the rules of [RFC4647], the server MUST
send an untagged LANGUAGE response indicating the language selected. send an untagged LANGUAGE response indicating the language selected.
If there aren't any arguments, the server SHOULD send an untagged If there aren't any arguments, the server SHOULD send an untagged
LANGUAGE response listing the languages it supports. If the server LANGUAGE response listing the languages it supports. If the server
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. Server MUST reply with BAD. > < Client requested MUL language, which no server supports. >
C: A002 LANGUAGE MUL C: A002 LANGUAGE MUL
S: A002 NO Unsupported language MUL
Internet-draft November 2006 Internet-draft December 2006
S: A002 BAD Invalid 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
C: B001 LANGUAGE C: B001 LANGUAGE
S: B001 NO Server is unable to enumerate supported languages S: B001 NO Server is unable to enumerate supported languages
< Once the client changes the language, all responses will be in < Once the client changes the language, all responses will be in
that language starting with the tagged OK to the LANGUAGE that language starting after the LANGUAGE response. Note that
command. Because RFCs are in US-ASCII, this document uses an this includes the NAMESPACE response. Because RFCs are in US-
ASCII transcription rather than UTF-8 text, e.g. ue in the ASCII, this document uses an ASCII transcription rather than
word "ausgefuehrt" > UTF-8 text, e.g. ue in the word "ausgefuehrt" >
C: A004 LANGUAGE DE C: C001 LANGUAGE DE
S: A004 OK Sprachwechsel durch LANGUAGE-Befehl ausgefuehrt S: * LANGUAGE (DE)
S: * NAMESPACE (("" "/")) (("Other Users/" "/" "TRANSLATION"
("Andere Ben&APw-tzer/"))) (("Public Folders/" "/"
"TRANSLATION" ("Gemeinsame Mailboxen/")))
S: C001 OK Sprachwechsel durch LANGUAGE-Befehl ausgefuehrt
< If a server does not support the requested primary language, < If a server does not support the requested primary language,
responses will continue to be returned in the current language responses will continue to be returned in the current language
the server is using. > the server is using. >
C: A005 LANGUAGE FR C: D001 LANGUAGE FR
S: A005 NO Diese Sprache ist nicht unterstuetzt S: D001 NO Diese Sprache ist nicht unterstuetzt
C: D002 LANGUAGE DE-IT
C: A006 LANGUAGE DE-IT
S: * LANGUAGE (DE-IT) S: * LANGUAGE (DE-IT)
S: A006 OK Sprachwechsel durch LANGUAGE-Befehl ausgefuehrt S: * NAMESPACE (("" "/"))(("Other Users/" "/" "TRANSLATION"
C: A007 LANGUAGE "*" ("Andere Ben&APw-tzer/"))) (("Public Folders/" "/"
"TRANSLATION" ("Gemeinsame Mailboxen/")))
S: D002 OK Sprachwechsel durch LANGUAGE-Befehl ausgefuehrt
C: D003 LANGUAGE "*"
S: * LANGUAGE (DE) S: * LANGUAGE (DE)
S: A007 OK LANGUAGE-Befehl erfolgreich 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: A008 LANGUAGE FR-CA EN-CA C: E001 LANGUAGE FR-CA EN-CA
S: * LANGUAGE (EN) S: * LANGUAGE (EN)
S: A008 OK Now speaking English S: E001 OK Now speaking English
Internet-draft December 2006
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.
Internet-draft November 2006
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.
3.4 TRANSLATION Extension to the NAMESPACE Response 3.4 TRANSLATION Extension to the NAMESPACE Response
If as a result of the newly negotiated language, localized If localized representations of the namespace prefixes are available
representations of the namespace prefixes are available, the server in the selected language, the server SHOULD include these in the
SHOULD include these in the TRANSLATION extension to the NAMESPACE TRANSLATION extension to the NAMESPACE response.
response.
OPEN ISSUE: I would appreciate concrete suggestions about how to do
NAMESPACE better.
The TRANSLATION extension to the NAMESPACE response returns a single The TRANSLATION extension to the NAMESPACE response returns a single
string, containing the modified UTF-7 [RFC3501] encoded translation string, containing the modified UTF-7 [RFC3501] encoded translation
of the namespace prefix. It is the responsibility of the client to of the namespace prefix. It is the responsibility of the client to
convert between the namespace prefix and the translation of the convert between the namespace prefix and the translation of the
namespace prefix when presenting mailbox names to the user. namespace prefix when presenting mailbox names to the user.
In this example a server supports the IMAP4 NAMESPACE command. It In this example a server supports the IMAP4 NAMESPACE command. It
uses no prefix to the user's Personal Namespace, a prefix of "Other uses no prefix to the user's Personal Namespace, a prefix of "Other
Users" to its Other Users' Namespace and a prefix of "Public Users" to its Other Users' Namespace and a prefix of "Public
skipping to change at page 7, line 5 skipping to change at page 7, line 5
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], and UTF-8 [RFC3629]. Identifying Languages [RFC4646], and UTF-8 [RFC3629].
command-any =/ language-cmd command-any =/ language-cmd
; LANGUAGE command is valid in all states ; LANGUAGE command is valid in all states
language-cmd = "LANGUAGE" *(SP lang-range-quoted) language-cmd = "LANGUAGE" *(SP lang-range-quoted)
Internet-draft November 2006 Internet-draft December 2006
response-payload =/ language-data / comparator-data response-payload =/ language-data / comparator-data
language-data = "LANGUAGE" SP "(" lang-tag-quoted *(SP lang-tag- language-data = "LANGUAGE" SP "(" lang-tag-quoted *(SP lang-tag-
quoted) ")" 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 [RFC2342] ; the Namespace_Response_Extension rule in [RFC2342]
skipping to change at page 8, line 5 skipping to change at page 8, line 5
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
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.
Internet-draft November 2006 Internet-draft December 2006
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
active comparator applies to the subject field comparisons done by active comparator applies to the subject field comparisons done by
REFERENCES threading algorithm. Future extensions may choose to REFERENCES threading algorithm. Future extensions may choose to
skipping to change at page 9, line 5 skipping to change at page 9, line 5
states. states.
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.
Internet-draft November 2006 Internet-draft December 2006
Strings encoded using unknown character encodings should never match Strings encoded using unknown character encodings should never match
when using the SEARCH command, and should sort together with invalid when using the SEARCH command, and should sort together with invalid
input for the SORT and THREAD commands. input for the SORT and THREAD 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).
skipping to change at page 9, line 38 skipping to change at page 9, line 38
The argument "*" refers to the server's default comparator. The argument "*" refers to the server's default comparator.
Otherwise each argument is an comparator specification as defined in Otherwise each argument is an comparator specification as defined in
the Internet Application Protocol Comparator Registry [RFCxxxx]. the Internet Application Protocol Comparator Registry [RFCxxxx].
< 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. >
C: A001 COMPARATOR cz;* i;basic* C: A001 COMPARATOR cz;* i;basic
S: * COMPARATOR i;basic;uca=3.1.1;uv=3.2 S: * COMPARATOR i;basic
S: A001 OK Will use i;basic;uca=3.1.1;uv=3.2 for collation S: A001 OK Will use i;basic for collation
< The client requests pure octet matching, then does a search < The client requests pure octet matching, then does a search
for potential GIF files, then switches back to its usual for potential GIF files, then switches back to its usual
comparator. Note that this may not work on all IMAP servers, comparator. Note that this may not work on all IMAP servers,
see RFC 3501, page 50, second paragraph. > see RFC 3501, page 50, second paragraph. >
C: B123 COMPARATOR i;octet C: B123 COMPARATOR i;octet
S: * COMPARATOR i;octet S: * COMPARATOR i;octet
S: B123 OK S: B123 OK
C: B124 SEARCH OR BODY GIF87A BODY GIF89A C: B124 SEARCH OR BODY GIF87A BODY GIF89A
S: * SEARCH 42 69 S: * SEARCH 42 69
S: B124 OK S: B124 OK
Internet-draft November 2006 Internet-draft December 2006
C: B125 COMPARATOR cz;* i;basic* C: B125 COMPARATOR cz;* i;basic
S: * COMPARATOR i;basic;uca=3.1.1;uv=3.2 S: * COMPARATOR i;basic
S: B125 OK. S: B125 OK.
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.
The first argument in the comparator response is the name of the The first argument in the comparator response is the name of the
active comparator. The second argument is a list of comparators active comparator. The second argument is a list of comparators
skipping to change at page 11, line 5 skipping to change at page 11, line 5
; follows the collation-name rule from [RFCxxxx] ; follows the collation-name rule from [RFCxxxx]
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 [RFCxxxx] ; follows the collation-order rule from [RFCxxxx]
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-sel rule from [RFCxxxx] ; follows the collation-sel rule from [RFCxxxx]
Internet-draft November 2006 Internet-draft December 2006
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
skipping to change at page 11, line 27 skipping to change at page 11, line 27
LOGIN command to US-ASCII. The "userid" and "password" fields of the LOGIN command to US-ASCII. The "userid" and "password" fields of the
IMAP LOGIN command are restricted to US-ASCII only until a future IMAP LOGIN command are restricted to US-ASCII only until a future
standards track RFC states otherwise. Servers are encouraged to standards track RFC states otherwise. Servers are encouraged to
validate both fields to make sure they conform to the formal syntax validate both fields to make sure they conform to the formal syntax
of UTF-8 and to reject the LOGIN command if that syntax is violated. of UTF-8 and to reject the LOGIN command if that syntax is violated.
Servers MAY reject the use of any 8-bit in the "userid" or Servers MAY reject the use of any 8-bit in the "userid" or
"password" field. "password" field.
When AUTHENTICATE is used, some servers may support userids and When AUTHENTICATE is used, some servers may support userids and
passwords in Unicode [RFC3490] since SASL (see [RFC4422]) allows passwords in Unicode [RFC3490] since SASL (see [RFC4422]) allows
that. However, such userids cannot be used as email addresses. that. However, such userids cannot be used as part of email
addresses.
5.2 UTF-8 Mailbox Names 5.2 UTF-8 Mailbox Names
The modified UTF-7 mailbox naming convention described in section The modified UTF-7 mailbox naming convention described in section
5.1.3 of RFC 3501 is best viewed as an transition from the status 5.1.3 of RFC 3501 is best viewed as an transition from the status
quo in 1996 when modified UTF-7 was first specified. At that time, quo in 1996 when modified UTF-7 was first specified. At that time,
there was widespread unofficial use of local character sets such as there was widespread unofficial use of local character sets such as
ISO-8859-1 and Shift-JIS for non-ASCII mailbox names, with resultant ISO-8859-1 and Shift-JIS for non-ASCII mailbox names, with resultant
non-interoperability. non-interoperability.
skipping to change at page 11, line 49 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 December 2006
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.
Internet-draft November 2006
6. IANA Considerations 6. IANA Considerations
The IANA is requested to add LANGUAGE and COMPARATOR to the IMAP The IANA is requested to add LANGUAGE and COMPARATOR to the IMAP
Extensions registry. Extensions registry.
7. Security Considerations 7. Security Considerations
The LANGUAGE extension makes a new command available in "Not The LANGUAGE extension makes a new command available in "Not
Authenticated" state in IMAP. Some IMAP implementations run with Authenticated" state in IMAP. Some IMAP implementations run with
root privilege when the server is in "Not Authenticated" state and root privilege when the server is in "Not Authenticated" state and
skipping to change at page 12, line 49 skipping to change at page 13, line 5
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
incorporated into this document. incorporated into this document.
Internet-draft December 2006
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.
Internet-draft November 2006
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.
o The LANGUAGE and COMPARATOR extensions to IMAP (this o The LANGUAGE and COMPARATOR extensions to IMAP (this
specification). specification).
o The 8-bit rules for mailbox naming in section 5.1 of RFC 3501. o The 8-bit rules for mailbox naming in section 5.1 of RFC 3501.
o The Mailbox International Naming Convention in section 5.1.3 of o The Mailbox International Naming Convention in section 5.1.3 of
RFC 3501. RFC 3501.
skipping to change at page 13, line 50 skipping to change at page 14, line 5
[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
Internetworking, Demon Internet Ltd, October 2005. Internetworking, Demon Internet Ltd, October 2005.
Internet-draft December 2006
[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.
Internet-draft November 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.
[RFC4647] Philips, Davis, "Matching of Language Tags", BCP 47, RFC [RFC4647] Philips, Davis, "Matching of Language Tags", BCP 47, RFC
4647, September 2006. 4647, September 2006.
[RFCxxxx] Newman, Duerst, Gulbrandsen, "Internet Application [RFCxxxx] Newman, Duerst, Gulbrandsen, "Internet Application
Protocol Comparator Registry", RFC-draft-newman-i18n- Protocol Comparator Registry", RFC-draft-newman-i18n-
comparator, September 2006 comparator, September 2006
skipping to change at page 14, line 50 skipping to change at page 15, line 5
imapext-sort-17 (work in progress), May 2004. imapext-sort-17 (work in progress), May 2004.
[METADATA] Daboo, C., "IMAP METADATA Extension", draft-daboo-imap- [METADATA] Daboo, C., "IMAP METADATA Extension", draft-daboo-imap-
annotatemore-10 (work in progress), November 2006. annotatemore-10 (work in progress), November 2006.
[BASIC] Newman, Duerst, Gulbrandsen, "i;basic - Registration of [BASIC] Newman, Duerst, Gulbrandsen, "i;basic - Registration of
the Unicode Collation Algorithm (UCA)", draft- the Unicode Collation Algorithm (UCA)", draft-
gulbrandsen-collation-basic (work in progress), November gulbrandsen-collation-basic (work in progress), November
2006. 2006.
[IMAP-EAI] Resnick, Newman, ""IMAP Support for UTF-8", draft-ietf- Internet-draft December 2006
iea-imap-utf8 (work in progress), May 2006.
Internet-draft November 2006 [IMAP-EAI] Resnick, Newman, "IMAP Support for UTF-8", draft-ietf-
iea-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
Ontario, CA 91761 Ontario, CA 91761
US US
Email: chris.newman@sun.com Email: chris.newman@sun.com
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-81781 Muenchen D-81781 Muenchen
Germany Germany
Email: arnt@oryx.com Email: arnt@oryx.com
Fax: +49 89 4502 9758 Fax: +49 89 4502 9758
Internet-draft November 2006 Internet-draft December 2006
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
 End of changes. 39 change blocks. 
69 lines changed or deleted 70 lines changed or added

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