draft-ietf-imapext-sort-15.txt   draft-ietf-imapext-sort-16.txt 
IMAP Extensions Working Group M. Crispin IMAP Extensions Working Group M. Crispin
INTERNET-DRAFT: IMAP SORT K. Murchison INTERNET-DRAFT: IMAP SORT K. Murchison
Document: internet-drafts/draft-ietf-imapext-sort-15.txt April 2004 Document: internet-drafts/draft-ietf-imapext-sort-16.txt May 2004
INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at line 35 skipping to change at line 35
To view the list Internet-Draft Shadow Directories, see To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
A revised version of this document will be submitted to the RFC A revised version of this document will be submitted to the RFC
editor as an Informational Document for the Internet Community. editor as an Informational Document for the Internet Community.
A revised version of this draft document will be submitted to the RFC A revised version of this draft document will be submitted to the RFC
editor as a Proposed Standard for the Internet Community. Discussion editor as a Proposed Standard for the Internet Community. Discussion
and suggestions for improvement are requested, and should be sent to and suggestions for improvement are requested, and should be sent to
ietf-imapext@IMC.ORG. This document will expire before 7 October 2004. ietf-imapext@IMC.ORG. This document will expire before 3 November 2004.
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
Abstract Abstract
This document describes the base-level server-based sorting and This document describes the base-level server-based sorting and
threading extensions to the [IMAP] protocol. These extensions threading extensions to the [IMAP] protocol. These extensions
provide substantial performance improvements for IMAP clients which provide substantial performance improvements for IMAP clients which
offer sorted and threaded views. offer sorted and threaded views.
1. Introduction 1. Introduction
The SORT and THREAD extensions to the [IMAP] protocol provide a means The SORT and THREAD extensions to the [IMAP] protocol provide a means
of server-based sorting and threading of messages, without requiring of server-based sorting and threading of messages, without requiring
that the client download the necessary data to do so itself. This is that the client download the necessary data to do so itself. This is
particularly useful for online clients as described in [IMAP-MODELS]. particularly useful for online clients as described in [IMAP-MODELS].
A server which supports the base-level SORT extension indicates this A server which supports the base-level SORT extension indicates this
with a capability name which starts with "SORT". Future, with a capability name which starts with "SORT". Future,
upwards-compatible extensions to the SORT extension will all start upwards-compatible extensions to the SORT extension will all start
with "SORT", indicating support for this base level. with "SORT", indicating support for this base level. A server which
implements the SORT extension SHOULD also implement the COMPARATOR
extension as described in [IMAP-I18N].
A server which supports the THREAD extension indicates this with one A server which supports the THREAD extension indicates this with one
or more capability names consisting of "THREAD=" followed by a or more capability names consisting of "THREAD=" followed by a
supported threading algorithm name as described in this document. supported threading algorithm name as described in this document.
This provides for future upwards-compatible extensions. This provides for future upwards-compatible extensions.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to "SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to
skipping to change at line 722 skipping to change at line 724
considerations that are not present in the base [IMAP] protocol, and considerations that are not present in the base [IMAP] protocol, and
these issues are discussed in [IMAP]. Nevertheless, it is important these issues are discussed in [IMAP]. Nevertheless, it is important
to remember that [IMAP] protocol transactions, including message to remember that [IMAP] protocol transactions, including message
data, are sent in the clear over the network unless protection from data, are sent in the clear over the network unless protection from
snooping is negotiated, either by the use of STARTTLS, privacy snooping is negotiated, either by the use of STARTTLS, privacy
protection is negotiated in the AUTHENTICATE command, or some other protection is negotiated in the AUTHENTICATE command, or some other
protection mechanism is in effect. protection mechanism is in effect.
7. Internationalization Considerations 7. Internationalization Considerations
Strings in charsets other than US-ASCII and UTF-8 must be converted As described in [IMAP-I18N], strings in charsets other than US-ASCII
to UTF-8 prior to any comparisons. String comparisons used in SORT and UTF-8 MUST be converted to UTF-8 and compared in ascending order
and THREAD collations are performed as described in [IMAP-I18N]. according to the selected or active collation algorithm. If the server
does not support the [IMAP-I18N] COMPARATOR extension, the collation
algorithm used is the "en;ascii-casemap" collation described in
[COLLATION].
Translations of the "re" or "fw"/"fwd" tokens are not specified for Translations of the "re" or "fw"/"fwd" tokens are not specified for
removal in the base subject extraction process. An attempt to add such removal in the base subject extraction process. An attempt to add such
translated tokens would result in a geometrically complex, and translated tokens would result in a geometrically complex, and
ultimately unimplementable, task. ultimately unimplementable, task.
Instead, note that [RFC-2822] section 3.6.5 recommends that "re:" (from Instead, note that [RFC-2822] section 3.6.5 recommends that "re:" (from
the Latin "res", in the matter of) be used to identify a reply. the Latin "res", in the matter of) be used to identify a reply.
Although it is evident that, from the multiple forms of token to Although it is evident that, from the multiple forms of token to
identify a forwarded message, there is considerable variation found in identify a forwarded message, there is considerable variation found in
skipping to change at line 758 skipping to change at line 763
registers threading algorithms by publishing a standards track or IESG registers threading algorithms by publishing a standards track or IESG
approved experimental RFC. This document constitutes registration of approved experimental RFC. This document constitutes registration of
the ORDEREDSUBJECT and REFERENCES algorithms in that registry. the ORDEREDSUBJECT and REFERENCES algorithms in that registry.
Appendices Appendices
A. Normative References A. Normative References
The following documents are normative to this document: The following documents are normative to this document:
[ABNF] Crocker, D., and Overell, P. "Augmented BNF [ABNF] Crocker, D. and Overell, P. "Augmented BNF
for Syntax Specifications: ABNF", RFC 2234, for Syntax Specifications: ABNF", RFC 2234,
November 1997. November 1997.
[CHARSET] Freed, N. and J. Postel, "IANA Character Set [CHARSET] Freed, N. and J. Postel, "IANA Character Set
Registration Procedures", RFC 2978, October Registration Procedures", RFC 2978, October
2000. 2000.
[IMAP] Crispin, M., "Internet Message Access Protocol - [COMPARATOR] Newman, C. "Internet Appplication Protocol
Collation Registry", Work in Progress.
[IMAP] Crispin, M. "Internet Message Access Protocol -
Version 4rev1", RFC 3501, March 2003. Version 4rev1", RFC 3501, March 2003.
[IMAP-I18N] Newman, C. "Internet Message Access Protocol [IMAP-I18N] Newman, C. "Internet Message Access Protocol
Internationalization", Work in Progress. Internationalization", Work in Progress.
[KEYWORDS] Bradner, S. "Key words for use in RFCs to [KEYWORDS] Bradner, S. "Key words for use in RFCs to
Indicate Requirement Levels", RFC 2119, Harvard Indicate Requirement Levels", RFC 2119, Harvard
University, March 1997. University, March 1997.
[RFC-2822] Resnick, P. "Internet Message Format", RFC 2822, [RFC-2822] Resnick, P. "Internet Message Format", RFC 2822,
April 2001. April 2001.
B. Informative References B. Informative References
The following documents are informative to this document: The following documents are informative to this document:
[IMAP-MODELS] Crispin, M., "Distributed Electronic Mail Models [IMAP-MODELS] Crispin, M. "Distributed Electronic Mail Models
in IMAP4", RFC 1733, December 1994. in IMAP4", RFC 1733, December 1994.
[THREADING] Zawinski, J. "Message Threading", [THREADING] Zawinski, J. "Message Threading",
http://www.jwz.org/doc/threading.html, 1997-2002. http://www.jwz.org/doc/threading.html, 1997-2002.
Author's Address Author's Address
Mark R. Crispin Mark R. Crispin
Networks and Distributed Computing Networks and Distributed Computing
University of Washington University of Washington
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/