Display-based Address Sorting for the IMAP4 SORT Extension
draft-karp-morg-sortdisplay-00

Status of this Memo

By submitting this Internet-Draft, each author represents that any 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 aware will be disclosed, in accordance with Section 6 of BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on December 12, 2008.

Abstract

This document describes an IMAP protocol extension enabling server-side message sorting based on the commonly-displayed portion of the From header.

Table of Contents

1.  Conventions Used in This Document
2.  Introduction
3.  The DISPLAYFROM Sort Key
4.  Formal Syntax
5.  Security Considerations
6.  Internationalization Considerations
7.  IANA Considerations
8.  Normative References
§  Author's Address
§  Intellectual Property and Copyright Statements

1.  Conventions Used in This Document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).

2.  Introduction

The [SORT] (Crispin, M. and K. Murchison, “Internet Message Access Protocol - SORT and THREAD Extensions,” June 2008.) extension to the [IMAP] (Crispin, M., “INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1,” March 2003.) protocol provides a means for server-based sorting of messages. It defines a set of sort criteria and the mechanism for determining the sort value of a message for each such ordering.

The [SORT] (Crispin, M. and K. Murchison, “Internet Message Access Protocol - SORT and THREAD Extensions,” June 2008.) extension's FROM ordering sorts messages lexically on the [IMAP] (Crispin, M., “INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1,” March 2003.) addr-part of the first address in the From header. This document provides an alternate ordering, DISPLAYFROM, which sorts messages lexically based on the From address's [RFC2822] (Resnick, P., “Internet Message Format,” April 2001.) display-name, when present.

A server that supports the DISPLAYFROM sort criterion indicates this by returning "SORT=DISPLAYFROM" in its CAPABILITY response.

3.  The DISPLAYFROM Sort Key

This document introduces a new [SORT] (Crispin, M. and K. Murchison, “Internet Message Access Protocol - SORT and THREAD Extensions,” June 2008.) sort-key, DISPLAYFROM.

A message's sort value under the DISPLAYFROM ordering MUST be derived from the first [RFC2822] (Resnick, P., “Internet Message Format,” April 2001.) mailbox in its From header as follows:

• If the From header is absent or if the header contains no mailboxes, the message's sort value is the empty string.
• If the mailbox contains an [RFC2822] (Resnick, P., “Internet Message Format,” April 2001.) display-name, replace each instance of [RFC2822] (Resnick, P., “Internet Message Format,” April 2001.) CFWS in the display-name with a single space, trim all leading and trailing whitespace, and decode any [RFC2047] (Moore, K., “MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text,” November 1996.) encoded-words. If the resulting string is not the empty string, use it as the sort value for the message.
• Otherwise, completely remove all [RFC2822] (Resnick, P., “Internet Message Format,” April 2001.) CFWS from the mailbox's [RFC2822] (Resnick, P., “Internet Message Format,” April 2001.) addr-spec and use the resulting string as the message's sort value.

4.  Formal Syntax

The following syntax specification uses the Augmented Backus-Naur Form (ABNF) notation as specified in [RFC2234] (Crocker, D., Ed. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” November 1997.). [IMAP] (Crispin, M., “INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1,” March 2003.) defines the non-terminal "capability" and [SORT] (Crispin, M. and K. Murchison, “Internet Message Access Protocol - SORT and THREAD Extensions,” June 2008.) defines "sort-key".

capability    =/ "SORT=DISPLAYFROM"

sort-key      =/ "DISPLAYFROM"

5.  Security Considerations

This document defines an additional IMAP4 capability. As such, it does not change the underlying security considerations of [IMAP] (Crispin, M., “INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1,” March 2003.). The author believes that no new security issues are introduced with this additional IMAP4 capability.

6.  Internationalization Considerations

DISPLAYFROM is a string-based sort criterion. As stated in [SORT] (Crispin, M. and K. Murchison, “Internet Message Access Protocol - SORT and THREAD Extensions,” June 2008.), the collations mandated by I18NLEVEL=1 or I18NLEVEL=2 from [RFC5255] (Newman, C., Gulbrandsen, A., and A. Melnikov, “Internet Message Access Protocol Internationalization,” June 2008.) MUST be followed when sorting such strings.

The DISPLAYFROM ordering sorts on the full decoded [RFC2822] (Resnick, P., “Internet Message Format,” April 2001.) display-name, when present. It does not attempt to parse this string in a locale- or language-dependent manner in order to determine and sort on some semantically meaningful substring such as the surname.

7.  IANA Considerations

[IMAP] (Crispin, M., “INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1,” March 2003.) capabilities are registered by publishing a standards track or IESG-approved experimental RFC. This document constitutes registration of the SORT=DISPLAYFROM capability in the [IMAP] (Crispin, M., “INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1,” March 2003.) capabilities registry.

8. Normative References

Author's Address

Full Copyright Statement

Copyright © The IETF Trust (2008).

This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.