Re: Last Call: draft-ietf-imapext-sort (INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS) to Proposed Standard

Arnt Gulbrandsen <arnt@oryx.com> Tue, 04 March 2008 11:49 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id m24BnN6s051931 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Mar 2008 04:49:23 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id m24BnN4m051930; Tue, 4 Mar 2008 04:49:23 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id m24BnKMS051920 for <ietf-imapext@imc.org>; Tue, 4 Mar 2008 04:49:22 -0700 (MST) (envelope-from arnt@oryx.com)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1]) by kalyani.oryx.com (Postfix) with ESMTP id 4CFC24AC46; Tue, 4 Mar 2008 12:49:19 +0100 (CET)
Received: from 195.30.37.9 (HELO libertango.oryx.com) by kalyani.oryx.com with esmtp id 1204631359-96135-1849; Tue, 4 Mar 2008 12:49:19 +0100
Message-Id: <HF7+giCY2vhL7PTClOc5Cg.md5@libertango.oryx.com>
Date: Tue, 04 Mar 2008 12:49:19 +0100
From: Arnt Gulbrandsen <arnt@oryx.com>
To: ietf@ietf.org, ietf-imapext@imc.org
Subject: Re: Last Call: draft-ietf-imapext-sort (INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS) to Proposed Standard
Cc: Mark Crispin <mrc@washington.edu>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
References: <1366777170.29281204132370162.JavaMail.root@dogfood.zimbra.com> <alpine.OSX.1.00.0802270935460.11461@pangtzu.panda.com> <20080304103216.GA4077@nic.fr>
In-Reply-To: <20080304103216.GA4077@nic.fr>
Content-Type: text/plain; format="flowed"
Mime-Version: 1.0
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

Stephane Bortzmeyer writes:
> On Wed, Feb 27, 2008 at 10:26:44AM -0800,
>  Mark Crispin <mrc@Washington.EDU> wrote a message of 162 lines which said:
>
>>  The actual correct collation, assuming(!) surname-first collation 
>>  and Latin character ordering(!!), is:
> ...
>>  due to where the surname is located in various cultures.
>
> Is it a good idea to sort on the ordering of the sender's culture? If 
> the ordering is to be useful for the human user, it should be 
> according the receiver's culture, no?

There's support for that. You have to read a few drafts and RFCs, though.

The draft in question defines a sort command and some sort keys, and it 
permits defining more sort keys. Other documents allow defining 
collations (sort orders) and using them im IMAP.

Sorting by From field the way most MUAs do requires defining a new 
collation and a new sort key, since this draft's "from" key uses only 
the localpart ('arnt' in the case of this message). Personally I think 
that sort key isn't at all fortunate, but it's too late to change that. 
There's decade-old running code already and the most important thing is 
to document the deployed extension.

Arnt