
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7SBvcT26128 for ietf-imapext-bks; Wed, 28 Aug 2002 04:57:38 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7SBva226124 for <ietf-imapext@imc.org>; Wed, 28 Aug 2002 04:57:37 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24702; Wed, 28 Aug 2002 07:56:07 -0400 (EDT)
Message-Id: <200208281156.HAA24702@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ietf-imapext@imc.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-cridland-imap-quota-00.txt
Date: Wed, 28 Aug 2002 07:56:07 -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.


	Title		: IMAP4rev1 QUOTA Extension
	Author(s)	: D. Cridland, A. Melnikov
	Filename	: draft-cridland-imap-quota-00.txt
	Pages		: 20
	Date		: 2002-8-27
	
The QUOTA extension of the Internet Message Access Protocol IMAP4 [2]
permits administrative limits on resource usage (quotas) to be
manipulated through the IMAP protocol.
This memo replaces RFC2087 [4], but attempts to remain backwards
compatible whenever possible.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cridland-imap-quota-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-cridland-imap-quota-00.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-cridland-imap-quota-00.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:	<2002-8-27144552.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-cridland-imap-quota-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-cridland-imap-quota-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-8-27144552.I-D@ietf.org>

--OtherAccess--

--NextPart--




Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7S04jx06754 for ietf-imapext-bks; Tue, 27 Aug 2002 17:04:45 -0700 (PDT)
Received: from [165.227.249.18] (165-227-249-20.client.dsl.net [165.227.249.20]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7RNcH205470; Tue, 27 Aug 2002 16:38:17 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05111a48b991bcfec5f8@[165.227.249.18]>
Date: Tue, 27 Aug 2002 16:38:17 -0700
To: (many IETF mailing lists)
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Nomcom call for volunteers
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>

Forwarded for Phil Roberts <PRoberts@MEGISTO.com>:

The members of the IESG and IAB and the IETF chair are selected
by a nominations committee made up of volunteers from the
IETF community.  The nominations committee is now in the process
of being formed and volunteers are being accepted until Sep 6.
Please see (http://www.ietf.org/nomcom/msg19765.html)
for information if you are interested in volunteering
to be on the nominations committee.


Received: by above.proper.com (8.11.6/8.11.3) id g7LAAps28799 for ietf-imapext-bks; Wed, 21 Aug 2002 03:10:51 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7LAAo228794 for <ietf-imapext@imc.org>; Wed, 21 Aug 2002 03:10:50 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KLJAKSTD4W0001B1@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf-imapext@imc.org; Wed, 21 Aug 2002 03:10:49 -0700 (PDT)
Date: Wed, 21 Aug 2002 03:09:14 -0700 (PDT)
From: ned+imapext@INNOSOFT.COM
Subject: IESG review of draft-nerenberg-imap-binary-06.txt
In-reply-to: "Your message dated Mon, 21 Jan 2002 07:43:16 -0500" <200201211243.HAA07397@ietf.org>
To: ietf-imapext@imc.org, lyndon@atg.aciworldwide.com
Cc: ned.freed@mrochek.com, paf@cisco.com
Message-id: <01KLJM77PG6G0001B1@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
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>

IESG review produced the following comments on the document:

(0) This document does not contain the copyright boilerplate
    specified in RFC 2026 section 10.4.

(1) The ABNF uses underscores, which are not allowed. I suggest 
    hyphens.

(2) The "msg-att" rule uses the # repeat, which is defined in RFC 822
     but not in ABNF and is not used in IMAP4rev1 which this is 
     extending. However, it only uses it in copying some of IMAP4rev1, 
     which has since changed to be easier to extend. So, the comments
           ;; Append BINARY and BINARY.SIZE to <msg_att>.
           ;; This is not meant to be an absolute list;
           ;; it was done this way due to ABNF syntax
           ;; restrictions.
     are no longer correct, and this can be done by simply doing
             msg-att-static =/ "BINARY" section_number ["<" number ">"] SP
            (nstring / literal8) / "BINARY.SIZE" section_number SP number) ")"

(3) The text description, e.g. BINARY.SIZE[<section>]
    seem to imply that the section number is enclosed in brackets;
    however the ABNF does not include brackets and requires
    e.g. BINARY.SIZE1 . Further, the "section_number" definition
    of this grammar is exactly the same as IMAP4rev1's "section-part";
    perhaps the right thing is for this document to have
    section-number = "[" [section-part] "]" (assuming that 
     a) the section ID is allowed to be empty, as is true in 
                IMAP4rev1's ABNF, and
     b) the existing "section" rule in the IMAP4rev1 is not appropriate,
           perhaps due to its inclusion of "HEADER", "HEADER.FIELDS" and 
           "TEXT" pseudo-sections.)

(4) The reference for [ABNF] is missing from section 9.

(5) The document is formatted with hyphenation, which presumably the
    RFC-Editor could handle but if it has to be respun for these 
    changes it'd be nice to turn off hyphenation.

(6) Change Security Considerations to:

    There are no known additional security issues with this
    extension beyond those described by the base protocol in
    [IMAP4rev1].

(7) References need to be separated into normative and informative groups.

That's it!

				Ned


Received: by above.proper.com (8.11.6/8.11.3) id g7JLKII26271 for ietf-imapext-bks; Mon, 19 Aug 2002 14:20:18 -0700 (PDT)
Received: from lin1.andrew.cmu.edu (LIN1.andrew.cmu.edu [128.2.6.59]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7JLKGn26266 for <ietf-imapext@imc.org>; Mon, 19 Aug 2002 14:20:16 -0700 (PDT)
Received: from GOBO.andrew.cmu.edu (GOBO.andrew.cmu.edu [128.2.120.172]) (user=rjs3 mech=KERBEROS_V4 (0 bits)) by lin1.andrew.cmu.edu (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id g7JLKH1T027693; Mon, 19 Aug 2002 17:20:17 -0400
Date: Mon, 19 Aug 2002 17:20:17 -0400 (EDT)
From: Rob Siemborski <rjs3@andrew.cmu.edu>
To: ietf-imapext@imc.org, <daboo@cyrusoft.com>
Subject: annotatemore question
Message-ID: <Pine.LNX.4.44L-027.0208191719500.8214-100000@gobo.andrew.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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 Cyrus,

I had a quick question/clarification for ANNOTATEMORE.  It is unclear if
multiple untagged ANNOTATION responses allowed before the tagged OK
response (like fetch) or if a server must do a single large ANNOTATION
response.

Since it can be intensive for a server to build up a large result
(especially if it has to build a single response to do so).

I'd contend that multiple annotation responses are allowed (say, one per
entry, similar to how FETCH works), such that:

a GETANNOTATION ("/mailbox/{user.%}/comment" "/server/motd") "*"

might return (lines broken for clarity):

* ANNOTATION "/mailbox/{user.leg}/comment" ("value.shared" "foo"
  "size.shared" "3" )
* ANNOTATION "/mailbox/{user.rjs3}/comment" ("value.shared" "bar"
  "size.shared" "3")
* ANNOTATION "/server/motd" ("value.shared" "the message of the day")
a OK Completed

-Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski | Andrew Systems Group * Research Systems Programmer
PGP:0x5CE32FCC | Cyert Hall 207 * rjs3@andrew.cmu.edu * 412.268.7456
-----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS/IT/CM/PA d- s+: a-- C++++$ UBLS++++$ P+++$ L++(+++) E W+ N- o? K-
w O- M-- V-- PS+ PE++ Y+ PGP+ t+@ 5+++ R@ tv-- b++ DI+++ G e h r y?
------END GEEK CODE BLOCK-----






Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7GApEB28900 for ietf-imapext-bks; Fri, 16 Aug 2002 03:51:14 -0700 (PDT)
Received: from melkebalanse.gulbrandsen.priv.no (dialup-del-203.94.242.44.bol.net.in [203.94.242.44]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7GAp7w28885 for <ietf-imapext@imc.org>; Fri, 16 Aug 2002 03:51:07 -0700 (PDT)
Message-ID: <al75qo1L6j20hWEAeXdkGw.md5@melkebalanse.gulbrandsen.priv.no>
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Frank McShane <FMcS@dataconnection.com>
Subject: Re: status-counters extension
Cc: ietf-imapext@imc.org, vpim@lists.neystadt.org
References: <5B979B23E3B7D511B59100065B04D5C84DF24D@kenton.datcon.co.uk>
In-Reply-To: <5B979B23E3B7D511B59100065B04D5C84DF24D@kenton.datcon.co.uk>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
Date: Fri, 16 Aug 2002 16:21:15 +0530
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>

It doesn't sound like such a big deal.

The SEARCH volume can be a problem for the IMAP server while processing 
it, for the network while transmitting the results, for the TUI while 
processing the results, or for a combination. I'll deal with them in 
order, using a 200,000-message mailbox and a search with 60,000 results 
(30% of the messages). A bit on the high side, to make sure any 
scalability issues show up well.

The server:

Any server that's usable on such a big mailbox surely won't be using the 
naive search strategies of most current-day servers. It has to use some 
kind of indexing, or the server would be run into the ground well 
before 200,000 messages.

If it uses smartish indexing, searching 200,000 records isn't hard or 
slow. Google does subsecond searches on 2,000,000,000 records - ten 
thousand times as many.

The network:

That search result is almost 360k of data. Not very much for a 100Mbps 
ethernet. Very much for a modem connection, of course. For such a 
mailbox, "put the TUI and the IMAP server in the same room, preferably 
on the same switch" becomes a design imperative. Not onerous IMO.

The TUI:

Parsing 350k of data and storing it in a 240k array shouldn't be hard. 
RAM is cheap, and after all we're not talking about the common case. If 
the worst case doesn't mean more than a fraction of a second delay and 
having to store 240k instead of 2k, I think you're really very lucky ;)

--Arnt


Received: by above.proper.com (8.11.6/8.11.3) id g7GA80R20322 for ietf-imapext-bks; Fri, 16 Aug 2002 03:08:00 -0700 (PDT)
Received: from miles.dataconnection.com (smtp2.dataconnection.com [192.91.191.8]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7GA7ww20313 for <ietf-imapext@imc.org>; Fri, 16 Aug 2002 03:07:59 -0700 (PDT)
Received: by miles.datcon.co.uk with Internet Mail Service (5.5.2656.59) id <PTR7DKP0>; Fri, 16 Aug 2002 11:07:43 +0100
Message-ID: <5B979B23E3B7D511B59100065B04D5C84DF24D@kenton.datcon.co.uk>
From: Frank McShane <FMcS@dataconnection.com>
To: "'vpim@lists.neystadt.org'" <vpim@lists.neystadt.org>
Cc: "'ietf-imapext@imc.org'" <ietf-imapext@imc.org>
Subject: status-counters extension
Date: Fri, 16 Aug 2002 11:07:44 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain; charset="iso-8859-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>

I have been following the discussion on the status-counters extension.

I can see that the use of this function will give a scalable way to query
the contents of the mailbox,
and is extremely useful when you need to get a greeting message out through
the TUI as quickly as possible.

After the greeting message, the user might select to listen to their voice
messages.
To find the voice messages in the mailbox, the TUI will have to revert to
using SEARCH commands to find a list of the messages of interest.

That will be fine for small mailboxes (and maybe even for large ones) but
does still mean that the amount of data flowing across the wire is linear
with the number of messages.  So, at least in theory, that's a possible
scalability issue too - if only once we're dealing with mailboxes with tens
of thousands of messages in them.

I was wondering if anyone has considered whether this needs a scalable
solution also.
E.g. would it be useful to extend the fetch command to get the first message
of a particular type, then the second, then the third, and so on?

Or is it clear to everyone that this isn't really a real-world case :-)

Thanks

Frank


Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7SBvcT26128 for ietf-imapext-bks; Wed, 28 Aug 2002 04:57:38 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7SBva226124 for <ietf-imapext@imc.org>; Wed, 28 Aug 2002 04:57:37 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24702; Wed, 28 Aug 2002 07:56:07 -0400 (EDT)
Message-Id: <200208281156.HAA24702@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ietf-imapext@imc.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-cridland-imap-quota-00.txt
Date: Wed, 28 Aug 2002 07:56:07 -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.


	Title		: IMAP4rev1 QUOTA Extension
	Author(s)	: D. Cridland, A. Melnikov
	Filename	: draft-cridland-imap-quota-00.txt
	Pages		: 20
	Date		: 2002-8-27
	
The QUOTA extension of the Internet Message Access Protocol IMAP4 [2]
permits administrative limits on resource usage (quotas) to be
manipulated through the IMAP protocol.
This memo replaces RFC2087 [4], but attempts to remain backwards
compatible whenever possible.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cridland-imap-quota-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-cridland-imap-quota-00.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-cridland-imap-quota-00.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:	<2002-8-27144552.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-cridland-imap-quota-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-cridland-imap-quota-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-8-27144552.I-D@ietf.org>

--OtherAccess--

--NextPart--




Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7S04jx06754 for ietf-imapext-bks; Tue, 27 Aug 2002 17:04:45 -0700 (PDT)
Received: from [165.227.249.18] (165-227-249-20.client.dsl.net [165.227.249.20]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7RNcH205470; Tue, 27 Aug 2002 16:38:17 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05111a48b991bcfec5f8@[165.227.249.18]>
Date: Tue, 27 Aug 2002 16:38:17 -0700
To: (many IETF mailing lists)
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Nomcom call for volunteers
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>

Forwarded for Phil Roberts <PRoberts@MEGISTO.com>:

The members of the IESG and IAB and the IETF chair are selected
by a nominations committee made up of volunteers from the
IETF community.  The nominations committee is now in the process
of being formed and volunteers are being accepted until Sep 6.
Please see (http://www.ietf.org/nomcom/msg19765.html)
for information if you are interested in volunteering
to be on the nominations committee.


Received: by above.proper.com (8.11.6/8.11.3) id g7LAAps28799 for ietf-imapext-bks; Wed, 21 Aug 2002 03:10:51 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7LAAo228794 for <ietf-imapext@imc.org>; Wed, 21 Aug 2002 03:10:50 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KLJAKSTD4W0001B1@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf-imapext@imc.org; Wed, 21 Aug 2002 03:10:49 -0700 (PDT)
Date: Wed, 21 Aug 2002 03:09:14 -0700 (PDT)
From: ned+imapext@INNOSOFT.COM
Subject: IESG review of draft-nerenberg-imap-binary-06.txt
In-reply-to: "Your message dated Mon, 21 Jan 2002 07:43:16 -0500" <200201211243.HAA07397@ietf.org>
To: ietf-imapext@imc.org, lyndon@atg.aciworldwide.com
Cc: ned.freed@mrochek.com, paf@cisco.com
Message-id: <01KLJM77PG6G0001B1@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
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>

IESG review produced the following comments on the document:

(0) This document does not contain the copyright boilerplate
    specified in RFC 2026 section 10.4.

(1) The ABNF uses underscores, which are not allowed. I suggest 
    hyphens.

(2) The "msg-att" rule uses the # repeat, which is defined in RFC 822
     but not in ABNF and is not used in IMAP4rev1 which this is 
     extending. However, it only uses it in copying some of IMAP4rev1, 
     which has since changed to be easier to extend. So, the comments
           ;; Append BINARY and BINARY.SIZE to <msg_att>.
           ;; This is not meant to be an absolute list;
           ;; it was done this way due to ABNF syntax
           ;; restrictions.
     are no longer correct, and this can be done by simply doing
             msg-att-static =/ "BINARY" section_number ["<" number ">"] SP
            (nstring / literal8) / "BINARY.SIZE" section_number SP number) ")"

(3) The text description, e.g. BINARY.SIZE[<section>]
    seem to imply that the section number is enclosed in brackets;
    however the ABNF does not include brackets and requires
    e.g. BINARY.SIZE1 . Further, the "section_number" definition
    of this grammar is exactly the same as IMAP4rev1's "section-part";
    perhaps the right thing is for this document to have
    section-number = "[" [section-part] "]" (assuming that 
     a) the section ID is allowed to be empty, as is true in 
                IMAP4rev1's ABNF, and
     b) the existing "section" rule in the IMAP4rev1 is not appropriate,
           perhaps due to its inclusion of "HEADER", "HEADER.FIELDS" and 
           "TEXT" pseudo-sections.)

(4) The reference for [ABNF] is missing from section 9.

(5) The document is formatted with hyphenation, which presumably the
    RFC-Editor could handle but if it has to be respun for these 
    changes it'd be nice to turn off hyphenation.

(6) Change Security Considerations to:

    There are no known additional security issues with this
    extension beyond those described by the base protocol in
    [IMAP4rev1].

(7) References need to be separated into normative and informative groups.

That's it!

				Ned


Received: by above.proper.com (8.11.6/8.11.3) id g7JLKII26271 for ietf-imapext-bks; Mon, 19 Aug 2002 14:20:18 -0700 (PDT)
Received: from lin1.andrew.cmu.edu (LIN1.andrew.cmu.edu [128.2.6.59]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7JLKGn26266 for <ietf-imapext@imc.org>; Mon, 19 Aug 2002 14:20:16 -0700 (PDT)
Received: from GOBO.andrew.cmu.edu (GOBO.andrew.cmu.edu [128.2.120.172]) (user=rjs3 mech=KERBEROS_V4 (0 bits)) by lin1.andrew.cmu.edu (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id g7JLKH1T027693; Mon, 19 Aug 2002 17:20:17 -0400
Date: Mon, 19 Aug 2002 17:20:17 -0400 (EDT)
From: Rob Siemborski <rjs3@andrew.cmu.edu>
To: ietf-imapext@imc.org, <daboo@cyrusoft.com>
Subject: annotatemore question
Message-ID: <Pine.LNX.4.44L-027.0208191719500.8214-100000@gobo.andrew.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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 Cyrus,

I had a quick question/clarification for ANNOTATEMORE.  It is unclear if
multiple untagged ANNOTATION responses allowed before the tagged OK
response (like fetch) or if a server must do a single large ANNOTATION
response.

Since it can be intensive for a server to build up a large result
(especially if it has to build a single response to do so).

I'd contend that multiple annotation responses are allowed (say, one per
entry, similar to how FETCH works), such that:

a GETANNOTATION ("/mailbox/{user.%}/comment" "/server/motd") "*"

might return (lines broken for clarity):

* ANNOTATION "/mailbox/{user.leg}/comment" ("value.shared" "foo"
  "size.shared" "3" )
* ANNOTATION "/mailbox/{user.rjs3}/comment" ("value.shared" "bar"
  "size.shared" "3")
* ANNOTATION "/server/motd" ("value.shared" "the message of the day")
a OK Completed

-Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski | Andrew Systems Group * Research Systems Programmer
PGP:0x5CE32FCC | Cyert Hall 207 * rjs3@andrew.cmu.edu * 412.268.7456
-----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS/IT/CM/PA d- s+: a-- C++++$ UBLS++++$ P+++$ L++(+++) E W+ N- o? K-
w O- M-- V-- PS+ PE++ Y+ PGP+ t+@ 5+++ R@ tv-- b++ DI+++ G e h r y?
------END GEEK CODE BLOCK-----






Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7GApEB28900 for ietf-imapext-bks; Fri, 16 Aug 2002 03:51:14 -0700 (PDT)
Received: from melkebalanse.gulbrandsen.priv.no (dialup-del-203.94.242.44.bol.net.in [203.94.242.44]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7GAp7w28885 for <ietf-imapext@imc.org>; Fri, 16 Aug 2002 03:51:07 -0700 (PDT)
Message-ID: <al75qo1L6j20hWEAeXdkGw.md5@melkebalanse.gulbrandsen.priv.no>
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Frank McShane <FMcS@dataconnection.com>
Subject: Re: status-counters extension
Cc: ietf-imapext@imc.org, vpim@lists.neystadt.org
References: <5B979B23E3B7D511B59100065B04D5C84DF24D@kenton.datcon.co.uk>
In-Reply-To: <5B979B23E3B7D511B59100065B04D5C84DF24D@kenton.datcon.co.uk>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
Date: Fri, 16 Aug 2002 16:21:15 +0530
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>

It doesn't sound like such a big deal.

The SEARCH volume can be a problem for the IMAP server while processing 
it, for the network while transmitting the results, for the TUI while 
processing the results, or for a combination. I'll deal with them in 
order, using a 200,000-message mailbox and a search with 60,000 results 
(30% of the messages). A bit on the high side, to make sure any 
scalability issues show up well.

The server:

Any server that's usable on such a big mailbox surely won't be using the 
naive search strategies of most current-day servers. It has to use some 
kind of indexing, or the server would be run into the ground well 
before 200,000 messages.

If it uses smartish indexing, searching 200,000 records isn't hard or 
slow. Google does subsecond searches on 2,000,000,000 records - ten 
thousand times as many.

The network:

That search result is almost 360k of data. Not very much for a 100Mbps 
ethernet. Very much for a modem connection, of course. For such a 
mailbox, "put the TUI and the IMAP server in the same room, preferably 
on the same switch" becomes a design imperative. Not onerous IMO.

The TUI:

Parsing 350k of data and storing it in a 240k array shouldn't be hard. 
RAM is cheap, and after all we're not talking about the common case. If 
the worst case doesn't mean more than a fraction of a second delay and 
having to store 240k instead of 2k, I think you're really very lucky ;)

--Arnt


Received: by above.proper.com (8.11.6/8.11.3) id g7GA80R20322 for ietf-imapext-bks; Fri, 16 Aug 2002 03:08:00 -0700 (PDT)
Received: from miles.dataconnection.com (smtp2.dataconnection.com [192.91.191.8]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7GA7ww20313 for <ietf-imapext@imc.org>; Fri, 16 Aug 2002 03:07:59 -0700 (PDT)
Received: by miles.datcon.co.uk with Internet Mail Service (5.5.2656.59) id <PTR7DKP0>; Fri, 16 Aug 2002 11:07:43 +0100
Message-ID: <5B979B23E3B7D511B59100065B04D5C84DF24D@kenton.datcon.co.uk>
From: Frank McShane <FMcS@dataconnection.com>
To: "'vpim@lists.neystadt.org'" <vpim@lists.neystadt.org>
Cc: "'ietf-imapext@imc.org'" <ietf-imapext@imc.org>
Subject: status-counters extension
Date: Fri, 16 Aug 2002 11:07:44 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain; charset="iso-8859-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>

I have been following the discussion on the status-counters extension.

I can see that the use of this function will give a scalable way to query
the contents of the mailbox,
and is extremely useful when you need to get a greeting message out through
the TUI as quickly as possible.

After the greeting message, the user might select to listen to their voice
messages.
To find the voice messages in the mailbox, the TUI will have to revert to
using SEARCH commands to find a list of the messages of interest.

That will be fine for small mailboxes (and maybe even for large ones) but
does still mean that the amount of data flowing across the wire is linear
with the number of messages.  So, at least in theory, that's a possible
scalability issue too - if only once we're dealing with mailboxes with tens
of thousands of messages in them.

I was wondering if anyone has considered whether this needs a scalable
solution also.
E.g. would it be useful to extend the fetch command to get the first message
of a particular type, then the second, then the third, and so on?

Or is it clear to everyone that this isn't really a real-world case :-)

Thanks

Frank

