Subject: Re: Agenda items?
From: Alexey Melnikov <[email-masked]>
To: Pete Resnick <[email-masked]>
Cc: [email-masked]
Date: Fri, 28 Jul 2000 23:32:27 -0600
List-Id: <ietf-imapext.imc.org>

Pete Resnick wrote:

> Anyone care to give me agenda items for Pittsburgh?

For sure ACL draft. I would like also to talk about QUOTA if time
permits.

Alexey

Date: Tue, 25 Jul 2000 22:43:28 -0700
To: Simon Josefsson <[email-masked]>, [email-masked]
From: Randall Gellens <[email-masked]>
Subject: Re: ANNOTATE
Sender: [email-masked]

At 1:53 PM +0200 7/19/00, Simon Josefsson wrote:

>  I got two questions on the ANNOTATE draft, I hope they make sense.
>
>  . What purpose does \messages\flags serve, given that the base IMAP
>    protocol support client-specific flags?  Are the namespaces the same,
>    or different?  What would the reasons for using one instead of the
>    other be?

Primarily it is a way to standardize the meaning of additional flags. 
In addition, it should resolve the private versus shared issue. 
(Also, not all servers support arbitrary flags.)

>  . Is the intent of \body\<part-specifier> a way to make it possible
>    for IMAP clients to "alter" the display of a body part?  If so, what
>    about being able to "alter" part of message headers too?  There seem
>    to be a way to "alter" the subject line with \message\subject, but no
>    other header fields. Perhaps there is room for a more generic solution
>    here.

\body\<part-specifier> allows for flags on message parts, such as 
'seen'.  The 'subject' annotation provides for recipient-supplied 
replacement text for the original message subject, a feature some 
clients (such as Eudora) support for POP but currently can't offer 
with IMAP.

>
>    (Specifically, one of the most frequent feature request in my IMAP
>    client is to be able to somehow update References: headers in a
>    article.  I guess this can be solved within the \messages\vendor
>    subtree though.)

From: "Barry Leiba" <[email-masked]>
To: "IMAP extensions Mailing List" <[email-masked]>
Subject: Re: Agenda items?
Date: Tue, 25 Jul 2000 08:54:19 -0400
Sender: [email-masked]

> Anyone care to give me agenda items for Pittsburgh?

I had agreed to write the "LIST extensions" draft, but I'd like to
revisit the COMMAND+ draft first... so why don't we have some discussion
on that?  And then I'll commit to having a LIST extensions draft out,
with or without COMMAND+ involved, by the end of August.

Barry

Date: Mon, 24 Jul 2000 17:03:19 -0400
From: Cyrus Daboo <[email-masked]>
To: Pete Resnick <[email-masked]>, [email-masked]
Subject: Re: Agenda items?
Sender: [email-masked]

--On 07/24/00 15:39:22 -0500 Pete Resnick <[email-masked]> wrote:

> Anyone care to give me agenda items for Pittsburgh?

Drafts that I am directly involved with:

VIEW extension:
 - discussion about new \View flag mechanism for 
dynamic/semi-dynamic/static client behaviour
 - other issues with the document
 - discussion about SORT2 - proposals for new sort key items
 - last call current draft-ietf-imapext-sort (SORT)?

ANNOTATE extension:
 - discussion of document, in particular 'open issues'

-- 
Cyrus Daboo

Date: Mon, 24 Jul 2000 15:39:22 -0500
To: [email-masked]
From: Pete Resnick <[email-masked]>
Subject: Agenda items?
Sender: [email-masked]

Anyone care to give me agenda items for Pittsburgh?

pr
-- 
Pete Resnick <mailto:[email-masked]>
Eudora Engineering - QUALCOMM Incorporated
Ph: (217)337-6377 or (858)651-4478, Fax: (858)651-1102

To: [email-masked]
Subject: ANNOTATE
From: Simon Josefsson <[email-masked]>
Mail-Copies-To: never
Date: 19 Jul 2000 13:53:35 +0200
Lines: 18
Sender: [email-masked]

I got two questions on the ANNOTATE draft, I hope they make sense.

. What purpose does \messages\flags serve, given that the base IMAP
  protocol support client-specific flags?  Are the namespaces the same,
  or different?  What would the reasons for using one instead of the
  other be?

. Is the intent of \body\<part-specifier> a way to make it possible
  for IMAP clients to "alter" the display of a body part?  If so, what
  about being able to "alter" part of message headers too?  There seem
  to be a way to "alter" the subject line with \message\subject, but no
  other header fields. Perhaps there is room for a more generic solution
  here.

  (Specifically, one of the most frequent feature request in my IMAP
  client is to be able to somehow update References: headers in a
  article.  I guess this can be solved within the \messages\vendor
  subtree though.)

To: IETF-Announce: ;
Cc: [email-masked]
From: [email-masked]
Reply-to: [email-masked]
Subject: I-D ACTION:draft-ietf-imapext-annotate-00.txt
Date: Wed, 19 Jul 2000 06:34:49 -0400
Sender: [email-masked]

--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		: IMAP ANNOTATE Extension
	Author(s)	: R. Gellens, C. Daboo
	Filename	: draft-ietf-imapext-annotate-00.txt
	Pages		: 19
	Date		: 18-Jul-00
	
The ANNOTATE extension to the Internet Message Access Protocol
[IMAP4] permits clients and servers to maintain

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

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-annotate-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:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-imapext-annotate-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="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-imapext-annotate-00.txt

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

Content-Type: text/plain
Content-ID:	<[email-masked]>

--OtherAccess--

--NextPart--

Date: Thu, 13 Jul 2000 23:37:40 -0700
To: [email-masked]
From: Randall Gellens <[email-masked]>
Subject: Updated ANNOTATE Draft
Sender: [email-masked]

I just sent in an updated ANNOTATE draft.  I expect it will be a week or two until it shows up in the I-D directories, so in the meantime it is available at <ftp://ftp.pensive.org/public/randy/ietf-imapext-annotate-01.txt>.  Comments welcome, especially on the items marked "<<<OPEN-ISSUE>>>".

-- 
Randall Gellens
[email-masked]
-------------- Randomly-selected tag: ---------------
It wasn't as easy to get programs right as we had thought.  
                                           --Wilkes, 1949

Date: Fri, 28 Jul 2000 23:32:27 -0600
From: Alexey Melnikov <[email-masked]>
To: Pete Resnick <[email-masked]>
CC: [email-masked]
Subject: Re: Agenda items?
Sender: [email-masked]

Pete Resnick wrote:

> Anyone care to give me agenda items for Pittsburgh?

For sure ACL draft. I would like also to talk about QUOTA if time
permits.

Alexey

Date: Tue, 25 Jul 2000 22:43:28 -0700
To: Simon Josefsson <[email-masked]>, [email-masked]
From: Randall Gellens <[email-masked]>
Subject: Re: ANNOTATE
Sender: [email-masked]

At 1:53 PM +0200 7/19/00, Simon Josefsson wrote:

>  I got two questions on the ANNOTATE draft, I hope they make sense.
>
>  . What purpose does \messages\flags serve, given that the base IMAP
>    protocol support client-specific flags?  Are the namespaces the same,
>    or different?  What would the reasons for using one instead of the
>    other be?

Primarily it is a way to standardize the meaning of additional flags. 
In addition, it should resolve the private versus shared issue. 
(Also, not all servers support arbitrary flags.)

>  . Is the intent of \body\<part-specifier> a way to make it possible
>    for IMAP clients to "alter" the display of a body part?  If so, what
>    about being able to "alter" part of message headers too?  There seem
>    to be a way to "alter" the subject line with \message\subject, but no
>    other header fields. Perhaps there is room for a more generic solution
>    here.

\body\<part-specifier> allows for flags on message parts, such as 
'seen'.  The 'subject' annotation provides for recipient-supplied 
replacement text for the original message subject, a feature some 
clients (such as Eudora) support for POP but currently can't offer 
with IMAP.

>
>    (Specifically, one of the most frequent feature request in my IMAP
>    client is to be able to somehow update References: headers in a
>    article.  I guess this can be solved within the \messages\vendor
>    subtree though.)

From: "Barry Leiba" <[email-masked]>
To: "IMAP extensions Mailing List" <[email-masked]>
Subject: Re: Agenda items?
Date: Tue, 25 Jul 2000 08:54:19 -0400
Sender: [email-masked]

> Anyone care to give me agenda items for Pittsburgh?

I had agreed to write the "LIST extensions" draft, but I'd like to
revisit the COMMAND+ draft first... so why don't we have some discussion
on that?  And then I'll commit to having a LIST extensions draft out,
with or without COMMAND+ involved, by the end of August.

Barry

Date: Mon, 24 Jul 2000 17:03:19 -0400
From: Cyrus Daboo <[email-masked]>
To: Pete Resnick <[email-masked]>, [email-masked]
Subject: Re: Agenda items?
Sender: [email-masked]

--On 07/24/00 15:39:22 -0500 Pete Resnick <[email-masked]> wrote:

> Anyone care to give me agenda items for Pittsburgh?

Drafts that I am directly involved with:

VIEW extension:
 - discussion about new \View flag mechanism for 
dynamic/semi-dynamic/static client behaviour
 - other issues with the document
 - discussion about SORT2 - proposals for new sort key items
 - last call current draft-ietf-imapext-sort (SORT)?

ANNOTATE extension:
 - discussion of document, in particular 'open issues'

-- 
Cyrus Daboo

Date: Mon, 24 Jul 2000 15:39:22 -0500
To: [email-masked]
From: Pete Resnick <[email-masked]>
Subject: Agenda items?
Sender: [email-masked]

Anyone care to give me agenda items for Pittsburgh?

pr
-- 
Pete Resnick <mailto:[email-masked]>
Eudora Engineering - QUALCOMM Incorporated
Ph: (217)337-6377 or (858)651-4478, Fax: (858)651-1102

To: [email-masked]
Subject: ANNOTATE
From: Simon Josefsson <[email-masked]>
Mail-Copies-To: never
Date: 19 Jul 2000 13:53:35 +0200
Lines: 18
Sender: [email-masked]

I got two questions on the ANNOTATE draft, I hope they make sense.

. What purpose does \messages\flags serve, given that the base IMAP
  protocol support client-specific flags?  Are the namespaces the same,
  or different?  What would the reasons for using one instead of the
  other be?

. Is the intent of \body\<part-specifier> a way to make it possible
  for IMAP clients to "alter" the display of a body part?  If so, what
  about being able to "alter" part of message headers too?  There seem
  to be a way to "alter" the subject line with \message\subject, but no
  other header fields. Perhaps there is room for a more generic solution
  here.

  (Specifically, one of the most frequent feature request in my IMAP
  client is to be able to somehow update References: headers in a
  article.  I guess this can be solved within the \messages\vendor
  subtree though.)

To: IETF-Announce: ;
Cc: [email-masked]
From: [email-masked]
Reply-to: [email-masked]
Subject: I-D ACTION:draft-ietf-imapext-view-00.txt
Date: Wed, 19 Jul 2000 06:34:53 -0400
Sender: [email-masked]

--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		: IMAP VIEW Extension
	Author(s)	: C. Daboo, M. Pustilnik, M. Crispin
	Filename	: draft-ietf-imapext-view-00.txt
	Pages		: 19
	Date		: 18-Jul-00
	
The VIEW extension to the Internet Message Access Protocol [IMAP4]
permits a subset of messages in the mailbox to be processed
separately from the entire set of messages in the mailbox.  This
allows a client to restrict its view to only the messages appearing
in this set.  The subset of messages also need not be returned in
order of their sequence numbers, allowing clients to access messages
in a particular sort order.
The subsetting and sorting of messages is handled by existing
[IMAP4] commands that return a set of messages as their result.
This extension takes the set returned from such a command and
applies the VIEW methodology to it.

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

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-view-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:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-imapext-view-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="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-imapext-view-00.txt

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

Content-Type: text/plain
Content-ID:	<[email-masked]>

--OtherAccess--

--NextPart--

To: IETF-Announce: ;
Cc: [email-masked]
From: [email-masked]
Reply-to: [email-masked]
Subject: I-D ACTION:draft-ietf-imapext-annotate-00.txt
Date: Wed, 19 Jul 2000 06:34:49 -0400
Sender: [email-masked]

--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		: IMAP ANNOTATE Extension
	Author(s)	: R. Gellens, C. Daboo
	Filename	: draft-ietf-imapext-annotate-00.txt
	Pages		: 19
	Date		: 18-Jul-00
	
The ANNOTATE extension to the Internet Message Access Protocol
[IMAP4] permits clients and servers to maintain

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

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-annotate-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:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-imapext-annotate-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="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-imapext-annotate-00.txt

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

Content-Type: text/plain
Content-ID:	<[email-masked]>

--OtherAccess--

--NextPart--

Date: Thu, 13 Jul 2000 23:37:40 -0700
To: [email-masked]
From: Randall Gellens <[email-masked]>
Subject: Updated ANNOTATE Draft
Sender: [email-masked]

I just sent in an updated ANNOTATE draft.  I expect it will be a week or two until it shows up in the I-D directories, so in the meantime it is available at <ftp://ftp.pensive.org/public/randy/ietf-imapext-annotate-01.txt>.  Comments welcome, especially on the items marked "<<<OPEN-ISSUE>>>".

-- 
Randall Gellens
[email-masked]
-------------- Randomly-selected tag: ---------------
It wasn't as easy to get programs right as we had thought.  
                                           --Wilkes, 1949