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

[Ballot comment]
Gen-ART reviewer Avri Doria said:

This document is only understandable when taken with several other
documents.  The form of reference it uses relies on strong familiarity
with the normative references.  This may be fine given the specialized
audience but it was a difficult draft to read.

The IANA considerations seem sparse as it does not explcitly list the
parameters for which values are needed.

BC says:
 
  X-DRAFT-I02-ESEARCH < < fix before publication > >

What fix is needed? Is IANA requested to provide a different value?

5.  Security Considerations
 
  In general case IMAP SEARCH/UID SEARCH command can be CPU and/or IO
  intensive, so some sites/implementations even disable it entirely.
  This is quite unfortunate, as SEARCH command is one of the best
  examples demonstrating IMAP advantage over POP3.
  The ALL and COUNT return options don't change how SEARCH is working
  internally, they only change how information about found messages
  is returned. MIN and MAX SEARCH result options described in this
  document can lighten load on IMAP servers, which chose to optimize
  SEARCHes containing only one or both of them.

What on earth has that to do with security?

[Ballot comment]
Gen-ART reviewer Avri Doria said:

This document is only understandable when taken with several other
documents.  The form of reference it uses relies on strong familiarity
with the normative references.  This may be fine given the specialized
audience but it was a difficult draft to read.

The IANA considerations seem sparse as it does not explcitly list the
parameters for which values are needed.

BC says:
 
  X-DRAFT-I02-ESEARCH <>

What fix is needed? Is IANA requested to provide a different value?

5.  Security Considerations
 
  In general case IMAP SEARCH/UID SEARCH command can be CPU and/or IO
  intensive, so some sites/implementations even disable it entirely.
  This is quite unfortunate, as SEARCH command is one of the best
  examples demonstrating IMAP advantage over POP3.
  The ALL and COUNT return options don't change how SEARCH is working
  internally, they only change how information about found messages
  is returned. MIN and MAX SEARCH result options described in this
  document can lighten load on IMAP servers, which chose to optimize
  SEARCHes containing only one or both of them.

What on earth has that to do with security?

IANA Last Call Comment:

Upon approval of this document IANA will add a single name to the IMAP4
Capabilities Registry

ESEARCH

This registry is located at:

http://www.iana.org/assignments/imap4-capabilities

IANA understands that this is the only IANA Action required upon approval of
this document.