draft-ietf-imapext-i18n-08.txt   draft-ietf-imapext-i18n-09.txt 
Network Working Group Chris Newman Network Working Group Chris Newman
Request for Comments: DRAFT Sun Microsystems Internet-Draft Sun Microsystems
Arnt Gulbrandsen Intended Status: Proposed Standard Arnt Gulbrandsen
Oryx Mail Systems GmhH Oryx Mail Systems GmhH
December 2006
Internet Message Access Protocol Internationalization Internet Message Access Protocol Internationalization
draft-ietf-imapext-i18n-08.txt draft-ietf-imapext-i18n-09.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 32 skipping to change at page 1, line 30
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 September 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). 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
error text, and translations for namespace prefixes. error text, and translations for namespace prefixes.
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
3.5 Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 6 3.5 Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 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 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.
The COMPARATOR extension allows the client to request a suitable The COMPARATOR extension allows the client to request a suitable
comparator which will modify the behavior of the base comparator which will modify the behavior of the base
specification's SEARCH command as well as the SORT and THREAD specification's SEARCH command as well as the SORT and THREAD
extensions [SORT]. This leverages the comparator registry extensions [SORT]. This leverages the comparator registry
[RFCxxxx]. [RFC4790].
3. LANGUAGE Extension 3. LANGUAGE Extension
IMAP allows server responses to include human-readable text that in IMAP allows server responses to include human-readable text that in
many cases needs to be presented to the user. But that text is many cases needs to be presented to the user. But that text is
limited to US-ASCII by the IMAP specification [RFC3501] in order to limited to US-ASCII by the IMAP specification [RFC3501] in order to
preserve backwards compatibility with deployed IMAP implementations. preserve backwards compatibility with deployed IMAP implementations.
This section specifies a way for an IMAP client to negotiate which This section specifies a way for an IMAP client to negotiate which
language the server should use when sending human-readable text. language the server should use when sending human-readable text.
skipping to change at page 4, line 5 skipping to change at page 4, line 5
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. The LANGUAGE command is valid in all states.
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). 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
skipping to change at page 5, line 4 skipping to change at page 5, line 4
< 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. >
C: A002 LANGUAGE MUL C: A002 LANGUAGE MUL
S: A002 NO Unsupported language MUL S: A002 NO Unsupported language MUL
Internet-draft December 2006
< 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
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 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.
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], 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 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 7, line 44 skipping to change at page 7, line 41
4. COMPARATOR Extension 4. COMPARATOR Extension
IMAP4rev1 [RFC3501] includes the SEARCH command which can be used to IMAP4rev1 [RFC3501] includes the SEARCH command which can be used to
locate messages matching criteria including human-readable text. locate messages matching criteria including human-readable text.
The SORT extension [SORT] to IMAP allows the client to ask the The SORT extension [SORT] to IMAP allows the client to ask the
server to determine the order of messages based on criteria server to determine the order of messages based on criteria
including human-readable text. These mechanisms require the ability including human-readable text. These mechanisms require the ability
to support non-English search and sort functions. to support non-English search and sort functions.
This section defines an IMAP extension to negotiate use of This section defines an IMAP extension to negotiate use of
comparators [RFCxxxx] 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
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 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
apply the active comparator to their SEARCH keys. apply the active comparator to their SEARCH keys.
skipping to change at page 8, line 29 skipping to change at page 8, line 27
base subject text from a Subject header occurs prior to the base subject text from a Subject header occurs prior to the
application of a comparator. application of a comparator.
4.1 COMPARATOR Extension Requirements 4.1 COMPARATOR Extension Requirements
IMAP servers that support this extension MUST list the keyword IMAP servers that support this extension MUST list the keyword
COMPARATOR in their CAPABILITY data once IMAP enters authenticated COMPARATOR in their CAPABILITY data once IMAP enters authenticated
state, and MAY list that keyword in other states. state, and MAY list that keyword in other states.
A server that advertises this extension MUST implement the i;ascii- A server that advertises this extension MUST implement the i;ascii-
casemap and i;octet comparators, as defined in [RFCxxxx]. A server casemap and i;octet comparators, as defined in [RFC4790]. A server
intended to be deployed globally MUST implement the i;basic intended to be deployed globally MUST implement the i;basic
comparator, as defined in [BASIC]. comparator, as defined in [BASIC].
A server that advertises this extension SHOULD use i;ascii-casemap A server that advertises this extension SHOULD use i;ascii-casemap
as the default comparator. The selection of the default comparator as the default comparator. The selection of the default comparator
MAY be adjustable by the server administrator, and MAY be sensitive MAY be adjustable by the server administrator, and MAY be sensitive
to the current user. Once the IMAP connection enters authenticated to the current user. Once the IMAP connection enters authenticated
state, the default comparator MUST remain static for the remainder state, the default comparator MUST remain static for the remainder
of that connection. of that connection.
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 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 31 skipping to change at page 9, line 29
The COMPARATOR command is used to determine or change the active The COMPARATOR command is used to determine or change the active
comparator. When issued with no arguments, it results in a comparator. When issued with no arguments, it results in a
COMPARATOR response indicating the currently active comparator. COMPARATOR response indicating the currently active comparator.
When issued with one or more comparator order argument, it will When issued with one or more comparator order argument, it will
change the active comparator if any comparator matches any argument. change the active comparator if any comparator matches any argument.
The COMPARATOR response will list other matching comparators if more The COMPARATOR response will list other matching comparators if more
than one matches the specified patterns. than one matches the specified patterns.
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 [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. >
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
skipping to change at page 10, line 4 skipping to change at page 10, line 4
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 December 2006
C: B125 COMPARATOR cz;* i;basic C: B125 COMPARATOR cz;* i;basic
S: * COMPARATOR i;basic 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
which matched any of the arguments to the COMPARATOR command and is which matched any of the arguments to the COMPARATOR command and is
present only if more than one match is found. present only if more than one match is found.
4.5 Formal Syntax 4.5 Formal Syntax
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 [RFCxxxx]. 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)
comparator-data = "COMPARATOR" SP comp-sel-quoted [SP "(" comparator-data = "COMPARATOR" SP comp-sel-quoted [SP "("
comp-name-quoted *(SP comp-name-quoted) ")"] comp-name-quoted *(SP comp-name-quoted) ")"]
comp-name-quoted = astring comp-name-quoted = astring
; Once any literal wrapper or quoting is removed, this ; Once any literal wrapper or quoting is removed, this
; follows the collation-name rule from [RFCxxxx] ; follows the collation-name 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 [RFCxxxx] ; 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-sel rule from [RFCxxxx] ; follows the collation-sel rule from [RFC4790]
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 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 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.
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,
http://www.iana.org/assignments/imap4-capabilities.
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
do not revoke that privilege until after authentication is complete. do not revoke that privilege until after authentication is complete.
Such implementations are particularly vulnerable to buffer overflow Such implementations are particularly vulnerable to buffer overflow
security errors at this stage and need to implement parsing of this security errors at this stage and need to implement parsing of this
command with extra care. command with extra care.
skipping to change at page 13, line 5 skipping to change at page 13, line 6
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.
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).
skipping to change at page 14, line 5 skipping to change at page 14, line 6
[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.
[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 [RFC4790] Newman, Duerst, Gulbrandsen, "Internet Application
Protocol Comparator Registry", RFC-draft-newman-i18n- Protocol Comparator Registry", RFC 4790, February 2007
comparator, September 2006
Informative References Informative References
[RFC2045] Freed, Borenstein, "Multipurpose Internet Mail Extensions [RFC2045] Freed, Borenstein, "Multipurpose Internet Mail Extensions
(MIME) Part One: Format of Internet Message Bodies", RFC (MIME) Part One: Format of Internet Message Bodies", RFC
2045, November 1996. 2045, November 1996.
[RFC2047] Moore, "MIME (Multipurpose Internet Mail Extensions) Part [RFC2047] Moore, "MIME (Multipurpose Internet Mail Extensions) Part
Three: Message Header Extensions for Non-ASCII Text", RFC Three: Message Header Extensions for Non-ASCII Text", RFC
2047, November 1996. 2047, November 1996.
skipping to change at page 15, line 5 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.
Internet-draft December 2006
[IMAP-EAI] Resnick, Newman, "IMAP Support for UTF-8", draft-ietf- [IMAP-EAI] Resnick, Newman, "IMAP Support for UTF-8", draft-ietf-
iea-imap-utf8 (work in progress), May 2006. 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
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 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
documents can be found in BCP 78 and BCP 79. documents can be found in BCP 78 and BCP 79.
skipping to change at page 16, line 33 skipping to change at page 16, line 31
at http://www.ietf.org/ipr. at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The IETF Trust (2007). This document is subject to
to the rights, licenses and restrictions contained in BCP 78, and the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 31 change blocks. 
59 lines changed or deleted 26 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/