
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 k3RJoD5Q058190; Thu, 27 Apr 2006 12:50:13 -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 k3RJoD8Y058188; Thu, 27 Apr 2006 12:50:13 -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 willow.neustar.com (willow.neustar.com [209.173.53.84]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3RJoDpF058175 for <ietf-imapext@imc.org>; Thu, 27 Apr 2006 12:50:13 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k3RJo19W021150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Apr 2006 19:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FZCUz-0003Wu-M5; Thu, 27 Apr 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-imapext@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-imapext-list-extensions-17.txt 
Message-Id: <E1FZCUz-0003Wu-M5@stiedprstage1.ietf.org>
Date: Thu, 27 Apr 2006 15:50:01 -0400
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Message Access Protocol Extension Working Group of the IETF.

	Title		: IMAP4 LIST Command Extensions
	Author(s)	: B. Leiba, A. Melnikov
	Filename	: draft-ietf-imapext-list-extensions-17.txt
	Pages		: 39
	Date		: 2006-4-27
	
IMAP4 has two commands for listing mailboxes: LIST and LSUB.  As we
have added extensions, such as Mailbox Referrals, that have required
specialized lists we have had to expand the number of list commands,
since each extension must add its function to both LIST and LSUB, and
these commands are not, as they are defined, extensible.  If we've
needed the extensions to work together, we've had to add a set of
commands to mix the different options, the set increasing in size
with each new extension.  This document describes an extension to the
base LIST command that will allow these additions to be done with
mutually compatible options to the LIST command, avoiding the
exponential increase in specialized list commands.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-imapext-list-extensions-17.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-imapext-list-extensions-17.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-imapext-list-extensions-17.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2006-4-27103028.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-imapext-list-extensions-17.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-imapext-list-extensions-17.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2006-4-27103028.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 k3LMOvZJ019627; Fri, 21 Apr 2006 15:24:57 -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 k3LMOvK2019626; Fri, 21 Apr 2006 15:24:57 -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 episteme-software.com (216-43-25-66.ip.mcleodusa.net [216.43.25.66]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3LMOuaZ019619 for <ietf-imapext@imc.org>; Fri, 21 Apr 2006 15:24:57 -0700 (MST) (envelope-from presnick@qualcomm.com)
Received: from [216.43.25.67] (127.0.0.1) by episteme-software.com with ESMTP (EIMS X 3.3d22) for <ietf-imapext@imc.org>; Fri, 21 Apr 2006 17:24:51 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p07000c24c06edb5b3daf@[216.43.25.67]>
X-Mailer: Eudora [Macintosh version 7.0a12]
Date: Fri, 21 Apr 2006 17:24:48 -0500
To: IMAP Extensions <ietf-imapext@imc.org>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Minutes
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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>

Please confirm these:

Minutes of the IETF 65 IMAPEXT meeting, 22 March 2006.

Prepared by Pete Resnick - Chair
Rob Siemborski - In room minute taker

Agenda
- LIST Extensions
- Comparators/Internationalization
- ANNOTATE and ANNOTATEMORE
- Email Address Internationalization update

Barry Lieba lead discussion on the LIST Extensions draft.

-Discussion first concerned whether servers should be able to refuse 
to return CHILDREN information even if the client requests it. The 
sense of the room was that this was reasonable and that Barry will 
rework the section on CHILDREN.
- Some discussion was had about removing some of the text on special 
cases of combinations of features. The sense of the room was that 
this was unnecessary. Barry will attempt to simplify some of the text.
- The room was generally agreed that no further working group last 
call would be needed. Barry will submit his changed document and Pete 
will write up and submit it for IESG last call.

Chris Newman lead discussion on the comparators and i18n work.

- Not much objection to the idea that the basic collation refer to a 
specific version of UCA.
- General agreement that multi-valued attributes were not necessary 
and that that section be removed. A protocol that needs multi-valued 
attributes can describe how to use them.
- General agreement that table downloading be made non-normative.
- Some discussion about ascii-casemap. Agreement that it should be 
have like i;octet and throws no errors. Agreemet to make it "i" 
instead of "en".
- Some discussion of the COMPARATOR extension (for SEARCH, etc). No 
particular changes noted to plans.
Two new drafts will be produced and working group last called.

Cyrus Daboo lead the discussion of ANNOTATE.

- Now experimental instead of standards track with a recommendation 
to implement from the working group. Cyrus will decide what to do 
about the capability.
- Discussion of removing Content-Language (leaving only attribute, 
value, and size). Sense of the room to do so.
- Discussion of folding ANNOTATEMORE into LISTEXT. Not a significant 
amount of support for it.
- Discussion of changing ANNOTATEMORE to METADATA.

Pete Resnick and Chris Newman talked about some of the issues with EAI.
- Only action is for IMAP people to keep tabs on what is going on there.

Further discussion:
- It appears that ACL2 is going to be dropped as a working group item.

End of meeting. Hope to complete before Montreal.
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



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 k3EIstrI028087; Fri, 14 Apr 2006 11:54:55 -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 k3EIstro028086; Fri, 14 Apr 2006 11:54:55 -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 mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3EIsseL028080 for <ietf-imapext@imc.org>; Fri, 14 Apr 2006 11:54:55 -0700 (MST) (envelope-from mrc@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3EIsjv0017325 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 Apr 2006 11:54:45 -0700
X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3EIsibm018319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 14 Apr 2006 11:54:45 -0700
Date: Fri, 14 Apr 2006 11:54:43 -0700 (PDT)
From: Mark Crispin <mrc@CAC.Washington.EDU>
To: Timo Sirainen <tss@iki.fi>
cc: ietf-imapext@imc.org
Subject: Re: i18n draft and search
In-Reply-To: <1145030086.10727.96.camel@hurina>
Message-ID: <Pine.OSX.4.64.0604141150110.15258@pangtzu.panda.com>
References: <1145030086.10727.96.camel@hurina>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

Regarding conflicts between RFC 3501 and the i18n document:

The i18n draft overrides/updates rules of RFC 3501.  So in any case of a 
seeming contradiction between RFC 3501 and the i18n document, the i18n 
document is the authority for all implementations that advertise support 
for the i18n document.

I'll leave it for others to answer your other points.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.



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 k3EFssUp019302; Fri, 14 Apr 2006 08:54:54 -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 k3EFssuu019301; Fri, 14 Apr 2006 08:54:54 -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 danu.procontrol.fi (kone17.procontrol.vip.fi [212.149.71.178] (may be forged)) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3EFsru6019292 for <ietf-imapext@imc.org>; Fri, 14 Apr 2006 08:54:53 -0700 (MST) (envelope-from tss@iki.fi)
Received: from hurina (82-203-177-3.dsl.gohome.fi [82.203.177.3]) by danu.procontrol.fi (Postfix) with ESMTP id 52F7B1C1D0E2 for <ietf-imapext@imc.org>; Fri, 14 Apr 2006 18:54:57 +0300 (EEST)
Subject: i18n draft and search
From: Timo Sirainen <tss@iki.fi>
To: ietf-imapext@imc.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-1Inqn36ZC6EWRadTC/gT"
Date: Fri, 14 Apr 2006 18:54:46 +0300
Message-Id: <1145030086.10727.96.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
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>

--=-1Inqn36ZC6EWRadTC/gT
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

There's this example:

        < The client requests pure octet matching, then does a search
          for potential GIF files, then switches back to its usual
          comparator. >

But RFC 3501 says:

      Server implementations MAY exclude [MIME-IMB] body parts with
      terminal content media types other than TEXT and MESSAGE from
      consideration in SEARCH matching.

Should it be required that when comparator is "i;octet", all MIME parts
MUST be searched?

What to do if SEARCH command doesn't give a CHARSET parameter but search
key contains non-ASCII? Maybe require that after COMPARATOR command the
CHARSET paramter MUST be given for all SEARCH commands? Alternative way
would be to make non-CHARSET searches always use i;octet comparator.

Stringprep contains text "Stored strings using the profile MUST NOT
contain any unassigned code points." and talks about problems with it.
Now, since emails come from other systems which may be using newer
unicode maps than the IMAP server knows, there's no way to prevent this.
What should we do when we encounter such emails while searching?

--=-1Inqn36ZC6EWRadTC/gT
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBEP8XGyUhSUUBViskRAlnlAKCHFY5sY6ZMz/0CLxImuTLHo2FXkQCfaf50
R6aGVsKdHqgB0uud5jSbkrg=
=x8eo
-----END PGP SIGNATURE-----

--=-1Inqn36ZC6EWRadTC/gT--



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 k3CFrXSB074358; Wed, 12 Apr 2006 08:53:33 -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 k3CFrXDp074357; Wed, 12 Apr 2006 08:53:33 -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 mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3CFrWqv074350 for <ietf-imapext@imc.org>; Wed, 12 Apr 2006 08:53:32 -0700 (MST) (envelope-from mrc@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3CFrTDm018347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 12 Apr 2006 08:53:30 -0700
X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3CFrM9b029607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Apr 2006 08:53:28 -0700
Date: Wed, 12 Apr 2006 08:53:20 -0700 (PDT)
From: Mark Crispin <mrc@CAC.Washington.EDU>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
In-Reply-To: <443CEB1C.8080102@isode.com>
Message-ID: <Pine.OSX.4.64.0604120852330.2906@pangtzu.panda.com>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <443C11B5.1000302@isode.com> <Pine.WNT.4.65.0604111335250.3332@Tomobiki-Cho.CAC.Washington.EDU> <443CEB1C.8080102@isode.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

On Wed, 12 Apr 2006, Alexey Melnikov wrote:
>> Define a Namespace_Response_Extension, e.g., with a first string of 
>> "DESCRIPTION".  The values in the string list can either be a single string 
>> containing a description (which in turn is affected by the LANGUAGE 
>> setting) or it can be a list of language-tagged descriptions.  Your choice.
> I don't like the latter, as this can potentially result in a very large list.

I figured that would be your reaction.

> The draft effectively defines the former, even though it is called 
> differently. I agree with the request to change TRANSLATION to something 
> else.

Sounds good to me.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.



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 k3CBvceO063843; Wed, 12 Apr 2006 04:57:38 -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 k3CBvc1T063842; Wed, 12 Apr 2006 04:57:38 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3CBvYU7063835 for <ietf-imapext@imc.org>; Wed, 12 Apr 2006 04:57:35 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.2.164] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Wed, 12 Apr 2006 12:57:22 +0100
Message-ID: <443CEB1C.8080102@isode.com>
Date: Wed, 12 Apr 2006 12:57:16 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
To: Mark Crispin <MRC@CAC.Washington.EDU>
CC: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <443C11B5.1000302@isode.com> <Pine.WNT.4.65.0604111335250.3332@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To: <Pine.WNT.4.65.0604111335250.3332@Tomobiki-Cho.CAC.Washington.EDU>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Mark Crispin wrote:

> On Tue, 11 Apr 2006, Alexey Melnikov wrote:
>
>>> then why not add that (a description), along with a provision for 
>>> the description to be in multiple languages?
>>
>> I am not sure what you are suggesting here. Can you clarify?
>
> Define a Namespace_Response_Extension, e.g., with a first string of 
> "DESCRIPTION".  The values in the string list can either be a single 
> string containing a description (which in turn is affected by the 
> LANGUAGE setting) or it can be a list of language-tagged 
> descriptions.  Your choice.

I don't like the latter, as this can potentially result in a very large list.
The draft effectively defines the former, even though it is called differently. I agree with the request to change TRANSLATION to something        else.



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 k3BNqIXg037300; Tue, 11 Apr 2006 16:52:18 -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 k3BNqIHJ037299; Tue, 11 Apr 2006 16:52:18 -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 laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BNqG1c037293 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 16:52:18 -0700 (MST) (envelope-from lisa@osafoundation.org)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id CBD20142273; Tue, 11 Apr 2006 16:52:15 -0700 (PDT)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30791-06; Tue, 11 Apr 2006 16:52:14 -0700 (PDT)
Received: from [192.168.103.124] (adsl-75-5-124-98.dsl.pltn13.sbcglobal.net [75.5.124.98]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 520EB142266; Tue, 11 Apr 2006 16:52:14 -0700 (PDT)
In-Reply-To: <p07000c3fc05fb0b31b28@[216.43.25.67]>
References: <p07000c3fc05fb0b31b28@[216.43.25.67]>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2C88BD07-F10B-4E61-980D-4B9CDA824A17@osafoundation.org>
Cc: IMAP Extensions <ietf-imapext@imc.org>
Content-Transfer-Encoding: 7bit
From: Lisa Dusseault <lisa@osafoundation.org>
Subject: Re: To Do list
Date: Tue, 11 Apr 2006 16:52:10 -0700
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.746.2)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
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>

Also new milestones for the charter :)
(sorry, that was on my todo list before Dallas but I didn't get date  
commitments from everyone)

Lisa

On Apr 10, 2006, at 12:04 AM, Pete Resnick wrote:

>
> Updates post-Dallas:
>
> 1. Pete is doing the write-up for ANNOTATE and will soon pass it on  
> to the IESG for IETF Last Call.
> 2. Waiting for a rev of LISTEXT from Barry. Then Pete will write-up  
> and pass it on to the IESG for IETF Last Call.
> 3. Waiting for a rev of COMPARATOR from Arnt. The current version  
> of IMAPi18n should be ready to go. Once we get the new draft of  
> COMPARATOR, Pete will issue a WG Last Call for both.
>
> Anything else?
>
> pr
> -- 
> Pete Resnick <http://www.qualcomm.com/~presnick/>
> QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858) 
> 651-1102
>



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 k3BMattQ033262; Tue, 11 Apr 2006 15:36:55 -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 k3BMatlW033260; Tue, 11 Apr 2006 15:36:55 -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 k3BMarBc033242 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 15:36:54 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 9F4B54AC35; Wed, 12 Apr 2006 00:36:52 +0200 (CEST)
Message-Id: <fsUEuymqzYv8L0arplUMuw.md5@libertango.oryx.com>
Date: Wed, 12 Apr 2006 00:38:15 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Mark Crispin <mrc@cac.washington.edu>, Dave Cridland <dave@cridland.net>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <9875.1144791333.165815@peirce.dave.cridland.net> <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
In-Reply-To: <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
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>

Mark Crispin writes:
> I want to make certain (wooden stake in heart, garlic in coffin, 
> cruxifix on top, etc.) that the vampire of translating protocol 
> keywords is kept firmly dead and not just undead.

Relax. Completely.

Arnt



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 k3BM7k2x032067; Tue, 11 Apr 2006 15:07:46 -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 k3BM7kai032066; Tue, 11 Apr 2006 15:07:46 -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 heisenberg.zen.co.uk (heisenberg.zen.co.uk [212.23.3.141]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BM7jpd032060 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 15:07:45 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by heisenberg.zen.co.uk with esmtp (Exim 4.30) id 1FTR1U-0007ey-Oo; Tue, 11 Apr 2006 22:07:44 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id 230CD498003; Tue, 11 Apr 2006 23:14:38 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07622-07; Tue, 11 Apr 2006 23:14:28 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id 3636D498002; Tue, 11 Apr 2006 23:14:26 +0100 (BST)
Date: Tue, 11 Apr 2006 23:07:32 +0100
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <9875.1144791333.165815@peirce.dave.cridland.net> <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
In-Reply-To: <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
MIME-Version: 1.0
Message-Id: <9875.1144793252.496397@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Mark Crispin <mrc@CAC.Washington.EDU>
Cc: <ietf-imapext@imc.org>, Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Heisenberg-IP: [217.155.137.60]
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>

On Tue Apr 11 23:00:42 2006, Mark Crispin wrote:
> On Tue, 11 Apr 2006, Dave Cridland wrote:
>>> If the intention is to have a human-readable namespace 
>>> description extension, then why not add that (a description), 
>>> along with a provision for the description to be in multiple 
>>> languages?
>> I like it, but I think that's essentially what it provides - a 
>> client simply has to issue a LANGUAGE command at some point prior 
>> to NAMESPACE. "Translating" the namespace from "#news" to "Usenet 
>> groups" for language "en" seems sensible. The text ought to be 
>> changed to reflect this (more sensible) usage, though.
> 
> I have a semantic, although probably not technical, objection.
> 
> 
Yes, I agree - to make this clear, the protocol keywords need to be 
changed to reflect the changed semantics.

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k3BM0kkC031857; Tue, 11 Apr 2006 15:00:46 -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 k3BM0kBU031856; Tue, 11 Apr 2006 15:00:46 -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 mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BM0jNf031850 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 15:00:45 -0700 (MST) (envelope-from mrc@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3BM0h0r002094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Apr 2006 15:00:43 -0700
X-Auth-Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.37.173]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3BM0gO0017584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Apr 2006 15:00:42 -0700
Date: Tue, 11 Apr 2006 15:00:42 -0700 (PDT)
From: Mark Crispin <mrc@CAC.Washington.EDU>
To: Dave Cridland <dave@cridland.net>
cc: ietf-imapext@imc.org, Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
In-Reply-To: <9875.1144791333.165815@peirce.dave.cridland.net>
Message-ID: <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <9875.1144791333.165815@peirce.dave.cridland.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

On Tue, 11 Apr 2006, Dave Cridland wrote:
>> If the intention is to have a human-readable namespace description 
>> extension, then why not add that (a description), along with a provision 
>> for the description to be in multiple languages?
> I like it, but I think that's essentially what it provides - a client simply 
> has to issue a LANGUAGE command at some point prior to NAMESPACE. 
> "Translating" the namespace from "#news" to "Usenet groups" for language "en" 
> seems sensible. The text ought to be changed to reflect this (more sensible) 
> usage, though.

I have a semantic, although probably not technical, objection.

We're not "translating" the namespace from "#news." to "Usenet Groups" 
for language "en".

We are describing the namespace "#news." as being "Usenet Groups" in 
language "en"; and there are descriptions available in other languages. 
In no instance is "#news." translated; in all cases that is the name of 
the namespace.

I want to make certain (wooden stake in heart, garlic in coffin, 
cruxifix on top, etc.) that the vampire of translating protocol keywords 
is kept firmly dead and not just undead.  [Remember French-translated 
BASIC?  *Shudder*]

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



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 k3BLZq70030659; Tue, 11 Apr 2006 14:35:52 -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 k3BLZqfE030658; Tue, 11 Apr 2006 14:35:52 -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 heisenberg.zen.co.uk (heisenberg.zen.co.uk [212.23.3.141]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BLZpC4030649 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 14:35:52 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by heisenberg.zen.co.uk with esmtp (Exim 4.30) id 1FTQWX-0001eE-Pj; Tue, 11 Apr 2006 21:35:45 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id E7552498003; Tue, 11 Apr 2006 22:42:38 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07570-08; Tue, 11 Apr 2006 22:42:28 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id A2771498002; Tue, 11 Apr 2006 22:42:26 +0100 (BST)
Date: Tue, 11 Apr 2006 22:35:32 +0100
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To:  <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
MIME-Version: 1.0
Message-Id: <9875.1144791333.165815@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Mark Crispin <MRC@cac.washington.edu>
Cc: <ietf-imapext@imc.org>, Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Heisenberg-IP: [217.155.137.60]
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>

On Tue Apr 11 21:28:03 2006, Mark Crispin wrote:
> 
> On Tue, 11 Apr 2006, Alexey Melnikov wrote:
>> To clarify: the LANGUAGE command doesn't localize namespaces. It 
>> adds a new parameter to the NAMESPACE response that contains a 
>> translated version of the namespace, which can only be used in UI.
> 
> Why is this needed, given that NAMESPACE itself already identifies 
> namespaces by personal, other user, and shared/multi-user?
> 
> If the intention is to have a human-readable namespace description 
> extension, then why not add that (a description), along with a 
> provision for the description to be in multiple languages?

I like it, but I think that's essentially what it provides - a client 
simply has to issue a LANGUAGE command at some point prior to 
NAMESPACE. "Translating" the namespace from "#news" to "Usenet 
groups" for language "en" seems sensible. The text ought to be 
changed to reflect this (more sensible) usage, though.

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k3BKe4m8028443; Tue, 11 Apr 2006 13:40:04 -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 k3BKe4H4028442; Tue, 11 Apr 2006 13:40:04 -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 mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKe3jO028434 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:40:04 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3BKe3iJ028909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Apr 2006 13:40:03 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3BKe2pq025468 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 11 Apr 2006 13:40:02 -0700
Date: Tue, 11 Apr 2006 13:40:01 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
In-Reply-To: <443C11B5.1000302@isode.com>
Message-ID: <Pine.WNT.4.65.0604111335250.3332@Tomobiki-Cho.CAC.Washington.EDU>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <443C11B5.1000302@isode.com>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

On Tue, 11 Apr 2006, Alexey Melnikov wrote:
>> then why not add that (a description), along with a provision for the 
>> description to be in multiple languages?
> I am not sure what you are suggesting here. Can you clarify?

Define a Namespace_Response_Extension, e.g., with a first string of 
"DESCRIPTION".  The values in the string list can either be a single 
string containing a description (which in turn is affected by the LANGUAGE 
setting) or it can be a list of language-tagged descriptions.  Your 
choice.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



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 k3BKbOTH028352; Tue, 11 Apr 2006 13:37:24 -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 k3BKbOBl028351; Tue, 11 Apr 2006 13:37:24 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKbN3B028345 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:37:23 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 21:37:16 +0100
Message-ID: <443C1370.5000406@isode.com>
Date: Tue, 11 Apr 2006 21:37:04 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-imapext@imc.org
Subject: Re: Comments about draft-ietf-imapext-i18n-06.txt
References: <p07000c3fc05fb0b31b28@[216.43.25.67]> <443A5391.3090109@isode.com> <21242.1144674997.982052@peirce.dave.cridland.net>
In-Reply-To: <21242.1144674997.982052@peirce.dave.cridland.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Mark has suggested to split COMPARATOR from the rest of IMAP I18N. I 
kind of like the idea, considering that the latter might still be 
changing (or need more text). Can we get a general agreement if the 
split is a good thing and if it is, who is going to edit different 
pieces (presumably Arnt will co-edit one or both, but who else)?



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 k3BKToke028010; Tue, 11 Apr 2006 13:29:50 -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 k3BKToQr028009; Tue, 11 Apr 2006 13:29:50 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKTnIn028003 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:29:49 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 21:29:41 +0100
Message-ID: <443C11B5.1000302@isode.com>
Date: Tue, 11 Apr 2006 21:29:41 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mark Crispin <MRC@CAC.Washington.EDU>
CC: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To: <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Mark Crispin wrote:

> On Tue, 11 Apr 2006, Alexey Melnikov wrote:
>
>> To clarify: the LANGUAGE command doesn't localize namespaces. It adds 
>> a new parameter to the NAMESPACE response that contains a translated 
>> version of the namespace, which can only be used in UI.
>
> Why is this needed, given that NAMESPACE itself already identifies 
> namespaces by personal, other user, and shared/multi-user?
>
> If the intention is to have a human-readable namespace description 
> extension,

Yes.

> then why not add that (a description), along with a provision for the 
> description to be in multiple languages?

I am not sure what you are suggesting here. Can you clarify?



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 k3BKS62p027940; Tue, 11 Apr 2006 13:28:06 -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 k3BKS626027939; Tue, 11 Apr 2006 13:28:06 -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 mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKS57X027933 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:28:06 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3BKS5uD017068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Apr 2006 13:28:05 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3BKS4Gt021864 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 11 Apr 2006 13:28:04 -0700
Date: Tue, 11 Apr 2006 13:28:03 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
In-Reply-To: <443C0BCA.1000308@isode.com>
Message-ID: <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

On Tue, 11 Apr 2006, Alexey Melnikov wrote:
> To clarify: the LANGUAGE command doesn't localize namespaces. It adds a new 
> parameter to the NAMESPACE response that contains a translated version of the 
> namespace, which can only be used in UI.

Why is this needed, given that NAMESPACE itself already identifies 
namespaces by personal, other user, and shared/multi-user?

If the intention is to have a human-readable namespace description 
extension, then why not add that (a description), along with a provision 
for the description to be in multiple languages?

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



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 k3BKBA9u026873; Tue, 11 Apr 2006 13:11:10 -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 k3BKBAns026872; Tue, 11 Apr 2006 13:11:10 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKB9Af026862 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:11:10 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 21:11:04 +0100
Message-ID: <443C0D56.7080501@isode.com>
Date: Tue, 11 Apr 2006 21:11:02 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
CC: ietf-imapext@imc.org
Subject: Re: Comments about draft-ietf-imapext-i18n-06.txt
References: <p07000c3fc05fb0b31b28@[216.43.25.67]> <443A5391.3090109@isode.com> <21242.1144674997.982052@peirce.dave.cridland.net>
In-Reply-To: <21242.1144674997.982052@peirce.dave.cridland.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Dave Cridland wrote:

> 2) [Decouple NAMESPACE and LANGUAGE] - Consensus seemed to be in support.

Just to confirm: draft-ietf-imapext-i18n-xx.txt will still describe the 
TRANSLATION extension to the NAMESPACE response. If the server supports 
both the NAMESPACE extension and the LANGUAGE extension, it SHOULD 
return the NAMESPACE responses containing the TRANSLATION field.
However the requirement for the server to send the NAMESPACE response on 
LANGUAGE command is removed.

Alexey



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 k3BK4aBa026521; Tue, 11 Apr 2006 13:04:36 -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 k3BK4a5V026520; Tue, 11 Apr 2006 13:04:36 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BK4ZNY026514 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:04:35 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 21:04:26 +0100
Message-ID: <443C0BCA.1000308@isode.com>
Date: Tue, 11 Apr 2006 21:04:26 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Mark Crispin <mrc@CAC.Washington.EDU>
CC: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com>
In-Reply-To: <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Mark Crispin wrote:

>> 2) Section 3.4:
>> What's paragraph 1 for?
>
> Agreed.  This dependency is not good.
>
> IMHO, the LANGUAGE command should NOT localize namespaces.

To clarify: the LANGUAGE command doesn't localize namespaces. It adds a 
new parameter to the NAMESPACE response that contains a translated 
version of the namespace, which can only be used in UI.

> Instead, if such as desired, the NAMESPACE command itself should be 
> extended to take an argument.  I can see cases in which a user may 
> want error messages in his preferred language but retain mailbox paths 
> in i-default.
>
> This doesn't add an additional RTT since the client has to do a 
> NAMESPACE command anyway if it purposes to use namespaces.




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 k3BEjhv8013403; Tue, 11 Apr 2006 07:45:43 -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 k3BEjhOh013402; Tue, 11 Apr 2006 07:45:43 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BEjctX013395 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 07:45:39 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 15:45:29 +0100
Message-ID: <443BC107.4060108@isode.com>
Date: Tue, 11 Apr 2006 15:45:27 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Cyrus Daboo <cyrus@daboo.name>
CC: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com> <71CD159CA68C102AE848B539@Cyrus-Daboo.local> <443A608C.9040204@isode.com> <67248422E8EA862DC9A68052@Cyrus-Daboo.local>
In-Reply-To: <67248422E8EA862DC9A68052@Cyrus-Daboo.local>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Cyrus Daboo wrote:

> Hi Alexey,
>
> I think we are missing something here:
>
> In Section 3 under the description of 'SUBSCRIBED' you state for the 
> LSUB command:
>
>      the \NoSelect attribute has a special meaning (it indicates that
>      this mailbox is not, itself, subscribed, but that it has
>      descendant mailboxes that are)* *
>
> Actually \NoSelect has two meanings here.

You are right. I've changed the text quoted above to say "... has a 
second special meaning ...".

> It can be the 'special' one described above (and called out in 3501) 
> as well as its usual meaning of referring to an unselectable mailbox - 
> only in this case one that is subscribed. As far as I can tell, there 
> is nothing in IMAP that prevents a \NoSelect mailbox (a 'directory') 
> from being subscribed to - so in theory it is possible to have a 
> \NoSelect subscribed mailbox that exists. So the following could happen:
>
> a LIST (SUBSCRIBED) "" "%"
> * LIST (\NoSelect \HasChildren) "/" "foo"
> a OK
>
> and that is different than:
>
> a LIST (SUBSCRIBED) "" "%"
> * LIST (\NonExistent \HasChildren) "/" "foo"
> a OK
>
> i.e. it MUST be possible to get back \NoSelect in a LIST (SUBSCRIBED).

Right.
Do we need to add this example to the document?

> So the key thing is this: with the original LSUB command the \NoSelect 
> flag had two possible meanings. With the extended LIST (SUBSCRIBED) 
> command \NoSelect retains its meaning from the LIST command, and the 
> new \NonExistant attribute is used to indicate second 'special' case 
> that LSUB allows.

That is correct.

Here is what I've added to the document:

In section 3.3 CHILDINFO extended data item:

        Note: Some servers allow for mailboxes to exist without requiring
        their parent to exist. For example, a mailbox "Customers/ABC" 
can exist
        while the mailbox "Customers" does not. As CHILDINFO extended data
        item is not allowed if the RECURSIVEMATCH selection option is 
not specified,
        such servers SHOULD use the "\NonExistent \HasChildren" 
attribute pair to signal
        to the client that there is a descendant mailbox that matches 
the selection
        criteria. See example 11 in Section 5.

And example 11 in Section 5:

        The following example shows how a server that supports missing
        mailbox hierarchy elements can signal to a client that didn't
        specify the RECURSIVEMATH selection option that there is
        a child mailbox that matches the selection criteria.

   C: a1 LIST (REMOTE) "" *
   S: * LIST () "/" music/rock
   S: * LIST (\Remote) "/" also/jazz
   S: a1 OK done

   C: a2 LIST () "" %
   S: * LIST (\NonExistent \HasChildren) "/" music
   S: a2 OK done

   C: a3 LIST (REMOTE) "" %
   S: * LIST (\NonExistent \HasChildren) "/" music
   S: * LIST (\NonExistent \HasChildren) "/" also
   S: a3 OK done

Comments?



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 k3AEs4qO052283; Mon, 10 Apr 2006 07:54:04 -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 k3AEs4MN052282; Mon, 10 Apr 2006 07:54:04 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3AEs43f052275 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 07:54:04 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 52C09D472D4; Mon, 10 Apr 2006 10:54:03 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 10:53:45 -0400
X-Sasl-enc: JvGT2/ICA/gMH+VoGo4KIiDsdjbSQwVecqD2lT3vvuyk 1144680825
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id EDBF13B0E; Mon, 10 Apr 2006 10:53:44 -0400 (EDT)
Date: Mon, 10 Apr 2006 10:54:43 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: Philip's issue with LIST-EXTENDED
Message-ID: <67248422E8EA862DC9A68052@Cyrus-Daboo.local>
In-Reply-To: <443A608C.9040204@isode.com>
References: <44393A10.1010006@isode.com> <71CD159CA68C102AE848B539@Cyrus-Daboo.local> <443A608C.9040204@isode.com>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi Alexey,

I think we are missing something here:

In Section 3 under the description of 'SUBSCRIBED' you state for the LSUB 
command:

      the \NoSelect attribute has a special meaning (it indicates that
      this mailbox is not, itself, subscribed, but that it has
      descendant mailboxes that are)

Actually \NoSelect has two meanings here. It can be the 'special' one 
described above (and called out in 3501) as well as its usual meaning of 
referring to an unselectable mailbox - only in this case one that is 
subscribed. As far as I can tell, there is nothing in IMAP that prevents a 
\NoSelect mailbox (a 'directory') from being subscribed to - so in theory 
it is possible to have a \NoSelect subscribed mailbox that exists. So the 
following could happen:

a LIST (SUBSCRIBED) "" "%"
* LIST (\NoSelect \HasChildren) "/" "foo"
a OK

and that is different than:

a LIST (SUBSCRIBED) "" "%"
* LIST (\NonExistent \HasChildren) "/" "foo"
a OK

i.e. it MUST be possible to get back \NoSelect in a LIST (SUBSCRIBED).

So the key thing is this: with the original LSUB command the \NoSelect flag 
had two possible meanings. With the extended LIST (SUBSCRIBED) command 
\NoSelect retains its meaning from the LIST command, and the new 
\NonExistant attribute is used to indicate second 'special' case that LSUB 
allows.

-- 
Cyrus Daboo



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 k3AEO10Z050163; Mon, 10 Apr 2006 07:24:01 -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 k3AEO1CP050162; Mon, 10 Apr 2006 07:24:01 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3AEO0LK050155 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 07:24:00 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 3E9E3D47570 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 10:23:59 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 10:23:41 -0400
X-Sasl-enc: UHFD3opP6sQ8rLrtflqKvv4JBQe4FcZCRZrr04HHuzjA 1144679020
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id 3C5363AD2 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 10:23:39 -0400 (EDT)
Date: Mon, 10 Apr 2006 10:24:40 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: IMAP Extensions <ietf-imapext@imc.org>
Subject: Re: To Do list
Message-ID: <10832BD2661EE838E2780A3A@Cyrus-Daboo.local>
In-Reply-To: <277F687E43102F02B0DED4B6@Cyrus-Daboo.local>
References:  <p07000c3fc05fb0b31b28@[216.43.25.67]> <277F687E43102F02B0DED4B6@Cyrus-Daboo.local>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi,

--On April 10, 2006 10:10:00 AM -0400 Cyrus Daboo <cyrus@daboo.name> wrote:

> 2) Typo 'encourated' -> 'encourage'.

Sorry - that should have been a change to 'encouraged'.

-- 
Cyrus Daboo



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 k3AE9MnD049306; Mon, 10 Apr 2006 07:09:22 -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 k3AE9MmU049305; Mon, 10 Apr 2006 07:09:22 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3AE9MFw049299 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 07:09:22 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 322D5D47060; Mon, 10 Apr 2006 10:09:21 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 10:09:03 -0400
X-Sasl-enc: Y8x1h6WtEtvAl7ndTEUtnHCWMRqAvmToTDrTCn+AU6bq 1144678142
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id 927A939B2; Mon, 10 Apr 2006 10:09:01 -0400 (EDT)
Date: Mon, 10 Apr 2006 10:10:00 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Pete Resnick <presnick@qualcomm.com>, IMAP Extensions <ietf-imapext@imc.org>
Subject: Re: To Do list
Message-ID: <277F687E43102F02B0DED4B6@Cyrus-Daboo.local>
In-Reply-To: <p07000c3fc05fb0b31b28@[216.43.25.67]>
References:  <p07000c3fc05fb0b31b28@[216.43.25.67]>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi Pete,

--On April 10, 2006 2:04:51 AM -0500 Pete Resnick <presnick@qualcomm.com> 
wrote:

> 3. Waiting for a rev of COMPARATOR from Arnt. The current version of
> IMAPi18n should be ready to go. Once we get the new draft of COMPARATOR,
> Pete will issue a WG Last Call for both.

Some comments on i18n draft:

1) Change 'ANNOTATEMORE' to 'METADATA' in text and update reference title.

2) Typo 'encourated' -> 'encourage'.

3) Language formal syntax element 'language-data' is not referenced. I 
think you need to add the following to fix that:

       response-payload  =/ language-data

4) In the language formal syntax, put the comment for 'resp-text' after the 
element not before it.

5) In the language formal syntax the comment for 'lang-tag-quoted' is not 
wrapped properly.

6) Comparator formal syntax element 'comparator-data' is not referenced. I 
think you need to add the following to fix that:

       response-payload  =/ comparator-data

7) In the comparator formal syntax there are some comments of the form: 
'this follows the xxx rule' - I'm not sure where each of the 'xxx' items 
come from - a reference should be added.

-- 
Cyrus Daboo



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 k3ADhQZj048360; Mon, 10 Apr 2006 06:43:26 -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 k3ADhQvY048359; Mon, 10 Apr 2006 06:43:26 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADhPg8048343 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:43:25 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 14:43:06 +0100
Message-ID: <443A60DF.9050804@isode.com>
Date: Mon, 10 Apr 2006 14:42:55 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cyrus Daboo <cyrus@daboo.name>
CC: Pete Resnick <presnick@qualcomm.com>, IMAP Extensions <ietf-imapext@imc.org>
Subject: Re: To Do list
References: <p07000c3fc05fb0b31b28@[216.43.25.67]> <A8DAD1A0C3FAFCDC4684FA74@Cyrus-Daboo.local>
In-Reply-To: <A8DAD1A0C3FAFCDC4684FA74@Cyrus-Daboo.local>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Cyrus Daboo wrote:

>> 1. Pete is doing the write-up for ANNOTATE and will soon pass it on to
>> the IESG for IETF Last Call.
>> 2. Waiting for a rev of LISTEXT from Barry. Then Pete will write-up and
>> pass it on to the IESG for IETF Last Call.
>> 3. Waiting for a rev of COMPARATOR from Arnt. The current version of
>> IMAPi18n should be ready to go. Once we get the new draft of COMPARATOR,
>> Pete will issue a WG Last Call for both.
>>
>> Anything else?
>
> WG should review ANNOTATEMORE (aka METADATA).

Right. I would have no problems Last Calling it (officially or 
unofficially) in IMAPEXT and/or LEMONADE WGs.




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 k3ADfsb2048251; Mon, 10 Apr 2006 06:41:54 -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 k3ADfsKJ048250; Mon, 10 Apr 2006 06:41:54 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADfr6b048231 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:41:53 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 14:41:43 +0100
Message-ID: <443A608C.9040204@isode.com>
Date: Mon, 10 Apr 2006 14:41:32 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Cyrus Daboo <cyrus@daboo.name>
CC: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com> <71CD159CA68C102AE848B539@Cyrus-Daboo.local>
In-Reply-To: <71CD159CA68C102AE848B539@Cyrus-Daboo.local>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Cyrus Daboo wrote:

> Hi Alexey,
>
> --On April 9, 2006 5:45:04 PM +0100 Alexey Melnikov 
> <alexey.melnikov@isode.com> wrote:
>
>> However, if the client issues <LIST () "" %>, the server can't return
>> \NoSelect, as it was replaced by CHILDINFO. And the CHILDINFO extended
>> data can't be returned as per prohibition in section 3.1 (in -16), under
>> point 2 B):
>>            Note that the CHILDINFO
>>            extended data item can only be returned when the
>>            RECURSIVEMATCH selection option is specified.
>
> Where does it say that \NoSelect has been replaced?

I think I wasn't precise enough: it was only replaced for the case when 
SUBSCRIBED is specified:

>3.3  CHILDINFO extended data item
[...]
>   The LSUB command indicates this condition by using the "\NoSelect"
>   attribute, but the LIST (SUBSCRIBED) command MUST NOT do that, since
>   "\NoSelect" retains its original meaning here.  Further, the
>   CHILDINFO extended data item is more general, in that it can be used
>   with any extended set of selection criteria.

> I could not find any explicit statement to that effect. Given that 
> \NoSelect is one of the original LIST flags I would have thought it is 
> always returned.

Right. But \NonExistent has a stronger meaning, so it would be better in 
the described case.



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 k3ADaUbg048053; Mon, 10 Apr 2006 06:36:30 -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 k3ADaU1G048052; Mon, 10 Apr 2006 06:36:30 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADaTcN048046 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:36:30 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 0F2E8D478BF; Mon, 10 Apr 2006 09:36:29 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 09:36:10 -0400
X-Sasl-enc: 33nMzRfDifRtAmRwEj9sjPAQUnj75OcZ5UZxNuET2OzK 1144676170
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id 4B79838ED; Mon, 10 Apr 2006 09:36:08 -0400 (EDT)
Date: Mon, 10 Apr 2006 09:37:09 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Alexey Melnikov <alexey.melnikov@isode.com>, IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: Philip's issue with LIST-EXTENDED
Message-ID: <71CD159CA68C102AE848B539@Cyrus-Daboo.local>
In-Reply-To: <44393A10.1010006@isode.com>
References:  <44393A10.1010006@isode.com>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi Alexey,

--On April 9, 2006 5:45:04 PM +0100 Alexey Melnikov 
<alexey.melnikov@isode.com> wrote:

> However, if the client issues <LIST () "" %>, the server can't return
> \NoSelect, as it was replaced by CHILDINFO. And the CHILDINFO extended
> data can't be returned as per prohibition in section 3.1 (in -16), under
> point 2 B):
>            Note that the CHILDINFO
>            extended data item can only be returned when the
>            RECURSIVEMATCH selection option is specified.

Where does it say that \NoSelect has been replaced? I could not find any 
explicit statement to that effect. Given that \NoSelect is one of the 
original LIST flags I would have thought it is always returned.

-- 
Cyrus Daboo



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 k3ADOKAq047371; Mon, 10 Apr 2006 06:24:20 -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 k3ADOKZ1047370; Mon, 10 Apr 2006 06:24:20 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADOJFZ047364 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:24:19 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id CC68AD47533; Mon, 10 Apr 2006 09:24:17 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 09:23:59 -0400
X-Sasl-enc: 3b/J4uyQvRdeIOBNTNePjJw0AJL8Y8PZlwsvsVsNYG/9 1144675439
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id 32E3F37FD; Mon, 10 Apr 2006 09:23:57 -0400 (EDT)
Date: Mon, 10 Apr 2006 09:24:57 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Pete Resnick <presnick@qualcomm.com>, IMAP Extensions <ietf-imapext@imc.org>
Subject: Re: To Do list
Message-ID: <A8DAD1A0C3FAFCDC4684FA74@Cyrus-Daboo.local>
In-Reply-To: <p07000c3fc05fb0b31b28@[216.43.25.67]>
References:  <p07000c3fc05fb0b31b28@[216.43.25.67]>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi Pete,

--On April 10, 2006 2:04:51 AM -0500 Pete Resnick <presnick@qualcomm.com> 
wrote:

> 1. Pete is doing the write-up for ANNOTATE and will soon pass it on to
> the IESG for IETF Last Call.
> 2. Waiting for a rev of LISTEXT from Barry. Then Pete will write-up and
> pass it on to the IESG for IETF Last Call.
> 3. Waiting for a rev of COMPARATOR from Arnt. The current version of
> IMAPi18n should be ready to go. Once we get the new draft of COMPARATOR,
> Pete will issue a WG Last Call for both.
>
> Anything else?

WG should review ANNOTATEMORE (aka METADATA).

-- 
Cyrus Daboo



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 k3ADGpiJ046815; Mon, 10 Apr 2006 06:16:51 -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 k3ADGpHH046814; Mon, 10 Apr 2006 06:16:51 -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 rutherford.zen.co.uk (rutherford.zen.co.uk [212.23.3.142]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADGofR046808 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:16:51 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1FSwG9-0002TI-JR; Mon, 10 Apr 2006 13:16:49 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id E0F29498003; Mon, 10 Apr 2006 14:23:28 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31995-02; Mon, 10 Apr 2006 14:23:19 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id AC7D5498002; Mon, 10 Apr 2006 14:23:17 +0100 (BST)
Date: Mon, 10 Apr 2006 14:16:37 +0100
Subject: Re: Comments about draft-ietf-imapext-i18n-06.txt
References: <p07000c3fc05fb0b31b28@[216.43.25.67]> <443A5391.3090109@isode.com>
In-Reply-To: <443A5391.3090109@isode.com>
MIME-Version: 1.0
Message-Id: <21242.1144674997.982052@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: <ietf-imapext@imc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Rutherford-IP: [217.155.137.60]
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>

On Mon Apr 10 13:46:09 2006, Alexey Melnikov wrote:
> 3). Also check the list of other issues brought up by Dave Cridland:
> <http://www.imc.org/ietf-imapext/mail-archive/msg03258.html>

(Numbers referring to points in my email)

1) [Allow LANGUAGE to have a list of languages in preference order as 
parameters] - Consensus in support.

2) [Decouple NAMESPACE and LANGUAGE] - Consensus seemed to be in 
support.

3) Resolution depends on comparator draft.

4) [Better comparator support] Unresolved.

I'm actually not hugely fussed on this. A proper solution to this 
requires a lot more work than this document could reasonably provide.

To put it another way, IMAP's SEARCH is sufficiently good that 
providing sufficiently better comparator support to make the effort 
worthwhile requires much more radical change.

5) [Unicode in identifiers] Resolved by Alexey's text

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k3ACxeed045450; Mon, 10 Apr 2006 05:59:40 -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 k3ACxebn045449; Mon, 10 Apr 2006 05:59:40 -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 pythagoras.zen.co.uk (pythagoras.zen.co.uk [212.23.3.140]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ACxd6d045435 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 05:59:39 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by pythagoras.zen.co.uk with esmtp (Exim 4.30) id 1FSvzV-0001T1-6g; Mon, 10 Apr 2006 12:59:37 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id 9ADE2498003; Mon, 10 Apr 2006 14:06:16 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31821-07; Mon, 10 Apr 2006 14:06:12 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id 133A7498002; Mon, 10 Apr 2006 14:06:11 +0100 (BST)
Date: Mon, 10 Apr 2006 13:59:31 +0100
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com> <2ggGuv29sIJ1KJSYbq168A.md5@libertango.oryx.com> <443A53B6.40702@isode.com>
In-Reply-To: <443A53B6.40702@isode.com>
MIME-Version: 1.0
Message-Id: <21242.1144673971.475359@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: <ietf-imapext@imc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Pythagoras-IP: [217.155.137.60]
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>

On Mon Apr 10 13:46:46 2006, Alexey Melnikov wrote:
> 
> Arnt Gulbrandsen wrote:
> 
>> Alexey Melnikov writes:
>> 
>>> So, my question is what do we do with this? The options I see are:
>>> 1). punt, let server and client implementors figure this out.
>>> 2). add the example and document the workaround as a proper way 
>>> to respond in this case
>>> 3). allow CHILDINFO to be returned on extended LISTs with no 
>>> RECURSIVEMATCH.
>>> 
>>> I personally don't like the option 1), as this issue is too 
>>> subtle. I prefer option 2 over 3.
>> 
>> By 2 you mean '* LIST (\nonexistent \haschildren) "/" "foo"'? Then 
>> I agree.
> 
> Yes.
> 
> 
It applies to <LIST (REMOTE) "" %> too. Basically to any combination 
of selection options where adding RECURSIVEMATCH would be illegal.

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k3AClGKL044984; Mon, 10 Apr 2006 05:47:16 -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 k3AClGRP044983; Mon, 10 Apr 2006 05:47:16 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3AClFs8044977 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 05:47:15 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 13:46:51 +0100
Message-ID: <443A53B6.40702@isode.com>
Date: Mon, 10 Apr 2006 13:46:46 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: ietf-imapext@imc.org
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com> <2ggGuv29sIJ1KJSYbq168A.md5@libertango.oryx.com>
In-Reply-To: <2ggGuv29sIJ1KJSYbq168A.md5@libertango.oryx.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Arnt Gulbrandsen wrote:

> Alexey Melnikov writes:
>
>> So, my question is what do we do with this? The options I see are:
>> 1). punt, let server and client implementors figure this out.
>> 2). add the example and document the workaround as a proper way to 
>> respond in this case
>> 3). allow CHILDINFO to be returned on extended LISTs with no 
>> RECURSIVEMATCH.
>>
>> I personally don't like the option 1), as this issue is too subtle. I 
>> prefer option 2 over 3.
>
> By 2 you mean '* LIST (\nonexistent \haschildren) "/" "foo"'? Then I 
> agree.

Yes.



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 k3ACkITD044970; Mon, 10 Apr 2006 05:46:18 -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 k3ACkI01044969; Mon, 10 Apr 2006 05:46:18 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ACkHaB044963 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 05:46:18 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 13:46:13 +0100
Message-ID: <443A5391.3090109@isode.com>
Date: Mon, 10 Apr 2006 13:46:09 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IMAP Extensions <ietf-imapext@imc.org>
Subject: Comments about draft-ietf-imapext-i18n-06.txt
References: <p07000c3fc05fb0b31b28@[216.43.25.67]>
In-Reply-To: <p07000c3fc05fb0b31b28@[216.43.25.67]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Pete Resnick wrote:

> 3. Waiting for a rev of COMPARATOR from Arnt. The current version of 
> IMAPi18n should be ready to go.

Not quite yet, a new revision is needed to address the following issues 
in -06:

1). Section 5.1 (Unicode Userids and Passwords) says:

>   When AUTHENTICATE is used, some servers may support userids and
>   passwords in Unicode [13]. However, such userids cannot be used as
>   email addresses,

Delete the rest of the paragraph. ACL RFC 4314 says that all usernames are in UTF-8.

> and at present also seem to be incompatible with
>   the current latest ACL drafts. Unless the ACL drafts resolve this,
>   server authors are cautioned against supporting ACL and unicode
>   userids simultaneously.

2). Did the WG reach any conclusion on adding a new SEARCH keyword for 
comparators?

3). Also check the list of other issues brought up by Dave Cridland:
<http://www.imc.org/ietf-imapext/mail-archive/msg03258.html>



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 k3ACaGFS044695; Mon, 10 Apr 2006 05:36:16 -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 k3ACaG10044694; Mon, 10 Apr 2006 05:36:16 -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 k3ACaC3o044686 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 05:36:15 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id B3CCA4AC32 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 14:36:11 +0200 (CEST)
Message-Id: <2ggGuv29sIJ1KJSYbq168A.md5@libertango.oryx.com>
Date: Mon, 10 Apr 2006 14:37:27 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-imapext@imc.org
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com>
In-Reply-To: <44393A10.1010006@isode.com>
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>

Alexey Melnikov writes:
> So, my question is what do we do with this? The options I see are:
> 1). punt, let server and client implementors figure this out.
> 2). add the example and document the workaround as a proper way to 
> respond in this case
> 3). allow CHILDINFO to be returned on extended LISTs with no RECURSIVEMATCH.
>
> I personally don't like the option 1), as this issue is too subtle. I 
> prefer option 2 over 3.

By 2 you mean '* LIST (\nonexistent \haschildren) "/" "foo"'? Then I agree.

Arnt



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 k3ABEps0042398; Mon, 10 Apr 2006 04:14:51 -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 k3ABEphC042397; Mon, 10 Apr 2006 04:14:51 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ABEmGM042382 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 04:14:49 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 12:14:38 +0100
Message-ID: <44393A10.1010006@isode.com>
Date: Sun, 09 Apr 2006 17:45:04 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Philip's issue with LIST-EXTENDED
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Hi everyone,
After staring for 10 minutes at the jabber log and LISTEXT draft I 
finally understood what Philip was talking about.

Here is the issue:

Imagine that the server supports missing hierarchy members, like Cyrus 
does (i.e. a mailbox "foo/bar" can exists while "foo" doesn't).
If the client issues <LIST "" %>, the server would return:
      * LIST (\NoSelect) "/" "foo"

However, if the client issues <LIST () "" %>, the server can't return 
\NoSelect, as it was replaced by CHILDINFO. And the CHILDINFO extended 
data can't be returned as per prohibition in section 3.1 (in -16), under 
point 2 B):
           Note that the CHILDINFO
           extended data item can only be returned when the
           RECURSIVEMATCH selection option is specified.

This can be a bit unexpected for server implementors.
However there is a workaround for servers:
      * LIST (\NonExistent \HasChildren) "/" "foo"

So, my question is what do we do with this? The options I see are:
1). punt, let server and client implementors figure this out.
2). add the example and document the workaround as a proper way to 
respond in this case
3). allow CHILDINFO to be returned on extended LISTs with no RECURSIVEMATCH.

I personally don't like the option 1), as this issue is too subtle. I 
prefer option 2 over 3.




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 k3A751JD031131; Mon, 10 Apr 2006 00:05:01 -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 k3A751cP031130; Mon, 10 Apr 2006 00:05:01 -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 episteme-software.com (216-43-25-66.ip.mcleodusa.net [216.43.25.66]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3A750Vk031117 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 00:05:00 -0700 (MST) (envelope-from presnick@qualcomm.com)
Received: from [216.43.25.67] (127.0.0.1) by episteme-software.com with ESMTP (EIMS X 3.3d21) for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 02:04:52 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p07000c3fc05fb0b31b28@[216.43.25.67]>
X-Mailer: Eudora [Macintosh version 7.0a12]
Date: Mon, 10 Apr 2006 02:04:51 -0500
To: IMAP Extensions <ietf-imapext@imc.org>
From: Pete Resnick <presnick@qualcomm.com>
Subject: To Do list
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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>

Updates post-Dallas:

1. Pete is doing the write-up for ANNOTATE and will soon pass it on 
to the IESG for IETF Last Call.
2. Waiting for a rev of LISTEXT from Barry. Then Pete will write-up 
and pass it on to the IESG for IETF Last Call.
3. Waiting for a rev of COMPARATOR from Arnt. The current version of 
IMAPi18n should be ready to go. Once we get the new draft of 
COMPARATOR, Pete will issue a WG Last Call for both.

Anything else?

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



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 k35BlJUT016587; Wed, 5 Apr 2006 04:47:19 -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 k35BlJCv016586; Wed, 5 Apr 2006 04:47:19 -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 rutherford.zen.co.uk (rutherford.zen.co.uk [212.23.3.142]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k35BlIQ0016580 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 04:47:19 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1FR6Tk-0003UA-Ly; Wed, 05 Apr 2006 11:47:17 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id 8FE66498002; Wed,  5 Apr 2006 12:53:01 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28070-03; Wed, 5 Apr 2006 12:52:46 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id A237B498003; Wed,  5 Apr 2006 12:52:44 +0100 (BST)
Date: Wed, 05 Apr 2006 12:46:54 +0100
Subject: Re: postaddress, several addresses
References: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com> <4433971E.7010301@isode.com> <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
In-Reply-To: <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
MIME-Version: 1.0
Message-Id: <6711.1144237616.236199@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Cc: <ietf-imapext@imc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Rutherford-IP: [217.155.137.60]
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>

On Wed Apr  5 11:34:47 2006, Arnt Gulbrandsen wrote:
> 
> Alexey Melnikov writes:
> > If they are all equivalent - any.
> 
> Why "any" not "all"?

POSTADDRESS is just for a client to get an address to use for 
converting an FCC into a BCC, hence you only need a single address 
for that. I can't think of an alternate use for it at the moment, so 
I'm perfectly happy with just one address.

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k35BenXT016357; Wed, 5 Apr 2006 04:40:49 -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 k35BenGQ016356; Wed, 5 Apr 2006 04:40:49 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k35BelHb016350 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 04:40:48 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Wed, 5 Apr 2006 12:40:42 +0100
Message-ID: <4433ACAF.1010005@isode.com>
Date: Wed, 05 Apr 2006 12:40:31 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: ietf-imapext@imc.org
Subject: Re: postaddress, several addresses
References: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com>  <4433971E.7010301@isode.com> <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
In-Reply-To: <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Arnt Gulbrandsen wrote:

>Alexey Melnikov writes:
>  
>
>>If they are all equivalent - any.
>>    
>>
>Why "any" not "all"?
>  
>
What would the client do if the server returns multiple? Pick one at random?
I think the IMAP server is in a better position to decide which address 
to return.



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 k35AXwQ2013413; Wed, 5 Apr 2006 03:33:58 -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 k35AXwea013412; Wed, 5 Apr 2006 03:33:58 -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 k35AXvNJ013406 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 03:33:57 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 3AA084AC32 for <ietf-imapext@imc.org>; Wed,  5 Apr 2006 12:33:56 +0200 (CEST)
Message-Id: <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
Date: Wed, 5 Apr 2006 12:34:47 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-imapext@imc.org
Subject: Re: postaddress, several addresses
References: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com> <4433971E.7010301@isode.com>
In-Reply-To: <4433971E.7010301@isode.com>
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>

Alexey Melnikov writes:
> If they are all equivalent - any.

Why "any" not "all"?

Arnt



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 k35A8dcs012264; Wed, 5 Apr 2006 03:08:39 -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 k35A8dUL012263; Wed, 5 Apr 2006 03:08:39 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k35A8caf012257 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 03:08:38 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Wed, 5 Apr 2006 11:08:32 +0100
Message-ID: <4433971E.7010301@isode.com>
Date: Wed, 05 Apr 2006 11:08:30 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: postaddress, several addresses
References: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com>
In-Reply-To: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Arnt Gulbrandsen wrote:

> What if there are several addresses which will cause email to be 
> delivered to a mailbox? What should postaddress report?

If they are all equivalent - any.



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 k35A1Seq011557; Wed, 5 Apr 2006 03:01:28 -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 k35A1SIB011556; Wed, 5 Apr 2006 03:01:28 -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 k35A1QTr011550 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 03:01:27 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 9F7114AC32 for <ietf-imapext@imc.org>; Wed,  5 Apr 2006 12:01:25 +0200 (CEST)
Message-Id: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com>
Date: Wed, 5 Apr 2006 12:02:16 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: postaddress, several addresses
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>

What if there are several addresses which will cause email to be 
delivered to a mailbox? What should postaddress report?

Arnt



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 k34LXJRI080017; Tue, 4 Apr 2006 14:33:19 -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 k34LXJ0Y080016; Tue, 4 Apr 2006 14:33:19 -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 rutherford.zen.co.uk (rutherford.zen.co.uk [212.23.3.142]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k34LXIce080010 for <ietf-imapext@IMC.ORG>; Tue, 4 Apr 2006 14:33:18 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1FQt9I-0005Xm-3n; Tue, 04 Apr 2006 21:33:16 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id B43E7498003; Tue,  4 Apr 2006 22:38:57 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25043-03; Tue, 4 Apr 2006 22:38:52 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id 700A5498002; Tue,  4 Apr 2006 22:38:50 +0100 (BST)
Date: Tue, 04 Apr 2006 22:33:08 +0100
Subject: Re: [Imap-protocol] authentication condition reporting extensions
References:  <Pine.WNT.4.65.0604041404240.4136@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To:  <Pine.WNT.4.65.0604041404240.4136@Tomobiki-Cho.CAC.Washington.EDU>
MIME-Version: 1.0
Message-Id: <4142.1144186388.432464@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Mark Crispin <MRC@cac.washington.edu>
Cc: IMAP Extensions WG <ietf-imapext@imc.org>, IMAP Protocol Interest List <IMAP-Protocol@u.washington.edu>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Rutherford-IP: [217.155.137.60]
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>

On Tue Apr  4 22:15:01 2006, Mark Crispin wrote:
> The conditions in question are:
>  . password will expire at such-and-such future time (or interval)
>  . password has expired
>  . account will expire at such-and-such future time (or interval)
>  . account has expired
>  . account has been disabled
> 
> 
That last is definitely a security issue, isn't it?

It'd be useful to be able to signal all the SASL codes that are in 
ACAP - TRANSITION-NEEDED, for instance, or AUTH-TOO-WEAK.

> Example (with both ALERT for compatibility and new response code)
> 
> * NO [EXPIRED http://imap.example.com/expired]
> tag NO [ALERT] Your account has expired, contact the help desk
> 
> Comments?

I'm not convinced all clients will understand untagged responses 
inside an AUTHENTICATE command - I think Alexey and Corby abandoned 
that syntax style for the RECONNECT work a while back at least partly 
due to that concern.

Also, I don't think that the alert is needed here - clients typically 
report the text of the error after a failure, so I suspect you're 
safe using the terminal response:

tag NO [EXPIRED http://imap.example.com/expired] Your account has 
expired, contact the help desk.

However, the better alternative would be to combine this proposal 
with an update to the AUTHENTICATE command which both explicitly 
added untagged responses during its execution, and supported both 
initial response and final success SASL data from the server. You 
could make it use literal8 instead of base64, too

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k34LD0LC079411; Tue, 4 Apr 2006 14:13:00 -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 k34LD0hi079410; Tue, 4 Apr 2006 14:13:00 -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 mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k34LCw12079403 for <ietf-imapext@IMC.ORG>; Tue, 4 Apr 2006 14:12:59 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k34LCwbH005688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Apr 2006 14:12:58 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k34LCv0b022004 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 4 Apr 2006 14:12:57 -0700
Date: Tue, 4 Apr 2006 14:15:01 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: IMAP Protocol Interest List <IMAP-Protocol@U.Washington.EDU>
cc: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: authentication condition reporting extensions
Message-ID: <Pine.WNT.4.65.0604041404240.4136@Tomobiki-Cho.CAC.Washington.EDU>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

The question has come up about possible extensions to what may optionally 
be reported by the server due to authentication conditions.  Obviously, 
there is substantial security sensitivity here.

The conditions in question are:
  . password will expire at such-and-such future time (or interval)
  . password has expired
  . account will expire at such-and-such future time (or interval)
  . account has expired
  . account has been disabled

It is desired to include a URL that will provide more information.

Currently, the only way to do this is with ALERT, but perhaps it would be 
useful if the client could know about some of these.

Example (with both ALERT for compatibility and new response code)

* NO [EXPIRED http://imap.example.com/expired]
tag NO [ALERT] Your account has expired, contact the help desk

Comments?

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



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 k34AhBGx052989; Tue, 4 Apr 2006 03:43:11 -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 k34AhBqU052988; Tue, 4 Apr 2006 03:43:11 -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 dmgw.movial.fi (dmgw.movial.fi [62.236.91.5]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k34Ah91F052961 for <ietf-imapext@imc.org>; Tue, 4 Apr 2006 03:43:09 -0700 (MST) (envelope-from tss@iki.fi)
Received: from movial.fi (hellmail.movial.fi [62.236.91.6]) by dmgw.movial.fi (Postfix) with ESMTP id 22CDD231 for <ietf-imapext@imc.org>; Tue,  4 Apr 2006 13:43:02 +0300 (EEST)
Received: from localhost (hellmail.movial.fi [127.0.0.1]) by movial.fi (Postfix) with ESMTP id 13BE680068 for <ietf-imapext@imc.org>; Tue,  4 Apr 2006 13:43:02 +0300 (EEST)
Received: from movial.fi ([127.0.0.1]) by localhost (hellmail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01203-10 for <ietf-imapext@imc.org>; Tue, 4 Apr 2006 13:43:01 +0300 (EEST)
Received: from sd022.hel.movial.fi (sd022.hel.movial.fi [172.17.49.22]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by movial.fi (Postfix) with ESMTP id D2E8680063 for <ietf-imapext@imc.org>; Tue,  4 Apr 2006 13:43:01 +0300 (EEST)
Subject: Re: More on LISTEXT
From: Timo Sirainen <tss@iki.fi>
To: ietf-imapext@imc.org
In-Reply-To: <44316AA9.8040505@watson.ibm.com>
References: <68E7DF4660B140AC8B212B23@ninevah.local> <44316AA9.8040505@watson.ibm.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-OXTMHFGytnYb/AVupNXB"
Date: Tue, 04 Apr 2006 13:43:01 +0300
Message-Id: <1144147381.17923.13.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at movial.fi
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>

--=-OXTMHFGytnYb/AVupNXB
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2006-04-03 at 14:34 -0400, Barry Leiba wrote:
> > 1) Leave things as they are - getting annotations will result in gettin=
g=20
> > the standard flags all over again.
> >=20
> > 2) Add a new STDFLAGs return option such that if a RETURN is specified,=
=20
> > then standard flags are only returned if STDFLAG is present as one of=20
> > the return options. If there is no return option, then the normal=20
> > behaviour occurs.
> >=20
> > 3) Add a new NOSTDFLAGS return option such that if specified in RETURN,=
=20
> > the standard flags are not returned.
..
> I would be willing to add STDFLAGS if it's the case that extended LIST=20
> does NOT normally return them, and so we *always* have to ask for them=20
> explicitly.  But I don't like it; I'd rather behave more like the=20
> base-doc LIST command in this regard.

Actually this is how I originally read the 2) part. Never returning
flags unless asked sounds good to me..

> I will be happy to add NOSTDFLAGS (or some other such text) that=20
> EXPLICITLY tells LIST to deviate from the normal behaviour.

I'm not really against this either.

--=-OXTMHFGytnYb/AVupNXB
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBEMk21Q95cgkr2Z40RAlzlAJ48nu0tu30Z9b3X/a5j/TBLrf4BOACeI2Tr
RhGpLQIUKTpZqOKpnd/xTGg=
=xPEv
-----END PGP SIGNATURE-----

--=-OXTMHFGytnYb/AVupNXB--



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 k33IYQ2v069832; Mon, 3 Apr 2006 11:34:26 -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 k33IYQVp069831; Mon, 3 Apr 2006 11:34:26 -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 igw2.watson.ibm.com (igw2.watson.ibm.com [129.34.20.6]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k33IYP2p069824 for <ietf-imapext@imc.org>; Mon, 3 Apr 2006 11:34:26 -0700 (MST) (envelope-from leiba@watson.ibm.com)
Received: from sp1n293en1.watson.ibm.com (sp1n293en1.watson.ibm.com [129.34.20.41]) by igw2.watson.ibm.com (8.12.11.20060308/8.13.1/8.13.1-2005-04-25 igw) with ESMTP id k33IYcMi020750 for <ietf-imapext@imc.org>; Mon, 3 Apr 2006 14:34:38 -0400
Received: from sp1n293en1.watson.ibm.com (localhost [127.0.0.1]) by sp1n293en1.watson.ibm.com (8.11.7-20030924/8.11.7/01-14-2004_2) with ESMTP id k33IYJh40806 for <ietf-imapext@imc.org>; Mon, 3 Apr 2006 14:34:19 -0400
Received: from mars (mars.watson.ibm.com [9.2.40.64]) by sp1n293en1.watson.ibm.com (8.11.7-20030924/8.11.7/01-14-2004_1) with ESMTP id k33IYIB88028 for <ietf-imapext@imc.org>; Mon, 3 Apr 2006 14:34:18 -0400
Received: from saturn ([9.2.43.127]) by mars.watson.ibm.com (IMF.2005.07.16.1050.haw) with SMTP ID IMFd1144089258.4650; Mon, 03 Apr 2006 14:34:18 -0400
Message-ID: <44316AA9.8040505@watson.ibm.com>
Date: Mon, 03 Apr 2006 14:34:17 -0400
From: Barry Leiba <leiba@watson.ibm.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: ietf-imapext@imc.org
Subject: Re: More on LISTEXT
References: <68E7DF4660B140AC8B212B23@ninevah.local>
In-Reply-To: <68E7DF4660B140AC8B212B23@ninevah.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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>

> 1) Leave things as they are - getting annotations will result in getting 
> the standard flags all over again.
> 
> 2) Add a new STDFLAGs return option such that if a RETURN is specified, 
> then standard flags are only returned if STDFLAG is present as one of 
> the return options. If there is no return option, then the normal 
> behaviour occurs.
> 
> 3) Add a new NOSTDFLAGS return option such that if specified in RETURN, 
> the standard flags are not returned.

I AM VERY STRONGLY AGAINST 2.
As Dave has already pointed out, this is a specification nightmare, 
giving all return options the side-effect of turning off the default 
STDFLAGS, and requiring that it be specified.

As a document editor, I WILL NOT put it in unless the WG chair (Hi 
Pete!) declares consensus for it.

I would be willing to add STDFLAGS if it's the case that extended LIST 
does NOT normally return them, and so we *always* have to ask for them 
explicitly.  But I don't like it; I'd rather behave more like the 
base-doc LIST command in this regard.

I will be happy to add NOSTDFLAGS (or some other such text) that 
EXPLICITLY tells LIST to deviate from the normal behaviour.


I will point out a couple of things:

1. As Dave said, NOSTDFLAGS *could* be added in an extension.

2. STDFLAGS could be added in the METADATA spec, setting things up so 
that the METADATA return option is the only one that cancels the default 
STDFLAGS return, and so STDFLAGS is needed to explicitly put it back.  I 
don't like that approach, but since it wouldn't affect LISTEXT I 
wouldn't care about it just now.  :-)


For now, I'm doing nothing about it in the LISTEXT spec, until we decide 
what the consensus is.

Barry

--
Barry Leiba, Pervasive Computing Technology  (leiba@watson.ibm.com)
http://www.research.ibm.com/people/l/leiba
http://www.research.ibm.com/spam



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 k31JH3g2041944; Sat, 1 Apr 2006 12:17:03 -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 k31JH3Dr041943; Sat, 1 Apr 2006 12:17:03 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k31JH2M1041937 for <ietf-imapext@imc.org>; Sat, 1 Apr 2006 12:17:03 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Sat, 1 Apr 2006 20:16:55 +0100
Message-ID: <442ED1A4.8070606@isode.com>
Date: Sat, 01 Apr 2006 11:16:52 -0800
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Ken Murchison <murch@andrew.cmu.edu>
CC: ietf-imapext@imc.org
Subject: Re: CONDSTORE
References: <4429A882.7010609@andrew.cmu.edu> <442D3DFE.20401@isode.com> <442D708F.9090707@andrew.cmu.edu>
In-Reply-To: <442D708F.9090707@andrew.cmu.edu>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Ken Murchison wrote:

> Alexey Melnikov wrote:
>
>> Ken Murchison wrote:
>
>>> And what should be done for STATUS HIGHESTMODSEQ when the mailbox 
>>> doesn't support CONDSTORE?  I assume that the server should just 
>>> ignore the HIGHESTMODSEQ status item, in the same way that it will 
>>> have to ignore the SELECT/EXAMINE CONDSTORE parameter.
>>
>> Right.
>
> Hmm, the ABNF for the STATUS response requires at least one 
> status-att.  So what should we do for:
>
> a STATUS mailbox (HIGHESTMODSEQ)
>
> Return a HIGHESTMODSEQ of zero, or don't return * STATUS for the 
> mailbox?  I'm assuming the latter.

The latter, but I guess the document can be updated to say that the 
former means "modseq are not supported for the mailbox".





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 k3RJoD5Q058190; Thu, 27 Apr 2006 12:50:13 -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 k3RJoD8Y058188; Thu, 27 Apr 2006 12:50:13 -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 willow.neustar.com (willow.neustar.com [209.173.53.84]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3RJoDpF058175 for <ietf-imapext@imc.org>; Thu, 27 Apr 2006 12:50:13 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k3RJo19W021150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Apr 2006 19:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FZCUz-0003Wu-M5; Thu, 27 Apr 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-imapext@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-imapext-list-extensions-17.txt 
Message-Id: <E1FZCUz-0003Wu-M5@stiedprstage1.ietf.org>
Date: Thu, 27 Apr 2006 15:50:01 -0400
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Message Access Protocol Extension Working Group of the IETF.

	Title		: IMAP4 LIST Command Extensions
	Author(s)	: B. Leiba, A. Melnikov
	Filename	: draft-ietf-imapext-list-extensions-17.txt
	Pages		: 39
	Date		: 2006-4-27
	
IMAP4 has two commands for listing mailboxes: LIST and LSUB.  As we
have added extensions, such as Mailbox Referrals, that have required
specialized lists we have had to expand the number of list commands,
since each extension must add its function to both LIST and LSUB, and
these commands are not, as they are defined, extensible.  If we've
needed the extensions to work together, we've had to add a set of
commands to mix the different options, the set increasing in size
with each new extension.  This document describes an extension to the
base LIST command that will allow these additions to be done with
mutually compatible options to the LIST command, avoiding the
exponential increase in specialized list commands.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-imapext-list-extensions-17.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-imapext-list-extensions-17.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-imapext-list-extensions-17.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2006-4-27103028.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-imapext-list-extensions-17.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-imapext-list-extensions-17.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2006-4-27103028.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 k3LMOvZJ019627; Fri, 21 Apr 2006 15:24:57 -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 k3LMOvK2019626; Fri, 21 Apr 2006 15:24:57 -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 episteme-software.com (216-43-25-66.ip.mcleodusa.net [216.43.25.66]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3LMOuaZ019619 for <ietf-imapext@imc.org>; Fri, 21 Apr 2006 15:24:57 -0700 (MST) (envelope-from presnick@qualcomm.com)
Received: from [216.43.25.67] (127.0.0.1) by episteme-software.com with ESMTP (EIMS X 3.3d22) for <ietf-imapext@imc.org>; Fri, 21 Apr 2006 17:24:51 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p07000c24c06edb5b3daf@[216.43.25.67]>
X-Mailer: Eudora [Macintosh version 7.0a12]
Date: Fri, 21 Apr 2006 17:24:48 -0500
To: IMAP Extensions <ietf-imapext@imc.org>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Minutes
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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>

Please confirm these:

Minutes of the IETF 65 IMAPEXT meeting, 22 March 2006.

Prepared by Pete Resnick - Chair
Rob Siemborski - In room minute taker

Agenda
- LIST Extensions
- Comparators/Internationalization
- ANNOTATE and ANNOTATEMORE
- Email Address Internationalization update

Barry Lieba lead discussion on the LIST Extensions draft.

-Discussion first concerned whether servers should be able to refuse 
to return CHILDREN information even if the client requests it. The 
sense of the room was that this was reasonable and that Barry will 
rework the section on CHILDREN.
- Some discussion was had about removing some of the text on special 
cases of combinations of features. The sense of the room was that 
this was unnecessary. Barry will attempt to simplify some of the text.
- The room was generally agreed that no further working group last 
call would be needed. Barry will submit his changed document and Pete 
will write up and submit it for IESG last call.

Chris Newman lead discussion on the comparators and i18n work.

- Not much objection to the idea that the basic collation refer to a 
specific version of UCA.
- General agreement that multi-valued attributes were not necessary 
and that that section be removed. A protocol that needs multi-valued 
attributes can describe how to use them.
- General agreement that table downloading be made non-normative.
- Some discussion about ascii-casemap. Agreement that it should be 
have like i;octet and throws no errors. Agreemet to make it "i" 
instead of "en".
- Some discussion of the COMPARATOR extension (for SEARCH, etc). No 
particular changes noted to plans.
Two new drafts will be produced and working group last called.

Cyrus Daboo lead the discussion of ANNOTATE.

- Now experimental instead of standards track with a recommendation 
to implement from the working group. Cyrus will decide what to do 
about the capability.
- Discussion of removing Content-Language (leaving only attribute, 
value, and size). Sense of the room to do so.
- Discussion of folding ANNOTATEMORE into LISTEXT. Not a significant 
amount of support for it.
- Discussion of changing ANNOTATEMORE to METADATA.

Pete Resnick and Chris Newman talked about some of the issues with EAI.
- Only action is for IMAP people to keep tabs on what is going on there.

Further discussion:
- It appears that ACL2 is going to be dropped as a working group item.

End of meeting. Hope to complete before Montreal.
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



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 k3EIstrI028087; Fri, 14 Apr 2006 11:54:55 -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 k3EIstro028086; Fri, 14 Apr 2006 11:54:55 -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 mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3EIsseL028080 for <ietf-imapext@imc.org>; Fri, 14 Apr 2006 11:54:55 -0700 (MST) (envelope-from mrc@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3EIsjv0017325 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 Apr 2006 11:54:45 -0700
X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3EIsibm018319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 14 Apr 2006 11:54:45 -0700
Date: Fri, 14 Apr 2006 11:54:43 -0700 (PDT)
From: Mark Crispin <mrc@CAC.Washington.EDU>
To: Timo Sirainen <tss@iki.fi>
cc: ietf-imapext@imc.org
Subject: Re: i18n draft and search
In-Reply-To: <1145030086.10727.96.camel@hurina>
Message-ID: <Pine.OSX.4.64.0604141150110.15258@pangtzu.panda.com>
References: <1145030086.10727.96.camel@hurina>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

Regarding conflicts between RFC 3501 and the i18n document:

The i18n draft overrides/updates rules of RFC 3501.  So in any case of a 
seeming contradiction between RFC 3501 and the i18n document, the i18n 
document is the authority for all implementations that advertise support 
for the i18n document.

I'll leave it for others to answer your other points.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.



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 k3EFssUp019302; Fri, 14 Apr 2006 08:54:54 -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 k3EFssuu019301; Fri, 14 Apr 2006 08:54:54 -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 danu.procontrol.fi (kone17.procontrol.vip.fi [212.149.71.178] (may be forged)) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3EFsru6019292 for <ietf-imapext@imc.org>; Fri, 14 Apr 2006 08:54:53 -0700 (MST) (envelope-from tss@iki.fi)
Received: from hurina (82-203-177-3.dsl.gohome.fi [82.203.177.3]) by danu.procontrol.fi (Postfix) with ESMTP id 52F7B1C1D0E2 for <ietf-imapext@imc.org>; Fri, 14 Apr 2006 18:54:57 +0300 (EEST)
Subject: i18n draft and search
From: Timo Sirainen <tss@iki.fi>
To: ietf-imapext@imc.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-1Inqn36ZC6EWRadTC/gT"
Date: Fri, 14 Apr 2006 18:54:46 +0300
Message-Id: <1145030086.10727.96.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
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>

--=-1Inqn36ZC6EWRadTC/gT
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

There's this example:

        < The client requests pure octet matching, then does a search
          for potential GIF files, then switches back to its usual
          comparator. >

But RFC 3501 says:

      Server implementations MAY exclude [MIME-IMB] body parts with
      terminal content media types other than TEXT and MESSAGE from
      consideration in SEARCH matching.

Should it be required that when comparator is "i;octet", all MIME parts
MUST be searched?

What to do if SEARCH command doesn't give a CHARSET parameter but search
key contains non-ASCII? Maybe require that after COMPARATOR command the
CHARSET paramter MUST be given for all SEARCH commands? Alternative way
would be to make non-CHARSET searches always use i;octet comparator.

Stringprep contains text "Stored strings using the profile MUST NOT
contain any unassigned code points." and talks about problems with it.
Now, since emails come from other systems which may be using newer
unicode maps than the IMAP server knows, there's no way to prevent this.
What should we do when we encounter such emails while searching?

--=-1Inqn36ZC6EWRadTC/gT
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBEP8XGyUhSUUBViskRAlnlAKCHFY5sY6ZMz/0CLxImuTLHo2FXkQCfaf50
R6aGVsKdHqgB0uud5jSbkrg=
=x8eo
-----END PGP SIGNATURE-----

--=-1Inqn36ZC6EWRadTC/gT--



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 k3CFrXSB074358; Wed, 12 Apr 2006 08:53:33 -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 k3CFrXDp074357; Wed, 12 Apr 2006 08:53:33 -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 mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3CFrWqv074350 for <ietf-imapext@imc.org>; Wed, 12 Apr 2006 08:53:32 -0700 (MST) (envelope-from mrc@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3CFrTDm018347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 12 Apr 2006 08:53:30 -0700
X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3CFrM9b029607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Apr 2006 08:53:28 -0700
Date: Wed, 12 Apr 2006 08:53:20 -0700 (PDT)
From: Mark Crispin <mrc@CAC.Washington.EDU>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
In-Reply-To: <443CEB1C.8080102@isode.com>
Message-ID: <Pine.OSX.4.64.0604120852330.2906@pangtzu.panda.com>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <443C11B5.1000302@isode.com> <Pine.WNT.4.65.0604111335250.3332@Tomobiki-Cho.CAC.Washington.EDU> <443CEB1C.8080102@isode.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

On Wed, 12 Apr 2006, Alexey Melnikov wrote:
>> Define a Namespace_Response_Extension, e.g., with a first string of 
>> "DESCRIPTION".  The values in the string list can either be a single string 
>> containing a description (which in turn is affected by the LANGUAGE 
>> setting) or it can be a list of language-tagged descriptions.  Your choice.
> I don't like the latter, as this can potentially result in a very large list.

I figured that would be your reaction.

> The draft effectively defines the former, even though it is called 
> differently. I agree with the request to change TRANSLATION to something 
> else.

Sounds good to me.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.



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 k3CBvceO063843; Wed, 12 Apr 2006 04:57:38 -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 k3CBvc1T063842; Wed, 12 Apr 2006 04:57:38 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3CBvYU7063835 for <ietf-imapext@imc.org>; Wed, 12 Apr 2006 04:57:35 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.2.164] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Wed, 12 Apr 2006 12:57:22 +0100
Message-ID: <443CEB1C.8080102@isode.com>
Date: Wed, 12 Apr 2006 12:57:16 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
To: Mark Crispin <MRC@CAC.Washington.EDU>
CC: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <443C11B5.1000302@isode.com> <Pine.WNT.4.65.0604111335250.3332@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To: <Pine.WNT.4.65.0604111335250.3332@Tomobiki-Cho.CAC.Washington.EDU>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Mark Crispin wrote:

> On Tue, 11 Apr 2006, Alexey Melnikov wrote:
>
>>> then why not add that (a description), along with a provision for 
>>> the description to be in multiple languages?
>>
>> I am not sure what you are suggesting here. Can you clarify?
>
> Define a Namespace_Response_Extension, e.g., with a first string of 
> "DESCRIPTION".  The values in the string list can either be a single 
> string containing a description (which in turn is affected by the 
> LANGUAGE setting) or it can be a list of language-tagged 
> descriptions.  Your choice.

I don't like the latter, as this can potentially result in a very large list.
The draft effectively defines the former, even though it is called differently. I agree with the request to change TRANSLATION to something        else.



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 k3BNqIXg037300; Tue, 11 Apr 2006 16:52:18 -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 k3BNqIHJ037299; Tue, 11 Apr 2006 16:52:18 -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 laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BNqG1c037293 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 16:52:18 -0700 (MST) (envelope-from lisa@osafoundation.org)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id CBD20142273; Tue, 11 Apr 2006 16:52:15 -0700 (PDT)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30791-06; Tue, 11 Apr 2006 16:52:14 -0700 (PDT)
Received: from [192.168.103.124] (adsl-75-5-124-98.dsl.pltn13.sbcglobal.net [75.5.124.98]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 520EB142266; Tue, 11 Apr 2006 16:52:14 -0700 (PDT)
In-Reply-To: <p07000c3fc05fb0b31b28@[216.43.25.67]>
References: <p07000c3fc05fb0b31b28@[216.43.25.67]>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2C88BD07-F10B-4E61-980D-4B9CDA824A17@osafoundation.org>
Cc: IMAP Extensions <ietf-imapext@imc.org>
Content-Transfer-Encoding: 7bit
From: Lisa Dusseault <lisa@osafoundation.org>
Subject: Re: To Do list
Date: Tue, 11 Apr 2006 16:52:10 -0700
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.746.2)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
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>

Also new milestones for the charter :)
(sorry, that was on my todo list before Dallas but I didn't get date  
commitments from everyone)

Lisa

On Apr 10, 2006, at 12:04 AM, Pete Resnick wrote:

>
> Updates post-Dallas:
>
> 1. Pete is doing the write-up for ANNOTATE and will soon pass it on  
> to the IESG for IETF Last Call.
> 2. Waiting for a rev of LISTEXT from Barry. Then Pete will write-up  
> and pass it on to the IESG for IETF Last Call.
> 3. Waiting for a rev of COMPARATOR from Arnt. The current version  
> of IMAPi18n should be ready to go. Once we get the new draft of  
> COMPARATOR, Pete will issue a WG Last Call for both.
>
> Anything else?
>
> pr
> -- 
> Pete Resnick <http://www.qualcomm.com/~presnick/>
> QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858) 
> 651-1102
>



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 k3BMattQ033262; Tue, 11 Apr 2006 15:36:55 -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 k3BMatlW033260; Tue, 11 Apr 2006 15:36:55 -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 k3BMarBc033242 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 15:36:54 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 9F4B54AC35; Wed, 12 Apr 2006 00:36:52 +0200 (CEST)
Message-Id: <fsUEuymqzYv8L0arplUMuw.md5@libertango.oryx.com>
Date: Wed, 12 Apr 2006 00:38:15 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Mark Crispin <mrc@cac.washington.edu>, Dave Cridland <dave@cridland.net>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <9875.1144791333.165815@peirce.dave.cridland.net> <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
In-Reply-To: <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
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>

Mark Crispin writes:
> I want to make certain (wooden stake in heart, garlic in coffin, 
> cruxifix on top, etc.) that the vampire of translating protocol 
> keywords is kept firmly dead and not just undead.

Relax. Completely.

Arnt



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 k3BM7k2x032067; Tue, 11 Apr 2006 15:07:46 -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 k3BM7kai032066; Tue, 11 Apr 2006 15:07:46 -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 heisenberg.zen.co.uk (heisenberg.zen.co.uk [212.23.3.141]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BM7jpd032060 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 15:07:45 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by heisenberg.zen.co.uk with esmtp (Exim 4.30) id 1FTR1U-0007ey-Oo; Tue, 11 Apr 2006 22:07:44 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id 230CD498003; Tue, 11 Apr 2006 23:14:38 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07622-07; Tue, 11 Apr 2006 23:14:28 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id 3636D498002; Tue, 11 Apr 2006 23:14:26 +0100 (BST)
Date: Tue, 11 Apr 2006 23:07:32 +0100
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <9875.1144791333.165815@peirce.dave.cridland.net> <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
In-Reply-To: <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
MIME-Version: 1.0
Message-Id: <9875.1144793252.496397@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Mark Crispin <mrc@CAC.Washington.EDU>
Cc: <ietf-imapext@imc.org>, Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Heisenberg-IP: [217.155.137.60]
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>

On Tue Apr 11 23:00:42 2006, Mark Crispin wrote:
> On Tue, 11 Apr 2006, Dave Cridland wrote:
>>> If the intention is to have a human-readable namespace 
>>> description extension, then why not add that (a description), 
>>> along with a provision for the description to be in multiple 
>>> languages?
>> I like it, but I think that's essentially what it provides - a 
>> client simply has to issue a LANGUAGE command at some point prior 
>> to NAMESPACE. "Translating" the namespace from "#news" to "Usenet 
>> groups" for language "en" seems sensible. The text ought to be 
>> changed to reflect this (more sensible) usage, though.
> 
> I have a semantic, although probably not technical, objection.
> 
> 
Yes, I agree - to make this clear, the protocol keywords need to be 
changed to reflect the changed semantics.

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k3BM0kkC031857; Tue, 11 Apr 2006 15:00:46 -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 k3BM0kBU031856; Tue, 11 Apr 2006 15:00:46 -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 mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BM0jNf031850 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 15:00:45 -0700 (MST) (envelope-from mrc@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3BM0h0r002094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Apr 2006 15:00:43 -0700
X-Auth-Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.37.173]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3BM0gO0017584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Apr 2006 15:00:42 -0700
Date: Tue, 11 Apr 2006 15:00:42 -0700 (PDT)
From: Mark Crispin <mrc@CAC.Washington.EDU>
To: Dave Cridland <dave@cridland.net>
cc: ietf-imapext@imc.org, Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
In-Reply-To: <9875.1144791333.165815@peirce.dave.cridland.net>
Message-ID: <Pine.LNX.5.00.0604111456090.25394@shiva2.cac.washington.edu>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <9875.1144791333.165815@peirce.dave.cridland.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

On Tue, 11 Apr 2006, Dave Cridland wrote:
>> If the intention is to have a human-readable namespace description 
>> extension, then why not add that (a description), along with a provision 
>> for the description to be in multiple languages?
> I like it, but I think that's essentially what it provides - a client simply 
> has to issue a LANGUAGE command at some point prior to NAMESPACE. 
> "Translating" the namespace from "#news" to "Usenet groups" for language "en" 
> seems sensible. The text ought to be changed to reflect this (more sensible) 
> usage, though.

I have a semantic, although probably not technical, objection.

We're not "translating" the namespace from "#news." to "Usenet Groups" 
for language "en".

We are describing the namespace "#news." as being "Usenet Groups" in 
language "en"; and there are descriptions available in other languages. 
In no instance is "#news." translated; in all cases that is the name of 
the namespace.

I want to make certain (wooden stake in heart, garlic in coffin, 
cruxifix on top, etc.) that the vampire of translating protocol keywords 
is kept firmly dead and not just undead.  [Remember French-translated 
BASIC?  *Shudder*]

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



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 k3BLZq70030659; Tue, 11 Apr 2006 14:35:52 -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 k3BLZqfE030658; Tue, 11 Apr 2006 14:35:52 -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 heisenberg.zen.co.uk (heisenberg.zen.co.uk [212.23.3.141]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BLZpC4030649 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 14:35:52 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by heisenberg.zen.co.uk with esmtp (Exim 4.30) id 1FTQWX-0001eE-Pj; Tue, 11 Apr 2006 21:35:45 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id E7552498003; Tue, 11 Apr 2006 22:42:38 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07570-08; Tue, 11 Apr 2006 22:42:28 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id A2771498002; Tue, 11 Apr 2006 22:42:26 +0100 (BST)
Date: Tue, 11 Apr 2006 22:35:32 +0100
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To:  <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
MIME-Version: 1.0
Message-Id: <9875.1144791333.165815@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Mark Crispin <MRC@cac.washington.edu>
Cc: <ietf-imapext@imc.org>, Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Heisenberg-IP: [217.155.137.60]
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>

On Tue Apr 11 21:28:03 2006, Mark Crispin wrote:
> 
> On Tue, 11 Apr 2006, Alexey Melnikov wrote:
>> To clarify: the LANGUAGE command doesn't localize namespaces. It 
>> adds a new parameter to the NAMESPACE response that contains a 
>> translated version of the namespace, which can only be used in UI.
> 
> Why is this needed, given that NAMESPACE itself already identifies 
> namespaces by personal, other user, and shared/multi-user?
> 
> If the intention is to have a human-readable namespace description 
> extension, then why not add that (a description), along with a 
> provision for the description to be in multiple languages?

I like it, but I think that's essentially what it provides - a client 
simply has to issue a LANGUAGE command at some point prior to 
NAMESPACE. "Translating" the namespace from "#news" to "Usenet 
groups" for language "en" seems sensible. The text ought to be 
changed to reflect this (more sensible) usage, though.

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k3BKe4m8028443; Tue, 11 Apr 2006 13:40:04 -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 k3BKe4H4028442; Tue, 11 Apr 2006 13:40:04 -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 mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKe3jO028434 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:40:04 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3BKe3iJ028909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Apr 2006 13:40:03 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3BKe2pq025468 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 11 Apr 2006 13:40:02 -0700
Date: Tue, 11 Apr 2006 13:40:01 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
In-Reply-To: <443C11B5.1000302@isode.com>
Message-ID: <Pine.WNT.4.65.0604111335250.3332@Tomobiki-Cho.CAC.Washington.EDU>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU> <443C11B5.1000302@isode.com>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

On Tue, 11 Apr 2006, Alexey Melnikov wrote:
>> then why not add that (a description), along with a provision for the 
>> description to be in multiple languages?
> I am not sure what you are suggesting here. Can you clarify?

Define a Namespace_Response_Extension, e.g., with a first string of 
"DESCRIPTION".  The values in the string list can either be a single 
string containing a description (which in turn is affected by the LANGUAGE 
setting) or it can be a list of language-tagged descriptions.  Your 
choice.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



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 k3BKbOTH028352; Tue, 11 Apr 2006 13:37:24 -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 k3BKbOBl028351; Tue, 11 Apr 2006 13:37:24 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKbN3B028345 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:37:23 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 21:37:16 +0100
Message-ID: <443C1370.5000406@isode.com>
Date: Tue, 11 Apr 2006 21:37:04 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-imapext@imc.org
Subject: Re: Comments about draft-ietf-imapext-i18n-06.txt
References: <p07000c3fc05fb0b31b28@[216.43.25.67]> <443A5391.3090109@isode.com> <21242.1144674997.982052@peirce.dave.cridland.net>
In-Reply-To: <21242.1144674997.982052@peirce.dave.cridland.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Mark has suggested to split COMPARATOR from the rest of IMAP I18N. I 
kind of like the idea, considering that the latter might still be 
changing (or need more text). Can we get a general agreement if the 
split is a good thing and if it is, who is going to edit different 
pieces (presumably Arnt will co-edit one or both, but who else)?



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 k3BKToke028010; Tue, 11 Apr 2006 13:29:50 -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 k3BKToQr028009; Tue, 11 Apr 2006 13:29:50 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKTnIn028003 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:29:49 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 21:29:41 +0100
Message-ID: <443C11B5.1000302@isode.com>
Date: Tue, 11 Apr 2006 21:29:41 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mark Crispin <MRC@CAC.Washington.EDU>
CC: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com> <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To: <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Mark Crispin wrote:

> On Tue, 11 Apr 2006, Alexey Melnikov wrote:
>
>> To clarify: the LANGUAGE command doesn't localize namespaces. It adds 
>> a new parameter to the NAMESPACE response that contains a translated 
>> version of the namespace, which can only be used in UI.
>
> Why is this needed, given that NAMESPACE itself already identifies 
> namespaces by personal, other user, and shared/multi-user?
>
> If the intention is to have a human-readable namespace description 
> extension,

Yes.

> then why not add that (a description), along with a provision for the 
> description to be in multiple languages?

I am not sure what you are suggesting here. Can you clarify?



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 k3BKS62p027940; Tue, 11 Apr 2006 13:28:06 -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 k3BKS626027939; Tue, 11 Apr 2006 13:28:06 -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 mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKS57X027933 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:28:06 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3BKS5uD017068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Apr 2006 13:28:05 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3BKS4Gt021864 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 11 Apr 2006 13:28:04 -0700
Date: Tue, 11 Apr 2006 13:28:03 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
In-Reply-To: <443C0BCA.1000308@isode.com>
Message-ID: <Pine.WNT.4.65.0604111326030.3332@Tomobiki-Cho.CAC.Washington.EDU>
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com> <443C0BCA.1000308@isode.com>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

On Tue, 11 Apr 2006, Alexey Melnikov wrote:
> To clarify: the LANGUAGE command doesn't localize namespaces. It adds a new 
> parameter to the NAMESPACE response that contains a translated version of the 
> namespace, which can only be used in UI.

Why is this needed, given that NAMESPACE itself already identifies 
namespaces by personal, other user, and shared/multi-user?

If the intention is to have a human-readable namespace description 
extension, then why not add that (a description), along with a provision 
for the description to be in multiple languages?

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



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 k3BKBA9u026873; Tue, 11 Apr 2006 13:11:10 -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 k3BKBAns026872; Tue, 11 Apr 2006 13:11:10 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BKB9Af026862 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:11:10 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 21:11:04 +0100
Message-ID: <443C0D56.7080501@isode.com>
Date: Tue, 11 Apr 2006 21:11:02 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
CC: ietf-imapext@imc.org
Subject: Re: Comments about draft-ietf-imapext-i18n-06.txt
References: <p07000c3fc05fb0b31b28@[216.43.25.67]> <443A5391.3090109@isode.com> <21242.1144674997.982052@peirce.dave.cridland.net>
In-Reply-To: <21242.1144674997.982052@peirce.dave.cridland.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Dave Cridland wrote:

> 2) [Decouple NAMESPACE and LANGUAGE] - Consensus seemed to be in support.

Just to confirm: draft-ietf-imapext-i18n-xx.txt will still describe the 
TRANSLATION extension to the NAMESPACE response. If the server supports 
both the NAMESPACE extension and the LANGUAGE extension, it SHOULD 
return the NAMESPACE responses containing the TRANSLATION field.
However the requirement for the server to send the NAMESPACE response on 
LANGUAGE command is removed.

Alexey



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 k3BK4aBa026521; Tue, 11 Apr 2006 13:04:36 -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 k3BK4a5V026520; Tue, 11 Apr 2006 13:04:36 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BK4ZNY026514 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 13:04:35 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 21:04:26 +0100
Message-ID: <443C0BCA.1000308@isode.com>
Date: Tue, 11 Apr 2006 21:04:26 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Mark Crispin <mrc@CAC.Washington.EDU>
CC: ietf-imapext@imc.org
Subject: Re: I-D ACTION:draft-ietf-imapext-i18n-06.txt
References: <E1FEYGn-00010X-GY@stiedprstage1.ietf.org> <2012.1141249951.789009@peirce.dave.cridland.net> <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com>
In-Reply-To: <Pine.OSX.4.64.0603011434420.436@pangtzu.panda.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Mark Crispin wrote:

>> 2) Section 3.4:
>> What's paragraph 1 for?
>
> Agreed.  This dependency is not good.
>
> IMHO, the LANGUAGE command should NOT localize namespaces.

To clarify: the LANGUAGE command doesn't localize namespaces. It adds a 
new parameter to the NAMESPACE response that contains a translated 
version of the namespace, which can only be used in UI.

> Instead, if such as desired, the NAMESPACE command itself should be 
> extended to take an argument.  I can see cases in which a user may 
> want error messages in his preferred language but retain mailbox paths 
> in i-default.
>
> This doesn't add an additional RTT since the client has to do a 
> NAMESPACE command anyway if it purposes to use namespaces.




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 k3BEjhv8013403; Tue, 11 Apr 2006 07:45:43 -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 k3BEjhOh013402; Tue, 11 Apr 2006 07:45:43 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3BEjctX013395 for <ietf-imapext@imc.org>; Tue, 11 Apr 2006 07:45:39 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Tue, 11 Apr 2006 15:45:29 +0100
Message-ID: <443BC107.4060108@isode.com>
Date: Tue, 11 Apr 2006 15:45:27 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Cyrus Daboo <cyrus@daboo.name>
CC: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com> <71CD159CA68C102AE848B539@Cyrus-Daboo.local> <443A608C.9040204@isode.com> <67248422E8EA862DC9A68052@Cyrus-Daboo.local>
In-Reply-To: <67248422E8EA862DC9A68052@Cyrus-Daboo.local>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Cyrus Daboo wrote:

> Hi Alexey,
>
> I think we are missing something here:
>
> In Section 3 under the description of 'SUBSCRIBED' you state for the 
> LSUB command:
>
>      the \NoSelect attribute has a special meaning (it indicates that
>      this mailbox is not, itself, subscribed, but that it has
>      descendant mailboxes that are)* *
>
> Actually \NoSelect has two meanings here.

You are right. I've changed the text quoted above to say "... has a 
second special meaning ...".

> It can be the 'special' one described above (and called out in 3501) 
> as well as its usual meaning of referring to an unselectable mailbox - 
> only in this case one that is subscribed. As far as I can tell, there 
> is nothing in IMAP that prevents a \NoSelect mailbox (a 'directory') 
> from being subscribed to - so in theory it is possible to have a 
> \NoSelect subscribed mailbox that exists. So the following could happen:
>
> a LIST (SUBSCRIBED) "" "%"
> * LIST (\NoSelect \HasChildren) "/" "foo"
> a OK
>
> and that is different than:
>
> a LIST (SUBSCRIBED) "" "%"
> * LIST (\NonExistent \HasChildren) "/" "foo"
> a OK
>
> i.e. it MUST be possible to get back \NoSelect in a LIST (SUBSCRIBED).

Right.
Do we need to add this example to the document?

> So the key thing is this: with the original LSUB command the \NoSelect 
> flag had two possible meanings. With the extended LIST (SUBSCRIBED) 
> command \NoSelect retains its meaning from the LIST command, and the 
> new \NonExistant attribute is used to indicate second 'special' case 
> that LSUB allows.

That is correct.

Here is what I've added to the document:

In section 3.3 CHILDINFO extended data item:

        Note: Some servers allow for mailboxes to exist without requiring
        their parent to exist. For example, a mailbox "Customers/ABC" 
can exist
        while the mailbox "Customers" does not. As CHILDINFO extended data
        item is not allowed if the RECURSIVEMATCH selection option is 
not specified,
        such servers SHOULD use the "\NonExistent \HasChildren" 
attribute pair to signal
        to the client that there is a descendant mailbox that matches 
the selection
        criteria. See example 11 in Section 5.

And example 11 in Section 5:

        The following example shows how a server that supports missing
        mailbox hierarchy elements can signal to a client that didn't
        specify the RECURSIVEMATH selection option that there is
        a child mailbox that matches the selection criteria.

   C: a1 LIST (REMOTE) "" *
   S: * LIST () "/" music/rock
   S: * LIST (\Remote) "/" also/jazz
   S: a1 OK done

   C: a2 LIST () "" %
   S: * LIST (\NonExistent \HasChildren) "/" music
   S: a2 OK done

   C: a3 LIST (REMOTE) "" %
   S: * LIST (\NonExistent \HasChildren) "/" music
   S: * LIST (\NonExistent \HasChildren) "/" also
   S: a3 OK done

Comments?



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 k3AEs4qO052283; Mon, 10 Apr 2006 07:54:04 -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 k3AEs4MN052282; Mon, 10 Apr 2006 07:54:04 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3AEs43f052275 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 07:54:04 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 52C09D472D4; Mon, 10 Apr 2006 10:54:03 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 10:53:45 -0400
X-Sasl-enc: JvGT2/ICA/gMH+VoGo4KIiDsdjbSQwVecqD2lT3vvuyk 1144680825
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id EDBF13B0E; Mon, 10 Apr 2006 10:53:44 -0400 (EDT)
Date: Mon, 10 Apr 2006 10:54:43 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: Philip's issue with LIST-EXTENDED
Message-ID: <67248422E8EA862DC9A68052@Cyrus-Daboo.local>
In-Reply-To: <443A608C.9040204@isode.com>
References: <44393A10.1010006@isode.com> <71CD159CA68C102AE848B539@Cyrus-Daboo.local> <443A608C.9040204@isode.com>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi Alexey,

I think we are missing something here:

In Section 3 under the description of 'SUBSCRIBED' you state for the LSUB 
command:

      the \NoSelect attribute has a special meaning (it indicates that
      this mailbox is not, itself, subscribed, but that it has
      descendant mailboxes that are)

Actually \NoSelect has two meanings here. It can be the 'special' one 
described above (and called out in 3501) as well as its usual meaning of 
referring to an unselectable mailbox - only in this case one that is 
subscribed. As far as I can tell, there is nothing in IMAP that prevents a 
\NoSelect mailbox (a 'directory') from being subscribed to - so in theory 
it is possible to have a \NoSelect subscribed mailbox that exists. So the 
following could happen:

a LIST (SUBSCRIBED) "" "%"
* LIST (\NoSelect \HasChildren) "/" "foo"
a OK

and that is different than:

a LIST (SUBSCRIBED) "" "%"
* LIST (\NonExistent \HasChildren) "/" "foo"
a OK

i.e. it MUST be possible to get back \NoSelect in a LIST (SUBSCRIBED).

So the key thing is this: with the original LSUB command the \NoSelect flag 
had two possible meanings. With the extended LIST (SUBSCRIBED) command 
\NoSelect retains its meaning from the LIST command, and the new 
\NonExistant attribute is used to indicate second 'special' case that LSUB 
allows.

-- 
Cyrus Daboo



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 k3AEO10Z050163; Mon, 10 Apr 2006 07:24:01 -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 k3AEO1CP050162; Mon, 10 Apr 2006 07:24:01 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3AEO0LK050155 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 07:24:00 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 3E9E3D47570 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 10:23:59 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 10:23:41 -0400
X-Sasl-enc: UHFD3opP6sQ8rLrtflqKvv4JBQe4FcZCRZrr04HHuzjA 1144679020
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id 3C5363AD2 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 10:23:39 -0400 (EDT)
Date: Mon, 10 Apr 2006 10:24:40 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: IMAP Extensions <ietf-imapext@imc.org>
Subject: Re: To Do list
Message-ID: <10832BD2661EE838E2780A3A@Cyrus-Daboo.local>
In-Reply-To: <277F687E43102F02B0DED4B6@Cyrus-Daboo.local>
References:  <p07000c3fc05fb0b31b28@[216.43.25.67]> <277F687E43102F02B0DED4B6@Cyrus-Daboo.local>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi,

--On April 10, 2006 10:10:00 AM -0400 Cyrus Daboo <cyrus@daboo.name> wrote:

> 2) Typo 'encourated' -> 'encourage'.

Sorry - that should have been a change to 'encouraged'.

-- 
Cyrus Daboo



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 k3AE9MnD049306; Mon, 10 Apr 2006 07:09:22 -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 k3AE9MmU049305; Mon, 10 Apr 2006 07:09:22 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3AE9MFw049299 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 07:09:22 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 322D5D47060; Mon, 10 Apr 2006 10:09:21 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 10:09:03 -0400
X-Sasl-enc: Y8x1h6WtEtvAl7ndTEUtnHCWMRqAvmToTDrTCn+AU6bq 1144678142
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id 927A939B2; Mon, 10 Apr 2006 10:09:01 -0400 (EDT)
Date: Mon, 10 Apr 2006 10:10:00 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Pete Resnick <presnick@qualcomm.com>, IMAP Extensions <ietf-imapext@imc.org>
Subject: Re: To Do list
Message-ID: <277F687E43102F02B0DED4B6@Cyrus-Daboo.local>
In-Reply-To: <p07000c3fc05fb0b31b28@[216.43.25.67]>
References:  <p07000c3fc05fb0b31b28@[216.43.25.67]>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi Pete,

--On April 10, 2006 2:04:51 AM -0500 Pete Resnick <presnick@qualcomm.com> 
wrote:

> 3. Waiting for a rev of COMPARATOR from Arnt. The current version of
> IMAPi18n should be ready to go. Once we get the new draft of COMPARATOR,
> Pete will issue a WG Last Call for both.

Some comments on i18n draft:

1) Change 'ANNOTATEMORE' to 'METADATA' in text and update reference title.

2) Typo 'encourated' -> 'encourage'.

3) Language formal syntax element 'language-data' is not referenced. I 
think you need to add the following to fix that:

       response-payload  =/ language-data

4) In the language formal syntax, put the comment for 'resp-text' after the 
element not before it.

5) In the language formal syntax the comment for 'lang-tag-quoted' is not 
wrapped properly.

6) Comparator formal syntax element 'comparator-data' is not referenced. I 
think you need to add the following to fix that:

       response-payload  =/ comparator-data

7) In the comparator formal syntax there are some comments of the form: 
'this follows the xxx rule' - I'm not sure where each of the 'xxx' items 
come from - a reference should be added.

-- 
Cyrus Daboo



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 k3ADhQZj048360; Mon, 10 Apr 2006 06:43:26 -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 k3ADhQvY048359; Mon, 10 Apr 2006 06:43:26 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADhPg8048343 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:43:25 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 14:43:06 +0100
Message-ID: <443A60DF.9050804@isode.com>
Date: Mon, 10 Apr 2006 14:42:55 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cyrus Daboo <cyrus@daboo.name>
CC: Pete Resnick <presnick@qualcomm.com>, IMAP Extensions <ietf-imapext@imc.org>
Subject: Re: To Do list
References: <p07000c3fc05fb0b31b28@[216.43.25.67]> <A8DAD1A0C3FAFCDC4684FA74@Cyrus-Daboo.local>
In-Reply-To: <A8DAD1A0C3FAFCDC4684FA74@Cyrus-Daboo.local>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Cyrus Daboo wrote:

>> 1. Pete is doing the write-up for ANNOTATE and will soon pass it on to
>> the IESG for IETF Last Call.
>> 2. Waiting for a rev of LISTEXT from Barry. Then Pete will write-up and
>> pass it on to the IESG for IETF Last Call.
>> 3. Waiting for a rev of COMPARATOR from Arnt. The current version of
>> IMAPi18n should be ready to go. Once we get the new draft of COMPARATOR,
>> Pete will issue a WG Last Call for both.
>>
>> Anything else?
>
> WG should review ANNOTATEMORE (aka METADATA).

Right. I would have no problems Last Calling it (officially or 
unofficially) in IMAPEXT and/or LEMONADE WGs.




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 k3ADfsb2048251; Mon, 10 Apr 2006 06:41:54 -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 k3ADfsKJ048250; Mon, 10 Apr 2006 06:41:54 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADfr6b048231 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:41:53 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 14:41:43 +0100
Message-ID: <443A608C.9040204@isode.com>
Date: Mon, 10 Apr 2006 14:41:32 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Cyrus Daboo <cyrus@daboo.name>
CC: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com> <71CD159CA68C102AE848B539@Cyrus-Daboo.local>
In-Reply-To: <71CD159CA68C102AE848B539@Cyrus-Daboo.local>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Cyrus Daboo wrote:

> Hi Alexey,
>
> --On April 9, 2006 5:45:04 PM +0100 Alexey Melnikov 
> <alexey.melnikov@isode.com> wrote:
>
>> However, if the client issues <LIST () "" %>, the server can't return
>> \NoSelect, as it was replaced by CHILDINFO. And the CHILDINFO extended
>> data can't be returned as per prohibition in section 3.1 (in -16), under
>> point 2 B):
>>            Note that the CHILDINFO
>>            extended data item can only be returned when the
>>            RECURSIVEMATCH selection option is specified.
>
> Where does it say that \NoSelect has been replaced?

I think I wasn't precise enough: it was only replaced for the case when 
SUBSCRIBED is specified:

>3.3  CHILDINFO extended data item
[...]
>   The LSUB command indicates this condition by using the "\NoSelect"
>   attribute, but the LIST (SUBSCRIBED) command MUST NOT do that, since
>   "\NoSelect" retains its original meaning here.  Further, the
>   CHILDINFO extended data item is more general, in that it can be used
>   with any extended set of selection criteria.

> I could not find any explicit statement to that effect. Given that 
> \NoSelect is one of the original LIST flags I would have thought it is 
> always returned.

Right. But \NonExistent has a stronger meaning, so it would be better in 
the described case.



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 k3ADaUbg048053; Mon, 10 Apr 2006 06:36:30 -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 k3ADaU1G048052; Mon, 10 Apr 2006 06:36:30 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADaTcN048046 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:36:30 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 0F2E8D478BF; Mon, 10 Apr 2006 09:36:29 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 09:36:10 -0400
X-Sasl-enc: 33nMzRfDifRtAmRwEj9sjPAQUnj75OcZ5UZxNuET2OzK 1144676170
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id 4B79838ED; Mon, 10 Apr 2006 09:36:08 -0400 (EDT)
Date: Mon, 10 Apr 2006 09:37:09 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Alexey Melnikov <alexey.melnikov@isode.com>, IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: Philip's issue with LIST-EXTENDED
Message-ID: <71CD159CA68C102AE848B539@Cyrus-Daboo.local>
In-Reply-To: <44393A10.1010006@isode.com>
References:  <44393A10.1010006@isode.com>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi Alexey,

--On April 9, 2006 5:45:04 PM +0100 Alexey Melnikov 
<alexey.melnikov@isode.com> wrote:

> However, if the client issues <LIST () "" %>, the server can't return
> \NoSelect, as it was replaced by CHILDINFO. And the CHILDINFO extended
> data can't be returned as per prohibition in section 3.1 (in -16), under
> point 2 B):
>            Note that the CHILDINFO
>            extended data item can only be returned when the
>            RECURSIVEMATCH selection option is specified.

Where does it say that \NoSelect has been replaced? I could not find any 
explicit statement to that effect. Given that \NoSelect is one of the 
original LIST flags I would have thought it is always returned.

-- 
Cyrus Daboo



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 k3ADOKAq047371; Mon, 10 Apr 2006 06:24:20 -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 k3ADOKZ1047370; Mon, 10 Apr 2006 06:24:20 -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 out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADOJFZ047364 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:24:19 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id CC68AD47533; Mon, 10 Apr 2006 09:24:17 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Mon, 10 Apr 2006 09:23:59 -0400
X-Sasl-enc: 3b/J4uyQvRdeIOBNTNePjJw0AJL8Y8PZlwsvsVsNYG/9 1144675439
Received: from [17.101.35.110] (unknown [17.101.35.110]) by www.fastmail.fm (Postfix) with ESMTP id 32E3F37FD; Mon, 10 Apr 2006 09:23:57 -0400 (EDT)
Date: Mon, 10 Apr 2006 09:24:57 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Pete Resnick <presnick@qualcomm.com>, IMAP Extensions <ietf-imapext@imc.org>
Subject: Re: To Do list
Message-ID: <A8DAD1A0C3FAFCDC4684FA74@Cyrus-Daboo.local>
In-Reply-To: <p07000c3fc05fb0b31b28@[216.43.25.67]>
References:  <p07000c3fc05fb0b31b28@[216.43.25.67]>
X-Mailer: Mulberry/4.0.4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>

Hi Pete,

--On April 10, 2006 2:04:51 AM -0500 Pete Resnick <presnick@qualcomm.com> 
wrote:

> 1. Pete is doing the write-up for ANNOTATE and will soon pass it on to
> the IESG for IETF Last Call.
> 2. Waiting for a rev of LISTEXT from Barry. Then Pete will write-up and
> pass it on to the IESG for IETF Last Call.
> 3. Waiting for a rev of COMPARATOR from Arnt. The current version of
> IMAPi18n should be ready to go. Once we get the new draft of COMPARATOR,
> Pete will issue a WG Last Call for both.
>
> Anything else?

WG should review ANNOTATEMORE (aka METADATA).

-- 
Cyrus Daboo



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 k3ADGpiJ046815; Mon, 10 Apr 2006 06:16:51 -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 k3ADGpHH046814; Mon, 10 Apr 2006 06:16:51 -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 rutherford.zen.co.uk (rutherford.zen.co.uk [212.23.3.142]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ADGofR046808 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 06:16:51 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1FSwG9-0002TI-JR; Mon, 10 Apr 2006 13:16:49 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id E0F29498003; Mon, 10 Apr 2006 14:23:28 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31995-02; Mon, 10 Apr 2006 14:23:19 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id AC7D5498002; Mon, 10 Apr 2006 14:23:17 +0100 (BST)
Date: Mon, 10 Apr 2006 14:16:37 +0100
Subject: Re: Comments about draft-ietf-imapext-i18n-06.txt
References: <p07000c3fc05fb0b31b28@[216.43.25.67]> <443A5391.3090109@isode.com>
In-Reply-To: <443A5391.3090109@isode.com>
MIME-Version: 1.0
Message-Id: <21242.1144674997.982052@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: <ietf-imapext@imc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Rutherford-IP: [217.155.137.60]
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>

On Mon Apr 10 13:46:09 2006, Alexey Melnikov wrote:
> 3). Also check the list of other issues brought up by Dave Cridland:
> <http://www.imc.org/ietf-imapext/mail-archive/msg03258.html>

(Numbers referring to points in my email)

1) [Allow LANGUAGE to have a list of languages in preference order as 
parameters] - Consensus in support.

2) [Decouple NAMESPACE and LANGUAGE] - Consensus seemed to be in 
support.

3) Resolution depends on comparator draft.

4) [Better comparator support] Unresolved.

I'm actually not hugely fussed on this. A proper solution to this 
requires a lot more work than this document could reasonably provide.

To put it another way, IMAP's SEARCH is sufficiently good that 
providing sufficiently better comparator support to make the effort 
worthwhile requires much more radical change.

5) [Unicode in identifiers] Resolved by Alexey's text

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k3ACxeed045450; Mon, 10 Apr 2006 05:59:40 -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 k3ACxebn045449; Mon, 10 Apr 2006 05:59:40 -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 pythagoras.zen.co.uk (pythagoras.zen.co.uk [212.23.3.140]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ACxd6d045435 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 05:59:39 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by pythagoras.zen.co.uk with esmtp (Exim 4.30) id 1FSvzV-0001T1-6g; Mon, 10 Apr 2006 12:59:37 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id 9ADE2498003; Mon, 10 Apr 2006 14:06:16 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31821-07; Mon, 10 Apr 2006 14:06:12 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id 133A7498002; Mon, 10 Apr 2006 14:06:11 +0100 (BST)
Date: Mon, 10 Apr 2006 13:59:31 +0100
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com> <2ggGuv29sIJ1KJSYbq168A.md5@libertango.oryx.com> <443A53B6.40702@isode.com>
In-Reply-To: <443A53B6.40702@isode.com>
MIME-Version: 1.0
Message-Id: <21242.1144673971.475359@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: <ietf-imapext@imc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Pythagoras-IP: [217.155.137.60]
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>

On Mon Apr 10 13:46:46 2006, Alexey Melnikov wrote:
> 
> Arnt Gulbrandsen wrote:
> 
>> Alexey Melnikov writes:
>> 
>>> So, my question is what do we do with this? The options I see are:
>>> 1). punt, let server and client implementors figure this out.
>>> 2). add the example and document the workaround as a proper way 
>>> to respond in this case
>>> 3). allow CHILDINFO to be returned on extended LISTs with no 
>>> RECURSIVEMATCH.
>>> 
>>> I personally don't like the option 1), as this issue is too 
>>> subtle. I prefer option 2 over 3.
>> 
>> By 2 you mean '* LIST (\nonexistent \haschildren) "/" "foo"'? Then 
>> I agree.
> 
> Yes.
> 
> 
It applies to <LIST (REMOTE) "" %> too. Basically to any combination 
of selection options where adding RECURSIVEMATCH would be illegal.

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k3AClGKL044984; Mon, 10 Apr 2006 05:47:16 -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 k3AClGRP044983; Mon, 10 Apr 2006 05:47:16 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3AClFs8044977 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 05:47:15 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 13:46:51 +0100
Message-ID: <443A53B6.40702@isode.com>
Date: Mon, 10 Apr 2006 13:46:46 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: ietf-imapext@imc.org
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com> <2ggGuv29sIJ1KJSYbq168A.md5@libertango.oryx.com>
In-Reply-To: <2ggGuv29sIJ1KJSYbq168A.md5@libertango.oryx.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Arnt Gulbrandsen wrote:

> Alexey Melnikov writes:
>
>> So, my question is what do we do with this? The options I see are:
>> 1). punt, let server and client implementors figure this out.
>> 2). add the example and document the workaround as a proper way to 
>> respond in this case
>> 3). allow CHILDINFO to be returned on extended LISTs with no 
>> RECURSIVEMATCH.
>>
>> I personally don't like the option 1), as this issue is too subtle. I 
>> prefer option 2 over 3.
>
> By 2 you mean '* LIST (\nonexistent \haschildren) "/" "foo"'? Then I 
> agree.

Yes.



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 k3ACkITD044970; Mon, 10 Apr 2006 05:46:18 -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 k3ACkI01044969; Mon, 10 Apr 2006 05:46:18 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ACkHaB044963 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 05:46:18 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 13:46:13 +0100
Message-ID: <443A5391.3090109@isode.com>
Date: Mon, 10 Apr 2006 13:46:09 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IMAP Extensions <ietf-imapext@imc.org>
Subject: Comments about draft-ietf-imapext-i18n-06.txt
References: <p07000c3fc05fb0b31b28@[216.43.25.67]>
In-Reply-To: <p07000c3fc05fb0b31b28@[216.43.25.67]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Pete Resnick wrote:

> 3. Waiting for a rev of COMPARATOR from Arnt. The current version of 
> IMAPi18n should be ready to go.

Not quite yet, a new revision is needed to address the following issues 
in -06:

1). Section 5.1 (Unicode Userids and Passwords) says:

>   When AUTHENTICATE is used, some servers may support userids and
>   passwords in Unicode [13]. However, such userids cannot be used as
>   email addresses,

Delete the rest of the paragraph. ACL RFC 4314 says that all usernames are in UTF-8.

> and at present also seem to be incompatible with
>   the current latest ACL drafts. Unless the ACL drafts resolve this,
>   server authors are cautioned against supporting ACL and unicode
>   userids simultaneously.

2). Did the WG reach any conclusion on adding a new SEARCH keyword for 
comparators?

3). Also check the list of other issues brought up by Dave Cridland:
<http://www.imc.org/ietf-imapext/mail-archive/msg03258.html>



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 k3ACaGFS044695; Mon, 10 Apr 2006 05:36:16 -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 k3ACaG10044694; Mon, 10 Apr 2006 05:36:16 -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 k3ACaC3o044686 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 05:36:15 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id B3CCA4AC32 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 14:36:11 +0200 (CEST)
Message-Id: <2ggGuv29sIJ1KJSYbq168A.md5@libertango.oryx.com>
Date: Mon, 10 Apr 2006 14:37:27 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-imapext@imc.org
Subject: Re: Philip's issue with LIST-EXTENDED
References: <44393A10.1010006@isode.com>
In-Reply-To: <44393A10.1010006@isode.com>
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>

Alexey Melnikov writes:
> So, my question is what do we do with this? The options I see are:
> 1). punt, let server and client implementors figure this out.
> 2). add the example and document the workaround as a proper way to 
> respond in this case
> 3). allow CHILDINFO to be returned on extended LISTs with no RECURSIVEMATCH.
>
> I personally don't like the option 1), as this issue is too subtle. I 
> prefer option 2 over 3.

By 2 you mean '* LIST (\nonexistent \haschildren) "/" "foo"'? Then I agree.

Arnt



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 k3ABEps0042398; Mon, 10 Apr 2006 04:14:51 -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 k3ABEphC042397; Mon, 10 Apr 2006 04:14:51 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3ABEmGM042382 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 04:14:49 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Mon, 10 Apr 2006 12:14:38 +0100
Message-ID: <44393A10.1010006@isode.com>
Date: Sun, 09 Apr 2006 17:45:04 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Philip's issue with LIST-EXTENDED
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Hi everyone,
After staring for 10 minutes at the jabber log and LISTEXT draft I 
finally understood what Philip was talking about.

Here is the issue:

Imagine that the server supports missing hierarchy members, like Cyrus 
does (i.e. a mailbox "foo/bar" can exists while "foo" doesn't).
If the client issues <LIST "" %>, the server would return:
      * LIST (\NoSelect) "/" "foo"

However, if the client issues <LIST () "" %>, the server can't return 
\NoSelect, as it was replaced by CHILDINFO. And the CHILDINFO extended 
data can't be returned as per prohibition in section 3.1 (in -16), under 
point 2 B):
           Note that the CHILDINFO
           extended data item can only be returned when the
           RECURSIVEMATCH selection option is specified.

This can be a bit unexpected for server implementors.
However there is a workaround for servers:
      * LIST (\NonExistent \HasChildren) "/" "foo"

So, my question is what do we do with this? The options I see are:
1). punt, let server and client implementors figure this out.
2). add the example and document the workaround as a proper way to 
respond in this case
3). allow CHILDINFO to be returned on extended LISTs with no RECURSIVEMATCH.

I personally don't like the option 1), as this issue is too subtle. I 
prefer option 2 over 3.




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 k3A751JD031131; Mon, 10 Apr 2006 00:05:01 -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 k3A751cP031130; Mon, 10 Apr 2006 00:05:01 -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 episteme-software.com (216-43-25-66.ip.mcleodusa.net [216.43.25.66]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3A750Vk031117 for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 00:05:00 -0700 (MST) (envelope-from presnick@qualcomm.com)
Received: from [216.43.25.67] (127.0.0.1) by episteme-software.com with ESMTP (EIMS X 3.3d21) for <ietf-imapext@imc.org>; Mon, 10 Apr 2006 02:04:52 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p07000c3fc05fb0b31b28@[216.43.25.67]>
X-Mailer: Eudora [Macintosh version 7.0a12]
Date: Mon, 10 Apr 2006 02:04:51 -0500
To: IMAP Extensions <ietf-imapext@imc.org>
From: Pete Resnick <presnick@qualcomm.com>
Subject: To Do list
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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>

Updates post-Dallas:

1. Pete is doing the write-up for ANNOTATE and will soon pass it on 
to the IESG for IETF Last Call.
2. Waiting for a rev of LISTEXT from Barry. Then Pete will write-up 
and pass it on to the IESG for IETF Last Call.
3. Waiting for a rev of COMPARATOR from Arnt. The current version of 
IMAPi18n should be ready to go. Once we get the new draft of 
COMPARATOR, Pete will issue a WG Last Call for both.

Anything else?

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



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 k35BlJUT016587; Wed, 5 Apr 2006 04:47:19 -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 k35BlJCv016586; Wed, 5 Apr 2006 04:47:19 -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 rutherford.zen.co.uk (rutherford.zen.co.uk [212.23.3.142]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k35BlIQ0016580 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 04:47:19 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1FR6Tk-0003UA-Ly; Wed, 05 Apr 2006 11:47:17 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id 8FE66498002; Wed,  5 Apr 2006 12:53:01 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28070-03; Wed, 5 Apr 2006 12:52:46 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id A237B498003; Wed,  5 Apr 2006 12:52:44 +0100 (BST)
Date: Wed, 05 Apr 2006 12:46:54 +0100
Subject: Re: postaddress, several addresses
References: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com> <4433971E.7010301@isode.com> <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
In-Reply-To: <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
MIME-Version: 1.0
Message-Id: <6711.1144237616.236199@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Cc: <ietf-imapext@imc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Rutherford-IP: [217.155.137.60]
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>

On Wed Apr  5 11:34:47 2006, Arnt Gulbrandsen wrote:
> 
> Alexey Melnikov writes:
> > If they are all equivalent - any.
> 
> Why "any" not "all"?

POSTADDRESS is just for a client to get an address to use for 
converting an FCC into a BCC, hence you only need a single address 
for that. I can't think of an alternate use for it at the moment, so 
I'm perfectly happy with just one address.

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k35BenXT016357; Wed, 5 Apr 2006 04:40:49 -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 k35BenGQ016356; Wed, 5 Apr 2006 04:40:49 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k35BelHb016350 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 04:40:48 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Wed, 5 Apr 2006 12:40:42 +0100
Message-ID: <4433ACAF.1010005@isode.com>
Date: Wed, 05 Apr 2006 12:40:31 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: ietf-imapext@imc.org
Subject: Re: postaddress, several addresses
References: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com>  <4433971E.7010301@isode.com> <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
In-Reply-To: <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Arnt Gulbrandsen wrote:

>Alexey Melnikov writes:
>  
>
>>If they are all equivalent - any.
>>    
>>
>Why "any" not "all"?
>  
>
What would the client do if the server returns multiple? Pick one at random?
I think the IMAP server is in a better position to decide which address 
to return.



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 k35AXwQ2013413; Wed, 5 Apr 2006 03:33:58 -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 k35AXwea013412; Wed, 5 Apr 2006 03:33:58 -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 k35AXvNJ013406 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 03:33:57 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 3AA084AC32 for <ietf-imapext@imc.org>; Wed,  5 Apr 2006 12:33:56 +0200 (CEST)
Message-Id: <k06SM630qB3J/Vr0N+mz4g.md5@libertango.oryx.com>
Date: Wed, 5 Apr 2006 12:34:47 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-imapext@imc.org
Subject: Re: postaddress, several addresses
References: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com> <4433971E.7010301@isode.com>
In-Reply-To: <4433971E.7010301@isode.com>
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>

Alexey Melnikov writes:
> If they are all equivalent - any.

Why "any" not "all"?

Arnt



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 k35A8dcs012264; Wed, 5 Apr 2006 03:08:39 -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 k35A8dUL012263; Wed, 5 Apr 2006 03:08:39 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k35A8caf012257 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 03:08:38 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Wed, 5 Apr 2006 11:08:32 +0100
Message-ID: <4433971E.7010301@isode.com>
Date: Wed, 05 Apr 2006 11:08:30 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: Re: postaddress, several addresses
References: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com>
In-Reply-To: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Arnt Gulbrandsen wrote:

> What if there are several addresses which will cause email to be 
> delivered to a mailbox? What should postaddress report?

If they are all equivalent - any.



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 k35A1Seq011557; Wed, 5 Apr 2006 03:01:28 -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 k35A1SIB011556; Wed, 5 Apr 2006 03:01:28 -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 k35A1QTr011550 for <ietf-imapext@imc.org>; Wed, 5 Apr 2006 03:01:27 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 9F7114AC32 for <ietf-imapext@imc.org>; Wed,  5 Apr 2006 12:01:25 +0200 (CEST)
Message-Id: <sRLiUeTANtKEnCoMVRJRQA.md5@libertango.oryx.com>
Date: Wed, 5 Apr 2006 12:02:16 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: postaddress, several addresses
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>

What if there are several addresses which will cause email to be 
delivered to a mailbox? What should postaddress report?

Arnt



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 k34LXJRI080017; Tue, 4 Apr 2006 14:33:19 -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 k34LXJ0Y080016; Tue, 4 Apr 2006 14:33:19 -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 rutherford.zen.co.uk (rutherford.zen.co.uk [212.23.3.142]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k34LXIce080010 for <ietf-imapext@IMC.ORG>; Tue, 4 Apr 2006 14:33:18 -0700 (MST) (envelope-from dave@cridland.net)
Received: from [217.155.137.60] (helo=turner.dave.cridland.net) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1FQt9I-0005Xm-3n; Tue, 04 Apr 2006 21:33:16 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by turner.dave.cridland.net (Postfix) with ESMTP id B43E7498003; Tue,  4 Apr 2006 22:38:57 +0100 (BST)
Received: from turner.dave.cridland.net ([127.0.0.1]) by localhost (turner.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25043-03; Tue, 4 Apr 2006 22:38:52 +0100 (BST)
Received: from peirce.dave.cridland.net (unknown [IPv6:2001:4bd0:2029:0:2e0:81ff:fe29:d16a]) by turner.dave.cridland.net (Postfix) with ESMTP id 700A5498002; Tue,  4 Apr 2006 22:38:50 +0100 (BST)
Date: Tue, 04 Apr 2006 22:33:08 +0100
Subject: Re: [Imap-protocol] authentication condition reporting extensions
References:  <Pine.WNT.4.65.0604041404240.4136@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To:  <Pine.WNT.4.65.0604041404240.4136@Tomobiki-Cho.CAC.Washington.EDU>
MIME-Version: 1.0
Message-Id: <4142.1144186388.432464@peirce.dave.cridland.net>
From: Dave Cridland <dave@cridland.net>
To: Mark Crispin <MRC@cac.washington.edu>
Cc: IMAP Extensions WG <ietf-imapext@imc.org>, IMAP Protocol Interest List <IMAP-Protocol@u.washington.edu>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dave.cridland.net
X-Originating-Rutherford-IP: [217.155.137.60]
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>

On Tue Apr  4 22:15:01 2006, Mark Crispin wrote:
> The conditions in question are:
>  . password will expire at such-and-such future time (or interval)
>  . password has expired
>  . account will expire at such-and-such future time (or interval)
>  . account has expired
>  . account has been disabled
> 
> 
That last is definitely a security issue, isn't it?

It'd be useful to be able to signal all the SASL codes that are in 
ACAP - TRANSITION-NEEDED, for instance, or AUTH-TOO-WEAK.

> Example (with both ALERT for compatibility and new response code)
> 
> * NO [EXPIRED http://imap.example.com/expired]
> tag NO [ALERT] Your account has expired, contact the help desk
> 
> Comments?

I'm not convinced all clients will understand untagged responses 
inside an AUTHENTICATE command - I think Alexey and Corby abandoned 
that syntax style for the RECONNECT work a while back at least partly 
due to that concern.

Also, I don't think that the alert is needed here - clients typically 
report the text of the error after a failure, so I suspect you're 
safe using the terminal response:

tag NO [EXPIRED http://imap.example.com/expired] Your account has 
expired, contact the help desk.

However, the better alternative would be to combine this proposal 
with an update to the AUTHENTICATE command which both explicitly 
added untagged responses during its execution, and supported both 
initial response and final success SASL data from the server. You 
could make it use literal8 instead of base64, too

Dave.
-- 
           You see things; and you say "Why?"
   But I dream things that never were; and I say "Why not?"
    - George Bernard Shaw



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 k34LD0LC079411; Tue, 4 Apr 2006 14:13:00 -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 k34LD0hi079410; Tue, 4 Apr 2006 14:13:00 -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 mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k34LCw12079403 for <ietf-imapext@IMC.ORG>; Tue, 4 Apr 2006 14:12:59 -0700 (MST) (envelope-from MRC@CAC.Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k34LCwbH005688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Apr 2006 14:12:58 -0700
X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k34LCv0b022004 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 4 Apr 2006 14:12:57 -0700
Date: Tue, 4 Apr 2006 14:15:01 -0700 (Pacific Daylight Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: IMAP Protocol Interest List <IMAP-Protocol@U.Washington.EDU>
cc: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: authentication condition reporting extensions
Message-ID: <Pine.WNT.4.65.0604041404240.4136@Tomobiki-Cho.CAC.Washington.EDU>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 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>

The question has come up about possible extensions to what may optionally 
be reported by the server due to authentication conditions.  Obviously, 
there is substantial security sensitivity here.

The conditions in question are:
  . password will expire at such-and-such future time (or interval)
  . password has expired
  . account will expire at such-and-such future time (or interval)
  . account has expired
  . account has been disabled

It is desired to include a URL that will provide more information.

Currently, the only way to do this is with ALERT, but perhaps it would be 
useful if the client could know about some of these.

Example (with both ALERT for compatibility and new response code)

* NO [EXPIRED http://imap.example.com/expired]
tag NO [ALERT] Your account has expired, contact the help desk

Comments?

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.



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 k34AhBGx052989; Tue, 4 Apr 2006 03:43:11 -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 k34AhBqU052988; Tue, 4 Apr 2006 03:43:11 -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 dmgw.movial.fi (dmgw.movial.fi [62.236.91.5]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k34Ah91F052961 for <ietf-imapext@imc.org>; Tue, 4 Apr 2006 03:43:09 -0700 (MST) (envelope-from tss@iki.fi)
Received: from movial.fi (hellmail.movial.fi [62.236.91.6]) by dmgw.movial.fi (Postfix) with ESMTP id 22CDD231 for <ietf-imapext@imc.org>; Tue,  4 Apr 2006 13:43:02 +0300 (EEST)
Received: from localhost (hellmail.movial.fi [127.0.0.1]) by movial.fi (Postfix) with ESMTP id 13BE680068 for <ietf-imapext@imc.org>; Tue,  4 Apr 2006 13:43:02 +0300 (EEST)
Received: from movial.fi ([127.0.0.1]) by localhost (hellmail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01203-10 for <ietf-imapext@imc.org>; Tue, 4 Apr 2006 13:43:01 +0300 (EEST)
Received: from sd022.hel.movial.fi (sd022.hel.movial.fi [172.17.49.22]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by movial.fi (Postfix) with ESMTP id D2E8680063 for <ietf-imapext@imc.org>; Tue,  4 Apr 2006 13:43:01 +0300 (EEST)
Subject: Re: More on LISTEXT
From: Timo Sirainen <tss@iki.fi>
To: ietf-imapext@imc.org
In-Reply-To: <44316AA9.8040505@watson.ibm.com>
References: <68E7DF4660B140AC8B212B23@ninevah.local> <44316AA9.8040505@watson.ibm.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-OXTMHFGytnYb/AVupNXB"
Date: Tue, 04 Apr 2006 13:43:01 +0300
Message-Id: <1144147381.17923.13.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at movial.fi
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>

--=-OXTMHFGytnYb/AVupNXB
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2006-04-03 at 14:34 -0400, Barry Leiba wrote:
> > 1) Leave things as they are - getting annotations will result in gettin=
g=20
> > the standard flags all over again.
> >=20
> > 2) Add a new STDFLAGs return option such that if a RETURN is specified,=
=20
> > then standard flags are only returned if STDFLAG is present as one of=20
> > the return options. If there is no return option, then the normal=20
> > behaviour occurs.
> >=20
> > 3) Add a new NOSTDFLAGS return option such that if specified in RETURN,=
=20
> > the standard flags are not returned.
..
> I would be willing to add STDFLAGS if it's the case that extended LIST=20
> does NOT normally return them, and so we *always* have to ask for them=20
> explicitly.  But I don't like it; I'd rather behave more like the=20
> base-doc LIST command in this regard.

Actually this is how I originally read the 2) part. Never returning
flags unless asked sounds good to me..

> I will be happy to add NOSTDFLAGS (or some other such text) that=20
> EXPLICITLY tells LIST to deviate from the normal behaviour.

I'm not really against this either.

--=-OXTMHFGytnYb/AVupNXB
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBEMk21Q95cgkr2Z40RAlzlAJ48nu0tu30Z9b3X/a5j/TBLrf4BOACeI2Tr
RhGpLQIUKTpZqOKpnd/xTGg=
=xPEv
-----END PGP SIGNATURE-----

--=-OXTMHFGytnYb/AVupNXB--



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 k33IYQ2v069832; Mon, 3 Apr 2006 11:34:26 -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 k33IYQVp069831; Mon, 3 Apr 2006 11:34:26 -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 igw2.watson.ibm.com (igw2.watson.ibm.com [129.34.20.6]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k33IYP2p069824 for <ietf-imapext@imc.org>; Mon, 3 Apr 2006 11:34:26 -0700 (MST) (envelope-from leiba@watson.ibm.com)
Received: from sp1n293en1.watson.ibm.com (sp1n293en1.watson.ibm.com [129.34.20.41]) by igw2.watson.ibm.com (8.12.11.20060308/8.13.1/8.13.1-2005-04-25 igw) with ESMTP id k33IYcMi020750 for <ietf-imapext@imc.org>; Mon, 3 Apr 2006 14:34:38 -0400
Received: from sp1n293en1.watson.ibm.com (localhost [127.0.0.1]) by sp1n293en1.watson.ibm.com (8.11.7-20030924/8.11.7/01-14-2004_2) with ESMTP id k33IYJh40806 for <ietf-imapext@imc.org>; Mon, 3 Apr 2006 14:34:19 -0400
Received: from mars (mars.watson.ibm.com [9.2.40.64]) by sp1n293en1.watson.ibm.com (8.11.7-20030924/8.11.7/01-14-2004_1) with ESMTP id k33IYIB88028 for <ietf-imapext@imc.org>; Mon, 3 Apr 2006 14:34:18 -0400
Received: from saturn ([9.2.43.127]) by mars.watson.ibm.com (IMF.2005.07.16.1050.haw) with SMTP ID IMFd1144089258.4650; Mon, 03 Apr 2006 14:34:18 -0400
Message-ID: <44316AA9.8040505@watson.ibm.com>
Date: Mon, 03 Apr 2006 14:34:17 -0400
From: Barry Leiba <leiba@watson.ibm.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: ietf-imapext@imc.org
Subject: Re: More on LISTEXT
References: <68E7DF4660B140AC8B212B23@ninevah.local>
In-Reply-To: <68E7DF4660B140AC8B212B23@ninevah.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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>

> 1) Leave things as they are - getting annotations will result in getting 
> the standard flags all over again.
> 
> 2) Add a new STDFLAGs return option such that if a RETURN is specified, 
> then standard flags are only returned if STDFLAG is present as one of 
> the return options. If there is no return option, then the normal 
> behaviour occurs.
> 
> 3) Add a new NOSTDFLAGS return option such that if specified in RETURN, 
> the standard flags are not returned.

I AM VERY STRONGLY AGAINST 2.
As Dave has already pointed out, this is a specification nightmare, 
giving all return options the side-effect of turning off the default 
STDFLAGS, and requiring that it be specified.

As a document editor, I WILL NOT put it in unless the WG chair (Hi 
Pete!) declares consensus for it.

I would be willing to add STDFLAGS if it's the case that extended LIST 
does NOT normally return them, and so we *always* have to ask for them 
explicitly.  But I don't like it; I'd rather behave more like the 
base-doc LIST command in this regard.

I will be happy to add NOSTDFLAGS (or some other such text) that 
EXPLICITLY tells LIST to deviate from the normal behaviour.


I will point out a couple of things:

1. As Dave said, NOSTDFLAGS *could* be added in an extension.

2. STDFLAGS could be added in the METADATA spec, setting things up so 
that the METADATA return option is the only one that cancels the default 
STDFLAGS return, and so STDFLAGS is needed to explicitly put it back.  I 
don't like that approach, but since it wouldn't affect LISTEXT I 
wouldn't care about it just now.  :-)


For now, I'm doing nothing about it in the LISTEXT spec, until we decide 
what the consensus is.

Barry

--
Barry Leiba, Pervasive Computing Technology  (leiba@watson.ibm.com)
http://www.research.ibm.com/people/l/leiba
http://www.research.ibm.com/spam



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 k31JH3g2041944; Sat, 1 Apr 2006 12:17:03 -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 k31JH3Dr041943; Sat, 1 Apr 2006 12:17:03 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k31JH2M1041937 for <ietf-imapext@imc.org>; Sat, 1 Apr 2006 12:17:03 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com via TCP (submission) with ESMTPA; Sat, 1 Apr 2006 20:16:55 +0100
Message-ID: <442ED1A4.8070606@isode.com>
Date: Sat, 01 Apr 2006 11:16:52 -0800
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Ken Murchison <murch@andrew.cmu.edu>
CC: ietf-imapext@imc.org
Subject: Re: CONDSTORE
References: <4429A882.7010609@andrew.cmu.edu> <442D3DFE.20401@isode.com> <442D708F.9090707@andrew.cmu.edu>
In-Reply-To: <442D708F.9090707@andrew.cmu.edu>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Ken Murchison wrote:

> Alexey Melnikov wrote:
>
>> Ken Murchison wrote:
>
>>> And what should be done for STATUS HIGHESTMODSEQ when the mailbox 
>>> doesn't support CONDSTORE?  I assume that the server should just 
>>> ignore the HIGHESTMODSEQ status item, in the same way that it will 
>>> have to ignore the SELECT/EXAMINE CONDSTORE parameter.
>>
>> Right.
>
> Hmm, the ABNF for the STATUS response requires at least one 
> status-att.  So what should we do for:
>
> a STATUS mailbox (HIGHESTMODSEQ)
>
> Return a HIGHESTMODSEQ of zero, or don't return * STATUS for the 
> mailbox?  I'm assuming the latter.

The latter, but I guess the document can be updated to say that the 
former means "modseq are not supported for the mailbox".




