IMAP4 Extension to SEARCH Command for Controlling What Kind of Information Is Returned
draft-melnikov-imap-search-ret-03

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'IMAP4 extension to SEARCH command for 
         controlling what kind of information is returned' to Proposed 
         Standard 

The IESG has approved the following document:

- 'IMAP4 extension to SEARCH command for controlling what kind of 
   information is returned '
   <draft-melnikov-imap-search-ret-04.txt> as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Ted Hardie.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-melnikov-imap-search-ret-04.txt

Ballot Text

Technical Summary
 
 This document extends IMAP  SEARCH and UID SEARCH
 commands with several result options, which can control what kind
 of information is returned. The following result options are
 defined: minimal value, maximal value, all found messages and
  number of found messages.
 
Working Group Summary
 
This is the product of an individual submitter.  It has been discussed
on several IMAP-related working group lists, however, and there seems
to be support for the work. Ongoing work in Lemonade may depend
on this draft.

Protocol Quality
 
This draft was reviewed for the IESG by Ted Hardie.

Note to RFC Editor
 

OLD:
  In general case IMAP SEARCH/UID SEARCH command can be CPU and/or IO
  intensive, so some sites/implementations even disable it entirely.

NEW:
  In the general case the IMAP SEARCH/UID SEARCH commands can be CPU
and/or IO intensive, and are seen by some as a potential attack point for
DoS attacks, so some sites/implementations even disable it entirely.

RFC Editor Note