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 16:44 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0729028C7CE; Tue, 4 Mar 2008 08:44:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.786
X-Spam-Level:
X-Spam-Status: No, score=-0.786 tagged_above=-999 required=5 tests=[AWL=-0.349, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAoR+DdQvuQK; Tue, 4 Mar 2008 08:44:10 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF62728C6A5; Tue, 4 Mar 2008 08:43:44 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BD3E28C1B4 for <ietf@core3.amsl.com>; Tue, 4 Mar 2008 03:49:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2dTn1L7hz2X3 for <ietf@core3.amsl.com>; Tue, 4 Mar 2008 03:49:30 -0800 (PST)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by core3.amsl.com (Postfix) with ESMTP id 7EC1C28C227 for <ietf@ietf.org>; Tue, 4 Mar 2008 03:49:29 -0800 (PST)
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
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>
Mime-Version: 1.0
X-Mailman-Approved-At: Tue, 04 Mar 2008 08:43:38 -0800
Cc: Mark Crispin <mrc@washington.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
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 _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Pete Resnick
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Cyrus Daboo
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Arnt Gulbrandsen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dave Cridland
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Stephane Bortzmeyer
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Cyrus Daboo
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Arnt Gulbrandsen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin