Re: [lemonade] New draft: SEARCH return options

Alexey Melnikov <Alexey.Melnikov@isode.com> Mon, 14 February 2005 19:44 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j1EJil9R049164; Mon, 14 Feb 2005 11:44:47 -0800 (PST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j1EJilJx049163; Mon, 14 Feb 2005 11:44:47 -0800 (PST)
X-Authentication-Warning: above.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 above.proper.com (8.12.11/8.12.9) with ESMTP id j1EJifVT049144 for <ietf-imapext@imc.org>; Mon, 14 Feb 2005 11:44:44 -0800 (PST) (envelope-from Alexey.Melnikov@isode.com)
Received: from [172.16.1.198] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (internal) with ESMTPA; Mon, 14 Feb 2005 19:44:15 +0000
Message-ID: <4210FF8E.8000302@isode.com>
Date: Mon, 14 Feb 2005 19:44:14 +0000
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: Michael.Wener@nokia.com
CC: ietf-imapext@imc.org
Subject: Re: [lemonade] New draft: SEARCH return options
References: <225A4E03D0EE5245A5C5F7E7B7C1F27A016D3D21@daebe005.americas.nokia.com>
In-Reply-To: <225A4E03D0EE5245A5C5F7E7B7C1F27A016D3D21@daebe005.americas.nokia.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>

Michael.Wener@nokia.com wrote:

>Comments:
>I don't understand what the anticipated use of RETURN () would be?
>  
>
This is a hook for the SEARCHRES extension 
(draft-melnikov-imap-search-res-01.txt).

>There should be some Normative text stipulating that SEARCH and 
>ESEARCH are mutually exclusive responses.
>  
>
The document already says "MUST send  ESEARCH when a return option is 
specified". Do you think this is not sufficient?