Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1SNrBi21287 for ietf-imapext-bks; Thu, 28 Feb 2002 15:53:11 -0800 (PST) Received: from duck.mail.pas.earthlink.net (duck.mail.pas.earthlink.net [207.217.121.117]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1SNr9i21283; Thu, 28 Feb 2002 15:53:10 -0800 (PST) Received: from eburger (ANice-102-2-1-235.abo.wanadoo.fr [193.252.60.235]) by duck.mail.pas.earthlink.net (8.9.3/8.9.3) with ESMTP id PAA19230; Thu, 28 Feb 2002 15:53:11 -0800 (PST) Reply-To: From: "Eric Burger" To: , "IETF UM" , Subject: FW: [VPIM] I-D ACTION:draft-burger-imap-chanuse-00.txt Date: Thu, 28 Feb 2002 18:52:58 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0091_01C1C089.23B60AF0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_0091_01C1C089.23B60AF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit This draft may be of interest to your groups. A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IMAP CHANNEL Use Cases Author(s) : E. Burger Filename : draft-burger-imap-chanuse-00.txt Pages : 7 Date : 27-Feb-02 This document describes different use cases for using the IMAP CHANNEL facility. Discussion of this and related drafts are on the IMAP Voice list. To subscribe, send the message 'subscribe' to ietf-imap-voice-request@imc.org . A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-burger-imap-chanuse-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-burger-imap-chanuse-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-burger-imap-chanuse-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. Received: by above.proper.com (8.11.6/8.11.3) id g1RFxwh26359 for ietf-imapext-bks; Wed, 27 Feb 2002 07:59:58 -0800 (PST) Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1RFxv326355 for ; Wed, 27 Feb 2002 07:59:57 -0800 (PST) Received: from socrates.cyrusoft.com (localhost [127.0.0.1]) by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id KAA16939 for ; Wed, 27 Feb 2002 10:57:27 -0500 (EST) Date: Wed, 27 Feb 2002 10:59:57 -0500 From: Cyrus Daboo To: IMAP Extensions WG Subject: I-D ACTION:draft-daboo-imap-annotatemore-00.txt (fwd) Message-ID: <2147483647.1014807597@socrates.cyrusoft.com> X-Mailer: Mulberry/3.0.0d3 (Mac OS/PPC) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: FYI The following draft is a private submission that describes an annotation extension that allows annotations on mailboxes and the server and is meant to be a complement to the message annotation draft. Any comments are welcome... ---------- Forwarded Message ---------- Date: Wednesday, February 27, 2002 7:23 AM -0500 From: Internet-Drafts@ietf.org To: IETF-Announce Subject: I-D ACTION:draft-daboo-imap-annotatemore-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IMAP ANNOTATEMORE Extension Author(s) : C. Daboo Filename : draft-daboo-imap-annotatemore-00.txt Pages : 14 Date : 26-Feb-02 The ANNOTATEMORE extension to the Internet Message Access Protocol [IMAP4] permits clients and servers to maintain 'metadata' on IMAP4 servers. This document describes two 'profiles' for mailbox and server metadata. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-daboo-imap-annotatemore-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-daboo-imap-annotatemore-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-daboo-imap-annotatemore-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. ---------- End Forwarded Message ---------- -- Cyrus Daboo Received: by above.proper.com (8.11.6/8.11.3) id g1OH4db19712 for ietf-imapext-bks; Sun, 24 Feb 2002 09:04:39 -0800 (PST) Received: from duck.mail.pas.earthlink.net (duck.mail.pas.earthlink.net [207.217.121.117]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1OH48319702 for ; Sun, 24 Feb 2002 09:04:08 -0800 (PST) Received: from eburger (ANice-102-2-1-96.abo.wanadoo.fr [193.252.60.96]) by duck.mail.pas.earthlink.net (8.9.3/8.9.3) with ESMTP id JAA26265; Sun, 24 Feb 2002 09:03:57 -0800 (PST) Reply-To: From: "Eric Burger" To: "Cyrus Daboo" , "Jutta Degener" Cc: Subject: RE: More SORT keys Date: Sun, 24 Feb 2002 12:03:46 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <847389664.1008261016@70-202-131-12.bellhead.com> Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: That's fine, so long as we use messagehint as an example, as it WILL be used. -----Original Message----- From: owner-ietf-imapext@mail.imc.org [mailto:owner-ietf-imapext@mail.imc.org]On Behalf Of Cyrus Daboo Sent: Thursday, December 13, 2001 6:30 PM To: Jutta Degener Cc: ietf-imapext@imc.org Subject: Re: More SORT keys --On Thursday, December 13, 2001 3:12 PM -0800 Jutta Degener wrote: > Maybe, rather than defining an specific extended feature set associated > with a SORT2 capability, we could do something along the lines of a > SORT=FOO,BAR,BAZ capability? > > Then new drafts that only define specific sorting rules can define SORT > capabilities (e.g., "MESSAGEHINT") that a server can announce without > requiring an update to SORT itself. > > Just an idea. I think that would be a fine solution. The question is whether this group would want to define any of these now, or simply require the the current sort document to indicate that this extensibility is possible. -- Cyrus Daboo Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1MBL2Z19567 for ietf-imapext-bks; Fri, 22 Feb 2002 03:21:02 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1MBL0319548 for ; Fri, 22 Feb 2002 03:21:00 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27151; Fri, 22 Feb 2002 06:20:57 -0500 (EST) Message-Id: <200202221120.GAA27151@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ietf-imapext@imc.org, vpim@lists.neystadt.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-vaudreuil-um-issues-00.txt Date: Fri, 22 Feb 2002 06:20:56 -0500 Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Messaging profile for telephone-based Messaging clients Author(s) : G. Vaudreuil Filename : draft-vaudreuil-um-issues-00.txt Pages : 12 Date : 21-Feb-02 This document discussed issues and requirements for a profile of the IMAP 4, message submission, and notification protocols for use by telephone user interfaces delivering the traditional voice mail user experience. Experience with IMAP 4 and voice mail systems has shown quite a few limitations that may be addressed by protocol extensions and standardized conventions between clients and servers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-vaudreuil-um-issues-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-vaudreuil-um-issues-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-vaudreuil-um-issues-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: <20020221155809.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-vaudreuil-um-issues-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-vaudreuil-um-issues-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020221155809.I-D@ietf.org> --OtherAccess-- --NextPart-- Received: by above.proper.com (8.11.6/8.11.3) id g1M6cv813887 for ietf-imapext-bks; Thu, 21 Feb 2002 22:38:57 -0800 (PST) Received: from Ikkoku-Kan.Panda.COM (peter@ikkoku-kan.panda.com [206.124.149.114]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1M6ct313882 for ; Thu, 21 Feb 2002 22:38:55 -0800 (PST) Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id WAA24755; Thu, 21 Feb 2002 22:38:55 -0800 (PST) Date: Thu, 21 Feb 2002 21:23:20 -0800 (PST) From: Mark Crispin Subject: Re: more on ACL2 To: Lawrence Greenfield cc: IMAP Extensions WG In-Reply-To: <200202220519.g1M5JeYJ016976@smtp5.andrew.cmu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Fri, 22 Feb 2002 00:19:40 -0500, Lawrence Greenfield wrote: > I disagree with almost all of the below. All of these complicate > existing ACL implementations. Many of them aren't even possible for > servers that have external authentication or authorization sources > that aren't tightly coupled to the IMAP server. Somehow, we must fix the missing functionality in IMAP ACL. Failure will result in multiple incompatible IMAP ACL specifications. IESG has already said that this will prevent the standardization of any IMAP ACL specification. Complexity has a cost, but this complexity is necessary in order to make ACL generic enough to be implementable on some platforms. We must pay this cost now, because in the past not enough attention was paid to multi-platform implementability. My proposal is an attempt to define the missing functionality in a manner which (1) is generic and not specific to any particular operating system, (2) does not create any new mandates for existing AFS-based implementations. I have not seen any other proposal that addresses the problem. I would be very happy to see a counter-proposal which also addresses the problem. Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1M5JiL12466 for ietf-imapext-bks; Thu, 21 Feb 2002 21:19:44 -0800 (PST) Received: from smtp5.andrew.cmu.edu (SMTP5.ANDREW.CMU.EDU [128.2.10.85]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1M5Jh312462 for ; Thu, 21 Feb 2002 21:19:43 -0800 (PST) Received: from dunbar.rem.cmu.edu (DUNBAR.REM.CMU.EDU [128.2.4.197]) by smtp5.andrew.cmu.edu (8.12.2.Beta3/8.12.2.Beta3) with ESMTP id g1M5JeYJ016976; Fri, 22 Feb 2002 00:19:40 -0500 Date: Fri, 22 Feb 2002 00:19:40 -0500 Message-Id: <200202220519.g1M5JeYJ016976@smtp5.andrew.cmu.edu> From: Lawrence Greenfield X-Mailer: BatIMail version 3.2 To: IMAP Extensions WG In-reply-to: Subject: Re: more on ACL2 References: Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I disagree with almost all of the below. All of these complicate existing ACL implementations. Many of them aren't even possible for servers that have external authentication or authorization sources that aren't tightly coupled to the IMAP server. Larry Date: Thu, 21 Feb 2002 16:00:10 -0800 (PST) From: Mark Crispin There needs to be a way to identify, per-mailbox, what identifiers are valid. There needs to be a way to change the identifier of an existing ACL. There needs to be a way to know if an ACL can be added or an existing ACL can be removed. Consider a fixed number of ACLs which can be modified (and their identifiers altered), but no ACL can be added or removed. A lot of this may be done by means of clever naming, but that naming scheme needs to be standardized. I'm starting to think that a "$" prefix isn't really the right thing, that instead, we need some sort of type=value identifier. GETACL does not distinguish between tied and untied rights. This is because of its syntax. Better to follow the rest of IMAP and use S-expression type syntax for all ACLs, e.g. "(" identifier SPACE rights *(SPACE rights) ")" Example: C: A002 GETACL INBOX S: * ACL INBOX (user=fred l r wipsextda)(group=staff l r)(anyone l) S: A002 OK GETACL completed Note, however, that I can not use "user=". I really need two different kinds of groups, one which is per-mailbox and one which is global. Also, it's important that anonymous *NOT* be part of anyone. Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1M0HGb05927 for ietf-imapext-bks; Thu, 21 Feb 2002 16:17:16 -0800 (PST) Received: from Ikkoku-Kan.Panda.COM (satori@ikkoku-kan.panda.com [206.124.149.114]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1M0HE305923 for ; Thu, 21 Feb 2002 16:17:14 -0800 (PST) Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id QAA23245; Thu, 21 Feb 2002 16:17:14 -0800 (PST) Date: Thu, 21 Feb 2002 16:00:10 -0800 (PST) From: Mark Crispin Subject: more on ACL2 To: IMAP Extensions WG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: There needs to be a way to identify, per-mailbox, what identifiers are valid. There needs to be a way to change the identifier of an existing ACL. There needs to be a way to know if an ACL can be added or an existing ACL can be removed. Consider a fixed number of ACLs which can be modified (and their identifiers altered), but no ACL can be added or removed. A lot of this may be done by means of clever naming, but that naming scheme needs to be standardized. I'm starting to think that a "$" prefix isn't really the right thing, that instead, we need some sort of type=value identifier. GETACL does not distinguish between tied and untied rights. This is because of its syntax. Better to follow the rest of IMAP and use S-expression type syntax for all ACLs, e.g. "(" identifier SPACE rights *(SPACE rights) ")" Example: C: A002 GETACL INBOX S: * ACL INBOX (user=fred l r wipsextda)(group=staff l r)(anyone l) S: A002 OK GETACL completed Note, however, that I can not use "user=". I really need two different kinds of groups, one which is per-mailbox and one which is global. Also, it's important that anonymous *NOT* be part of anyone. Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1LGSAp23336 for ietf-imapext-bks; Thu, 21 Feb 2002 08:28:10 -0800 (PST) Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1LGS8323327 for ; Thu, 21 Feb 2002 08:28:08 -0800 (PST) Received: from PLATO (localhost [127.0.0.1]) by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id LAA12288; Thu, 21 Feb 2002 11:23:01 -0500 (EST) Date: Thu, 21 Feb 2002 11:24:42 -0500 From: Cyrus Daboo To: Alexey Melnikov , Pete Resnick cc: ietf-imapext@imc.org Subject: Re: Do we need to meet? Message-ID: <846929059.1014290682@PLATO> In-Reply-To: <3C749EDF.B057410A@messagingdirect.com> References: <3C749EDF.B057410A@messagingdirect.com> X-Mailer: Mulberry/2.2.0b2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, --On Thursday, February 21, 2002 12:16 AM -0700 Alexey Melnikov wrote: > What happened to mailbox annotations and "ACL ids to Friendly Names" (the > draft that Chris was working on)? I will be submitting a draft on mailbox and server annotations before the deadline for new drafts tomorrow. I was waiting on comments on the message annotate draft before proceeding with this as it does depend on some aspects of message annotations (though it doesn't require implementing message annotations to do mailbox/server annotations). This will be a private submission since its not on the IMAPext charter. I will also be updating the message annotation document before the cut-off for existing drafts. At that point we need to decide on the last-call status. -- Cyrus Daboo Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1LGIfT22792 for ietf-imapext-bks; Thu, 21 Feb 2002 08:18:41 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1LGIe322788 for ; Thu, 21 Feb 2002 08:18:40 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g1LGFsj13582; Thu, 21 Feb 2002 09:15:54 -0700 Message-ID: <3C749EDF.B057410A@messagingdirect.com> Date: Thu, 21 Feb 2002 00:16:47 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Pete Resnick CC: ietf-imapext@imc.org Subject: Re: Do we need to meet? References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Pete Resnick wrote: > On 2/14/02 at 5:11 PM -0600, I wrote: > > >It looks to me that ANNOTATE is getting close. CONDSTORE doesn't > >seem to have too much in the way of open issues. I'm not sure what > >the state of ACL is. Do we have reason to meet in Minneapolis or not? > > I will take this silence to mean that we don't have to meet. Any objections? I guess everybody want to go to Japan instead of Minneapolis ;-). I have more unresolved issues with ACL and CONDSTORE I will submit to the mailing list shortly. I would like to ask people to share their opinion whether these documents are ready for Last Call. What happened to mailbox annotations and "ACL ids to Friendly Names" (the draft that Chris was working on)? I will be attending Minneapolis anyway, so I am curious who is going to attend. Please reply privately. Regards, Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: by above.proper.com (8.11.6/8.11.3) id g1LC1bZ08319 for ietf-imapext-bks; Thu, 21 Feb 2002 04:01:37 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1LC1Z308315 for ; Thu, 21 Feb 2002 04:01:35 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14111; Thu, 21 Feb 2002 07:01:34 -0500 (EST) Message-Id: <200202211201.HAA14111@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-ietf-imapext-acl-03.txt Date: Thu, 21 Feb 2002 07:01:33 -0500 Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --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 : IMAP4 ACL extension Author(s) : A. Melnikov Filename : draft-ietf-imapext-acl-03.txt Pages : 9 Date : 20-Feb-02 The ACL extension of the Internet Message Access Protocol [IMAP4] permits access control lists to be manipulated through the IMAP protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imapext-acl-03.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-ietf-imapext-acl-03.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-ietf-imapext-acl-03.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: <20020220135109.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imapext-acl-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imapext-acl-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020220135109.I-D@ietf.org> --OtherAccess-- --NextPart-- Received: by above.proper.com (8.11.6/8.11.3) id g1L67g529990 for ietf-imapext-bks; Wed, 20 Feb 2002 22:07:42 -0800 (PST) Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1L67e329986 for ; Wed, 20 Feb 2002 22:07:41 -0800 (PST) Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1L67exY029272 for ; Wed, 20 Feb 2002 22:07:45 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Wed Feb 20 22:07:39 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1L67akx018673 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Feb 2002 22:07:39 -0800 Date: Wed, 20 Feb 2002 21:45:44 -0800 (PST) From: Mark Crispin Subject: ACL2 To: IMAP Extensions WG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Since ACL2 can be incompatible from ACL, we should define a replacement identifier for "anyone" that does not conflict with a login id of "anyone". As matters stand now, the text: [...] The identifier "anyone" is reserved to refer to the universal identity (all authentications, including anonymous). All user name strings accepted by the LOGIN or AUTHENTICATE commands to authenticate to the IMAP server are reserved as identifiers for the corresponding user. is self-contradictory. Delete "PARTIAL" as a permitted operation of the "r" right. PARTIAL is a deprecated feature of RFC1730 which should now be extinct. The "d" right should first be described as "RFC 2086 compatible delete right" and then its semantics listed. Unfortunately, the given semantics don't work. What if one or more of the "x", "e", or "t" rights can not be set or cleared? Suggest changing the MUST to SHOULD. Consider deprecating the "d" right entirely for an ACL2-only server. Paragraph describing negative rights should make it clear that a negative right is not the same thing as a DELETACL. ACL2=MOST-SPECIFIC is a big improvement. Is ACL2=UNION really still necessary? Wouldn't it be better to do this in the semantics of the naming? Note that the addition of ACL2=MOST-SPECIFIC renders certain parts of my proposed naming system moot. However, there are other part of it which remain desirable, including: . new commands to access and define groups . separate "world" vs. "anonymous" access Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1L18bR23172 for ietf-imapext-bks; Wed, 20 Feb 2002 17:08:37 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1L18Z323168 for ; Wed, 20 Feb 2002 17:08:35 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g1L1Arj07055; Wed, 20 Feb 2002 18:10:58 -0700 Message-ID: <3C74432D.CAD507E9@messagingdirect.com> Date: Wed, 20 Feb 2002 17:45:33 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Arnt Gulbrandsen CC: Cyrus Daboo , IMAP Extensions WG Subject: Re: ACL2 backward compatability References: <2147483647.1013770289@socrates.cyrusoft.com> <3C6D45D6.AA1141B8@messagingdirect.com> <20020215190214.Q22712@witt-witt.caldera.de> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Arnt Gulbrandsen wrote: > Alexey Melnikov > > IMHO, only if a particular server implementation uses "$" prefix for groups and > > other special identifiers. > > The draft lists the incompatibilities; should it also explictly recommend > that servers advertise "ACL" if these incompatibilities don't apply in > that server's case? I've just added this to the version 03 I've sent yesterday. Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: by above.proper.com (8.11.6/8.11.3) id g1KH75n12219 for ietf-imapext-bks; Wed, 20 Feb 2002 09:07:05 -0800 (PST) Received: from episteme-software.com (champdsl-25-66.mcleodusa.net [216.43.25.66]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1KH73312215 for ; Wed, 20 Feb 2002 09:07:03 -0800 (PST) Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with ESMTP (Eudora Internet Mail Server 3.1) for ; Wed, 20 Feb 2002 11:07:00 -0600 Mime-Version: 1.0 X-Sender: resnick@resnick1.qualcomm.com (Unverified) Message-Id: In-Reply-To: References: X-Mailer: Eudora [Macintosh version 5.1fc3] Date: Wed, 20 Feb 2002 11:06:54 -0600 To: ietf-imapext@imc.org From: Pete Resnick Subject: Re: Do we need to meet? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On 2/14/02 at 5:11 PM -0600, I wrote: >It looks to me that ANNOTATE is getting close. CONDSTORE doesn't >seem to have too much in the way of open issues. I'm not sure what >the state of ACL is. Do we have reason to meet in Minneapolis or not? I will take this silence to mean that we don't have to meet. Any objections? pr -- Pete Resnick QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 Received: by above.proper.com (8.11.6/8.11.3) id g1FI3Lf09447 for ietf-imapext-bks; Fri, 15 Feb 2002 10:03:21 -0800 (PST) Received: from witt-witt.caldera.de (witt-witt.caldera.de [195.143.241.43]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1FI3H309443 for ; Fri, 15 Feb 2002 10:03:18 -0800 (PST) Received: (from arnt@localhost) by witt-witt.caldera.de (8.11.6/8.11.6) id g1FI2Ep27048; Fri, 15 Feb 2002 19:02:15 +0100 Date: Fri, 15 Feb 2002 19:02:14 +0100 From: Arnt Gulbrandsen To: Alexey Melnikov Cc: Cyrus Daboo , IMAP Extensions WG Subject: Re: ACL2 backward compatability Message-ID: <20020215190214.Q22712@witt-witt.caldera.de> References: <2147483647.1013770289@socrates.cyrusoft.com> <3C6D45D6.AA1141B8@messagingdirect.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C6D45D6.AA1141B8@messagingdirect.com> Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Alexey Melnikov > IMHO, only if a particular server implementation uses "$" prefix for groups and > other special identifiers. The draft lists the incompatibilities; should it also explictly recommend that servers advertise "ACL" if these incompatibilities don't apply in that server's case? --Arnt Received: by above.proper.com (8.11.6/8.11.3) id g1FHSe808475 for ietf-imapext-bks; Fri, 15 Feb 2002 09:28:40 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1FHSc308470 for ; Fri, 15 Feb 2002 09:28:38 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g1FHV5j19789; Fri, 15 Feb 2002 10:31:05 -0700 Message-ID: <3C6D45D6.AA1141B8@messagingdirect.com> Date: Fri, 15 Feb 2002 10:31:02 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Cyrus Daboo CC: IMAP Extensions WG Subject: Re: ACL2 backward compatability References: <2147483647.1013770289@socrates.cyrusoft.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Cyrus Daboo wrote: > I think the current ACL2 draft has backwards compatibility with the old ACL > draft wrt the the defined ACL bits. So should the current draft require > servers to also advertise 'ACL' in the capability response as well as > ACL2=xxx to allow existing ACL clients to interoperate? I would argue yes. IMHO, only if a particular server implementation uses "$" prefix for groups and other special identifiers. Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1FFpVd04426 for ietf-imapext-bks; Fri, 15 Feb 2002 07:51:31 -0800 (PST) Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1FFpU304421 for ; Fri, 15 Feb 2002 07:51:30 -0800 (PST) Received: from socrates.cyrusoft.com (localhost [127.0.0.1]) by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id KAA07538 for ; Fri, 15 Feb 2002 10:49:03 -0500 (EST) Date: Fri, 15 Feb 2002 10:51:29 -0500 From: Cyrus Daboo To: IMAP Extensions WG Subject: ACL2 backward compatability Message-ID: <2147483647.1013770289@socrates.cyrusoft.com> X-Mailer: Mulberry/3.0.0d2 (Mac OS/PPC) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I think the current ACL2 draft has backwards compatibility with the old ACL draft wrt the the defined ACL bits. So should the current draft require servers to also advertise 'ACL' in the capability response as well as ACL2=xxx to allow existing ACL clients to interoperate? I would argue yes. -- Cyrus Daboo Received: by above.proper.com (8.11.6/8.11.3) id g1FFmtf04300 for ietf-imapext-bks; Fri, 15 Feb 2002 07:48:55 -0800 (PST) Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1FFmr304296 for ; Fri, 15 Feb 2002 07:48:53 -0800 (PST) Received: from socrates.cyrusoft.com (localhost [127.0.0.1]) by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id KAA07502 for ; Fri, 15 Feb 2002 10:46:26 -0500 (EST) Date: Fri, 15 Feb 2002 10:48:52 -0500 From: Cyrus Daboo To: IMAP Extensions WG Subject: ACL and STATUS Message-ID: <2147483647.1013770132@socrates.cyrusoft.com> X-Mailer: Mulberry/3.0.0d2 (Mac OS/PPC) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The current ACL rfc and the latest draft for the updated version don't indicate which ACL bit controls the behaviour of the STATUS command. I would guess that at least read 'r' access is required in order to get status information on a mailbox. Can we have STATUS explicitly listed as one of the commands available for the 'r' bit? The other option would be to allow status with only the 'l' bit, which currently allows LIST/LSUB for a mailbox. If we ever get around to extending list, I believe one of the proposals did have list returning the equivalent of status information, so there might be some awkward interaction with ACL on that. -- Cyrus Daboo Received: by above.proper.com (8.11.6/8.11.3) id g1ENBIh00233 for ietf-imapext-bks; Thu, 14 Feb 2002 15:11:18 -0800 (PST) Received: from episteme-software.com (champdsl-25-66.mcleodusa.net [216.43.25.66]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1ENBH300227 for ; Thu, 14 Feb 2002 15:11:17 -0800 (PST) Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with ESMTP (Eudora Internet Mail Server 3.1) for ; Thu, 14 Feb 2002 17:11:14 -0600 Mime-Version: 1.0 X-Sender: resnick@resnick1.qualcomm.com (Unverified) Message-Id: X-Mailer: Eudora [Macintosh version 5.1fc3] Date: Thu, 14 Feb 2002 17:11:11 -0600 To: ietf-imapext@imc.org From: Pete Resnick Subject: Do we need to meet? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: It looks to me that ANNOTATE is getting close. CONDSTORE doesn't seem to have too much in the way of open issues. I'm not sure what the state of ACL is. Do we have reason to meet in Minneapolis or not? pr -- Pete Resnick QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g15N22x14956 for ietf-imapext-bks; Tue, 5 Feb 2002 15:02:02 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g15N21314951 for ; Tue, 5 Feb 2002 15:02:01 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g15N21j06772; Tue, 5 Feb 2002 16:02:01 -0700 Message-ID: <3C60646B.A5AFCEF6@messagingdirect.com> Date: Tue, 05 Feb 2002 16:02:03 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: IMAP Extensions WG Subject: Re: I-D ACTION:draft-melnikov-imap-condstore-06.txt References: <200202051451.JAA01738@ietf.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is the second revision submitted this year. Changes from -05 to -06: 1. Replaced "/message/flags/system" with "/message/flags" to match ANNOTATE draft. 2. Extended FETCH/SEARCH/SORT syntax to allow for specifying whether an operation should be performed on a shared or a private annotation (or both). 3. Corrected several examples. Changes from -04 to -05: 1. Added support for SORT extension. 2. Multiple language/spelling fixes by Randall Gellens. There is one major open issue left: MODSEQ fetch response as the result of STORE/UID STORE of a flag in any IMAP session: what _type_ of modseq should be returned: private, shared, both? This is related to the change 2) between 05 and 06. Comments? Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: by above.proper.com (8.11.6/8.11.3) id g15I0AM02848 for ietf-imapext-bks; Tue, 5 Feb 2002 10:00:10 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g15I08302843 for ; Tue, 5 Feb 2002 10:00:08 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g15I07j02995; Tue, 5 Feb 2002 11:00:07 -0700 Message-ID: <3C601DA9.800398B5@messagingdirect.com> Date: Tue, 05 Feb 2002 11:00:10 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: ietf-imapext@imc.org Subject: Re: I-D ACTION:draft-ietf-imapext-acl-02.txt References: <200202051451.JAA01899@ietf.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: A new revision is out. Major changes in this version: 1). Changed ACL capability name to ACL2= Added registry for the rules. Described two rules: UNION (union of the positive minus union of negative), MOST-SPECIFIC (most specific identifier describes the rights). 2). Added "t" right for performing STORE \Deleted. Changed "d" to be a macro for "x", "t" and "e". Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: by above.proper.com (8.11.6/8.11.3) id g15EpoM23056 for ietf-imapext-bks; Tue, 5 Feb 2002 06:51:50 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g15Epm323052 for ; Tue, 5 Feb 2002 06:51:48 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01899; Tue, 5 Feb 2002 09:51:46 -0500 (EST) Message-Id: <200202051451.JAA01899@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-ietf-imapext-acl-02.txt Date: Tue, 05 Feb 2002 09:51:46 -0500 Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --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 : IMAP4 ACL extension Author(s) : A. Melnikov Filename : draft-ietf-imapext-acl-02.txt Pages : 9 Date : 04-Feb-02 The ACL extension of the Internet Message Access Protocol [IMAP4] permits access control lists to be manipulated through the IMAP protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imapext-acl-02.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-ietf-imapext-acl-02.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-ietf-imapext-acl-02.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: <20020204134227.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imapext-acl-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imapext-acl-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020204134227.I-D@ietf.org> --OtherAccess-- --NextPart-- Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1SNrBi21287 for ietf-imapext-bks; Thu, 28 Feb 2002 15:53:11 -0800 (PST) Received: from duck.mail.pas.earthlink.net (duck.mail.pas.earthlink.net [207.217.121.117]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1SNr9i21283; Thu, 28 Feb 2002 15:53:10 -0800 (PST) Received: from eburger (ANice-102-2-1-235.abo.wanadoo.fr [193.252.60.235]) by duck.mail.pas.earthlink.net (8.9.3/8.9.3) with ESMTP id PAA19230; Thu, 28 Feb 2002 15:53:11 -0800 (PST) Reply-To: From: "Eric Burger" To: , "IETF UM" , Subject: FW: [VPIM] I-D ACTION:draft-burger-imap-chanuse-00.txt Date: Thu, 28 Feb 2002 18:52:58 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0091_01C1C089.23B60AF0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_0091_01C1C089.23B60AF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit This draft may be of interest to your groups. A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IMAP CHANNEL Use Cases Author(s) : E. Burger Filename : draft-burger-imap-chanuse-00.txt Pages : 7 Date : 27-Feb-02 This document describes different use cases for using the IMAP CHANNEL facility. Discussion of this and related drafts are on the IMAP Voice list. To subscribe, send the message 'subscribe' to ietf-imap-voice-request@imc.org . A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-burger-imap-chanuse-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-burger-imap-chanuse-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-burger-imap-chanuse-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. Received: by above.proper.com (8.11.6/8.11.3) id g1RFxwh26359 for ietf-imapext-bks; Wed, 27 Feb 2002 07:59:58 -0800 (PST) Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1RFxv326355 for ; Wed, 27 Feb 2002 07:59:57 -0800 (PST) Received: from socrates.cyrusoft.com (localhost [127.0.0.1]) by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id KAA16939 for ; Wed, 27 Feb 2002 10:57:27 -0500 (EST) Date: Wed, 27 Feb 2002 10:59:57 -0500 From: Cyrus Daboo To: IMAP Extensions WG Subject: I-D ACTION:draft-daboo-imap-annotatemore-00.txt (fwd) Message-ID: <2147483647.1014807597@socrates.cyrusoft.com> X-Mailer: Mulberry/3.0.0d3 (Mac OS/PPC) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: FYI The following draft is a private submission that describes an annotation extension that allows annotations on mailboxes and the server and is meant to be a complement to the message annotation draft. Any comments are welcome... ---------- Forwarded Message ---------- Date: Wednesday, February 27, 2002 7:23 AM -0500 From: Internet-Drafts@ietf.org To: IETF-Announce Subject: I-D ACTION:draft-daboo-imap-annotatemore-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IMAP ANNOTATEMORE Extension Author(s) : C. Daboo Filename : draft-daboo-imap-annotatemore-00.txt Pages : 14 Date : 26-Feb-02 The ANNOTATEMORE extension to the Internet Message Access Protocol [IMAP4] permits clients and servers to maintain 'metadata' on IMAP4 servers. This document describes two 'profiles' for mailbox and server metadata. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-daboo-imap-annotatemore-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-daboo-imap-annotatemore-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-daboo-imap-annotatemore-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. ---------- End Forwarded Message ---------- -- Cyrus Daboo Received: by above.proper.com (8.11.6/8.11.3) id g1OH4db19712 for ietf-imapext-bks; Sun, 24 Feb 2002 09:04:39 -0800 (PST) Received: from duck.mail.pas.earthlink.net (duck.mail.pas.earthlink.net [207.217.121.117]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1OH48319702 for ; Sun, 24 Feb 2002 09:04:08 -0800 (PST) Received: from eburger (ANice-102-2-1-96.abo.wanadoo.fr [193.252.60.96]) by duck.mail.pas.earthlink.net (8.9.3/8.9.3) with ESMTP id JAA26265; Sun, 24 Feb 2002 09:03:57 -0800 (PST) Reply-To: From: "Eric Burger" To: "Cyrus Daboo" , "Jutta Degener" Cc: Subject: RE: More SORT keys Date: Sun, 24 Feb 2002 12:03:46 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <847389664.1008261016@70-202-131-12.bellhead.com> Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: That's fine, so long as we use messagehint as an example, as it WILL be used. -----Original Message----- From: owner-ietf-imapext@mail.imc.org [mailto:owner-ietf-imapext@mail.imc.org]On Behalf Of Cyrus Daboo Sent: Thursday, December 13, 2001 6:30 PM To: Jutta Degener Cc: ietf-imapext@imc.org Subject: Re: More SORT keys --On Thursday, December 13, 2001 3:12 PM -0800 Jutta Degener wrote: > Maybe, rather than defining an specific extended feature set associated > with a SORT2 capability, we could do something along the lines of a > SORT=FOO,BAR,BAZ capability? > > Then new drafts that only define specific sorting rules can define SORT > capabilities (e.g., "MESSAGEHINT") that a server can announce without > requiring an update to SORT itself. > > Just an idea. I think that would be a fine solution. The question is whether this group would want to define any of these now, or simply require the the current sort document to indicate that this extensibility is possible. -- Cyrus Daboo Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1MBL2Z19567 for ietf-imapext-bks; Fri, 22 Feb 2002 03:21:02 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1MBL0319548 for ; Fri, 22 Feb 2002 03:21:00 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27151; Fri, 22 Feb 2002 06:20:57 -0500 (EST) Message-Id: <200202221120.GAA27151@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ietf-imapext@imc.org, vpim@lists.neystadt.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-vaudreuil-um-issues-00.txt Date: Fri, 22 Feb 2002 06:20:56 -0500 Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Messaging profile for telephone-based Messaging clients Author(s) : G. Vaudreuil Filename : draft-vaudreuil-um-issues-00.txt Pages : 12 Date : 21-Feb-02 This document discussed issues and requirements for a profile of the IMAP 4, message submission, and notification protocols for use by telephone user interfaces delivering the traditional voice mail user experience. Experience with IMAP 4 and voice mail systems has shown quite a few limitations that may be addressed by protocol extensions and standardized conventions between clients and servers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-vaudreuil-um-issues-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-vaudreuil-um-issues-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-vaudreuil-um-issues-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: <20020221155809.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-vaudreuil-um-issues-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-vaudreuil-um-issues-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020221155809.I-D@ietf.org> --OtherAccess-- --NextPart-- Received: by above.proper.com (8.11.6/8.11.3) id g1M6cv813887 for ietf-imapext-bks; Thu, 21 Feb 2002 22:38:57 -0800 (PST) Received: from Ikkoku-Kan.Panda.COM (peter@ikkoku-kan.panda.com [206.124.149.114]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1M6ct313882 for ; Thu, 21 Feb 2002 22:38:55 -0800 (PST) Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id WAA24755; Thu, 21 Feb 2002 22:38:55 -0800 (PST) Date: Thu, 21 Feb 2002 21:23:20 -0800 (PST) From: Mark Crispin Subject: Re: more on ACL2 To: Lawrence Greenfield cc: IMAP Extensions WG In-Reply-To: <200202220519.g1M5JeYJ016976@smtp5.andrew.cmu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Fri, 22 Feb 2002 00:19:40 -0500, Lawrence Greenfield wrote: > I disagree with almost all of the below. All of these complicate > existing ACL implementations. Many of them aren't even possible for > servers that have external authentication or authorization sources > that aren't tightly coupled to the IMAP server. Somehow, we must fix the missing functionality in IMAP ACL. Failure will result in multiple incompatible IMAP ACL specifications. IESG has already said that this will prevent the standardization of any IMAP ACL specification. Complexity has a cost, but this complexity is necessary in order to make ACL generic enough to be implementable on some platforms. We must pay this cost now, because in the past not enough attention was paid to multi-platform implementability. My proposal is an attempt to define the missing functionality in a manner which (1) is generic and not specific to any particular operating system, (2) does not create any new mandates for existing AFS-based implementations. I have not seen any other proposal that addresses the problem. I would be very happy to see a counter-proposal which also addresses the problem. Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1M5JiL12466 for ietf-imapext-bks; Thu, 21 Feb 2002 21:19:44 -0800 (PST) Received: from smtp5.andrew.cmu.edu (SMTP5.ANDREW.CMU.EDU [128.2.10.85]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1M5Jh312462 for ; Thu, 21 Feb 2002 21:19:43 -0800 (PST) Received: from dunbar.rem.cmu.edu (DUNBAR.REM.CMU.EDU [128.2.4.197]) by smtp5.andrew.cmu.edu (8.12.2.Beta3/8.12.2.Beta3) with ESMTP id g1M5JeYJ016976; Fri, 22 Feb 2002 00:19:40 -0500 Date: Fri, 22 Feb 2002 00:19:40 -0500 Message-Id: <200202220519.g1M5JeYJ016976@smtp5.andrew.cmu.edu> From: Lawrence Greenfield X-Mailer: BatIMail version 3.2 To: IMAP Extensions WG In-reply-to: Subject: Re: more on ACL2 References: Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I disagree with almost all of the below. All of these complicate existing ACL implementations. Many of them aren't even possible for servers that have external authentication or authorization sources that aren't tightly coupled to the IMAP server. Larry Date: Thu, 21 Feb 2002 16:00:10 -0800 (PST) From: Mark Crispin There needs to be a way to identify, per-mailbox, what identifiers are valid. There needs to be a way to change the identifier of an existing ACL. There needs to be a way to know if an ACL can be added or an existing ACL can be removed. Consider a fixed number of ACLs which can be modified (and their identifiers altered), but no ACL can be added or removed. A lot of this may be done by means of clever naming, but that naming scheme needs to be standardized. I'm starting to think that a "$" prefix isn't really the right thing, that instead, we need some sort of type=value identifier. GETACL does not distinguish between tied and untied rights. This is because of its syntax. Better to follow the rest of IMAP and use S-expression type syntax for all ACLs, e.g. "(" identifier SPACE rights *(SPACE rights) ")" Example: C: A002 GETACL INBOX S: * ACL INBOX (user=fred l r wipsextda)(group=staff l r)(anyone l) S: A002 OK GETACL completed Note, however, that I can not use "user=". I really need two different kinds of groups, one which is per-mailbox and one which is global. Also, it's important that anonymous *NOT* be part of anyone. Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1M0HGb05927 for ietf-imapext-bks; Thu, 21 Feb 2002 16:17:16 -0800 (PST) Received: from Ikkoku-Kan.Panda.COM (satori@ikkoku-kan.panda.com [206.124.149.114]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1M0HE305923 for ; Thu, 21 Feb 2002 16:17:14 -0800 (PST) Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id QAA23245; Thu, 21 Feb 2002 16:17:14 -0800 (PST) Date: Thu, 21 Feb 2002 16:00:10 -0800 (PST) From: Mark Crispin Subject: more on ACL2 To: IMAP Extensions WG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: There needs to be a way to identify, per-mailbox, what identifiers are valid. There needs to be a way to change the identifier of an existing ACL. There needs to be a way to know if an ACL can be added or an existing ACL can be removed. Consider a fixed number of ACLs which can be modified (and their identifiers altered), but no ACL can be added or removed. A lot of this may be done by means of clever naming, but that naming scheme needs to be standardized. I'm starting to think that a "$" prefix isn't really the right thing, that instead, we need some sort of type=value identifier. GETACL does not distinguish between tied and untied rights. This is because of its syntax. Better to follow the rest of IMAP and use S-expression type syntax for all ACLs, e.g. "(" identifier SPACE rights *(SPACE rights) ")" Example: C: A002 GETACL INBOX S: * ACL INBOX (user=fred l r wipsextda)(group=staff l r)(anyone l) S: A002 OK GETACL completed Note, however, that I can not use "user=". I really need two different kinds of groups, one which is per-mailbox and one which is global. Also, it's important that anonymous *NOT* be part of anyone. Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1LGSAp23336 for ietf-imapext-bks; Thu, 21 Feb 2002 08:28:10 -0800 (PST) Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1LGS8323327 for ; Thu, 21 Feb 2002 08:28:08 -0800 (PST) Received: from PLATO (localhost [127.0.0.1]) by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id LAA12288; Thu, 21 Feb 2002 11:23:01 -0500 (EST) Date: Thu, 21 Feb 2002 11:24:42 -0500 From: Cyrus Daboo To: Alexey Melnikov , Pete Resnick cc: ietf-imapext@imc.org Subject: Re: Do we need to meet? Message-ID: <846929059.1014290682@PLATO> In-Reply-To: <3C749EDF.B057410A@messagingdirect.com> References: <3C749EDF.B057410A@messagingdirect.com> X-Mailer: Mulberry/2.2.0b2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Hi, --On Thursday, February 21, 2002 12:16 AM -0700 Alexey Melnikov wrote: > What happened to mailbox annotations and "ACL ids to Friendly Names" (the > draft that Chris was working on)? I will be submitting a draft on mailbox and server annotations before the deadline for new drafts tomorrow. I was waiting on comments on the message annotate draft before proceeding with this as it does depend on some aspects of message annotations (though it doesn't require implementing message annotations to do mailbox/server annotations). This will be a private submission since its not on the IMAPext charter. I will also be updating the message annotation document before the cut-off for existing drafts. At that point we need to decide on the last-call status. -- Cyrus Daboo Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1LGIfT22792 for ietf-imapext-bks; Thu, 21 Feb 2002 08:18:41 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1LGIe322788 for ; Thu, 21 Feb 2002 08:18:40 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g1LGFsj13582; Thu, 21 Feb 2002 09:15:54 -0700 Message-ID: <3C749EDF.B057410A@messagingdirect.com> Date: Thu, 21 Feb 2002 00:16:47 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Pete Resnick CC: ietf-imapext@imc.org Subject: Re: Do we need to meet? References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Pete Resnick wrote: > On 2/14/02 at 5:11 PM -0600, I wrote: > > >It looks to me that ANNOTATE is getting close. CONDSTORE doesn't > >seem to have too much in the way of open issues. I'm not sure what > >the state of ACL is. Do we have reason to meet in Minneapolis or not? > > I will take this silence to mean that we don't have to meet. Any objections? I guess everybody want to go to Japan instead of Minneapolis ;-). I have more unresolved issues with ACL and CONDSTORE I will submit to the mailing list shortly. I would like to ask people to share their opinion whether these documents are ready for Last Call. What happened to mailbox annotations and "ACL ids to Friendly Names" (the draft that Chris was working on)? I will be attending Minneapolis anyway, so I am curious who is going to attend. Please reply privately. Regards, Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: by above.proper.com (8.11.6/8.11.3) id g1LC1bZ08319 for ietf-imapext-bks; Thu, 21 Feb 2002 04:01:37 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1LC1Z308315 for ; Thu, 21 Feb 2002 04:01:35 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14111; Thu, 21 Feb 2002 07:01:34 -0500 (EST) Message-Id: <200202211201.HAA14111@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-ietf-imapext-acl-03.txt Date: Thu, 21 Feb 2002 07:01:33 -0500 Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --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 : IMAP4 ACL extension Author(s) : A. Melnikov Filename : draft-ietf-imapext-acl-03.txt Pages : 9 Date : 20-Feb-02 The ACL extension of the Internet Message Access Protocol [IMAP4] permits access control lists to be manipulated through the IMAP protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imapext-acl-03.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-ietf-imapext-acl-03.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-ietf-imapext-acl-03.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: <20020220135109.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imapext-acl-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imapext-acl-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020220135109.I-D@ietf.org> --OtherAccess-- --NextPart-- Received: by above.proper.com (8.11.6/8.11.3) id g1L67g529990 for ietf-imapext-bks; Wed, 20 Feb 2002 22:07:42 -0800 (PST) Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1L67e329986 for ; Wed, 20 Feb 2002 22:07:41 -0800 (PST) Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1L67exY029272 for ; Wed, 20 Feb 2002 22:07:45 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Wed Feb 20 22:07:39 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1L67akx018673 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Feb 2002 22:07:39 -0800 Date: Wed, 20 Feb 2002 21:45:44 -0800 (PST) From: Mark Crispin Subject: ACL2 To: IMAP Extensions WG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Since ACL2 can be incompatible from ACL, we should define a replacement identifier for "anyone" that does not conflict with a login id of "anyone". As matters stand now, the text: [...] The identifier "anyone" is reserved to refer to the universal identity (all authentications, including anonymous). All user name strings accepted by the LOGIN or AUTHENTICATE commands to authenticate to the IMAP server are reserved as identifiers for the corresponding user. is self-contradictory. Delete "PARTIAL" as a permitted operation of the "r" right. PARTIAL is a deprecated feature of RFC1730 which should now be extinct. The "d" right should first be described as "RFC 2086 compatible delete right" and then its semantics listed. Unfortunately, the given semantics don't work. What if one or more of the "x", "e", or "t" rights can not be set or cleared? Suggest changing the MUST to SHOULD. Consider deprecating the "d" right entirely for an ACL2-only server. Paragraph describing negative rights should make it clear that a negative right is not the same thing as a DELETACL. ACL2=MOST-SPECIFIC is a big improvement. Is ACL2=UNION really still necessary? Wouldn't it be better to do this in the semantics of the naming? Note that the addition of ACL2=MOST-SPECIFIC renders certain parts of my proposed naming system moot. However, there are other part of it which remain desirable, including: . new commands to access and define groups . separate "world" vs. "anonymous" access Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1L18bR23172 for ietf-imapext-bks; Wed, 20 Feb 2002 17:08:37 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1L18Z323168 for ; Wed, 20 Feb 2002 17:08:35 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g1L1Arj07055; Wed, 20 Feb 2002 18:10:58 -0700 Message-ID: <3C74432D.CAD507E9@messagingdirect.com> Date: Wed, 20 Feb 2002 17:45:33 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Arnt Gulbrandsen CC: Cyrus Daboo , IMAP Extensions WG Subject: Re: ACL2 backward compatability References: <2147483647.1013770289@socrates.cyrusoft.com> <3C6D45D6.AA1141B8@messagingdirect.com> <20020215190214.Q22712@witt-witt.caldera.de> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Arnt Gulbrandsen wrote: > Alexey Melnikov > > IMHO, only if a particular server implementation uses "$" prefix for groups and > > other special identifiers. > > The draft lists the incompatibilities; should it also explictly recommend > that servers advertise "ACL" if these incompatibilities don't apply in > that server's case? I've just added this to the version 03 I've sent yesterday. Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: by above.proper.com (8.11.6/8.11.3) id g1KH75n12219 for ietf-imapext-bks; Wed, 20 Feb 2002 09:07:05 -0800 (PST) Received: from episteme-software.com (champdsl-25-66.mcleodusa.net [216.43.25.66]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1KH73312215 for ; Wed, 20 Feb 2002 09:07:03 -0800 (PST) Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with ESMTP (Eudora Internet Mail Server 3.1) for ; Wed, 20 Feb 2002 11:07:00 -0600 Mime-Version: 1.0 X-Sender: resnick@resnick1.qualcomm.com (Unverified) Message-Id: In-Reply-To: References: X-Mailer: Eudora [Macintosh version 5.1fc3] Date: Wed, 20 Feb 2002 11:06:54 -0600 To: ietf-imapext@imc.org From: Pete Resnick Subject: Re: Do we need to meet? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On 2/14/02 at 5:11 PM -0600, I wrote: >It looks to me that ANNOTATE is getting close. CONDSTORE doesn't >seem to have too much in the way of open issues. I'm not sure what >the state of ACL is. Do we have reason to meet in Minneapolis or not? I will take this silence to mean that we don't have to meet. Any objections? pr -- Pete Resnick QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 Received: by above.proper.com (8.11.6/8.11.3) id g1FI3Lf09447 for ietf-imapext-bks; Fri, 15 Feb 2002 10:03:21 -0800 (PST) Received: from witt-witt.caldera.de (witt-witt.caldera.de [195.143.241.43]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1FI3H309443 for ; Fri, 15 Feb 2002 10:03:18 -0800 (PST) Received: (from arnt@localhost) by witt-witt.caldera.de (8.11.6/8.11.6) id g1FI2Ep27048; Fri, 15 Feb 2002 19:02:15 +0100 Date: Fri, 15 Feb 2002 19:02:14 +0100 From: Arnt Gulbrandsen To: Alexey Melnikov Cc: Cyrus Daboo , IMAP Extensions WG Subject: Re: ACL2 backward compatability Message-ID: <20020215190214.Q22712@witt-witt.caldera.de> References: <2147483647.1013770289@socrates.cyrusoft.com> <3C6D45D6.AA1141B8@messagingdirect.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C6D45D6.AA1141B8@messagingdirect.com> Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Alexey Melnikov > IMHO, only if a particular server implementation uses "$" prefix for groups and > other special identifiers. The draft lists the incompatibilities; should it also explictly recommend that servers advertise "ACL" if these incompatibilities don't apply in that server's case? --Arnt Received: by above.proper.com (8.11.6/8.11.3) id g1FHSe808475 for ietf-imapext-bks; Fri, 15 Feb 2002 09:28:40 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1FHSc308470 for ; Fri, 15 Feb 2002 09:28:38 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g1FHV5j19789; Fri, 15 Feb 2002 10:31:05 -0700 Message-ID: <3C6D45D6.AA1141B8@messagingdirect.com> Date: Fri, 15 Feb 2002 10:31:02 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Cyrus Daboo CC: IMAP Extensions WG Subject: Re: ACL2 backward compatability References: <2147483647.1013770289@socrates.cyrusoft.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Cyrus Daboo wrote: > I think the current ACL2 draft has backwards compatibility with the old ACL > draft wrt the the defined ACL bits. So should the current draft require > servers to also advertise 'ACL' in the capability response as well as > ACL2=xxx to allow existing ACL clients to interoperate? I would argue yes. IMHO, only if a particular server implementation uses "$" prefix for groups and other special identifiers. Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g1FFpVd04426 for ietf-imapext-bks; Fri, 15 Feb 2002 07:51:31 -0800 (PST) Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1FFpU304421 for ; Fri, 15 Feb 2002 07:51:30 -0800 (PST) Received: from socrates.cyrusoft.com (localhost [127.0.0.1]) by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id KAA07538 for ; Fri, 15 Feb 2002 10:49:03 -0500 (EST) Date: Fri, 15 Feb 2002 10:51:29 -0500 From: Cyrus Daboo To: IMAP Extensions WG Subject: ACL2 backward compatability Message-ID: <2147483647.1013770289@socrates.cyrusoft.com> X-Mailer: Mulberry/3.0.0d2 (Mac OS/PPC) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: I think the current ACL2 draft has backwards compatibility with the old ACL draft wrt the the defined ACL bits. So should the current draft require servers to also advertise 'ACL' in the capability response as well as ACL2=xxx to allow existing ACL clients to interoperate? I would argue yes. -- Cyrus Daboo Received: by above.proper.com (8.11.6/8.11.3) id g1FFmtf04300 for ietf-imapext-bks; Fri, 15 Feb 2002 07:48:55 -0800 (PST) Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1FFmr304296 for ; Fri, 15 Feb 2002 07:48:53 -0800 (PST) Received: from socrates.cyrusoft.com (localhost [127.0.0.1]) by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id KAA07502 for ; Fri, 15 Feb 2002 10:46:26 -0500 (EST) Date: Fri, 15 Feb 2002 10:48:52 -0500 From: Cyrus Daboo To: IMAP Extensions WG Subject: ACL and STATUS Message-ID: <2147483647.1013770132@socrates.cyrusoft.com> X-Mailer: Mulberry/3.0.0d2 (Mac OS/PPC) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The current ACL rfc and the latest draft for the updated version don't indicate which ACL bit controls the behaviour of the STATUS command. I would guess that at least read 'r' access is required in order to get status information on a mailbox. Can we have STATUS explicitly listed as one of the commands available for the 'r' bit? The other option would be to allow status with only the 'l' bit, which currently allows LIST/LSUB for a mailbox. If we ever get around to extending list, I believe one of the proposals did have list returning the equivalent of status information, so there might be some awkward interaction with ACL on that. -- Cyrus Daboo Received: by above.proper.com (8.11.6/8.11.3) id g1ENBIh00233 for ietf-imapext-bks; Thu, 14 Feb 2002 15:11:18 -0800 (PST) Received: from episteme-software.com (champdsl-25-66.mcleodusa.net [216.43.25.66]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g1ENBH300227 for ; Thu, 14 Feb 2002 15:11:17 -0800 (PST) Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with ESMTP (Eudora Internet Mail Server 3.1) for ; Thu, 14 Feb 2002 17:11:14 -0600 Mime-Version: 1.0 X-Sender: resnick@resnick1.qualcomm.com (Unverified) Message-Id: X-Mailer: Eudora [Macintosh version 5.1fc3] Date: Thu, 14 Feb 2002 17:11:11 -0600 To: ietf-imapext@imc.org From: Pete Resnick Subject: Do we need to meet? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: It looks to me that ANNOTATE is getting close. CONDSTORE doesn't seem to have too much in the way of open issues. I'm not sure what the state of ACL is. Do we have reason to meet in Minneapolis or not? pr -- Pete Resnick QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g15N22x14956 for ietf-imapext-bks; Tue, 5 Feb 2002 15:02:02 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g15N21314951 for ; Tue, 5 Feb 2002 15:02:01 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g15N21j06772; Tue, 5 Feb 2002 16:02:01 -0700 Message-ID: <3C60646B.A5AFCEF6@messagingdirect.com> Date: Tue, 05 Feb 2002 16:02:03 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: IMAP Extensions WG Subject: Re: I-D ACTION:draft-melnikov-imap-condstore-06.txt References: <200202051451.JAA01738@ietf.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is the second revision submitted this year. Changes from -05 to -06: 1. Replaced "/message/flags/system" with "/message/flags" to match ANNOTATE draft. 2. Extended FETCH/SEARCH/SORT syntax to allow for specifying whether an operation should be performed on a shared or a private annotation (or both). 3. Corrected several examples. Changes from -04 to -05: 1. Added support for SORT extension. 2. Multiple language/spelling fixes by Randall Gellens. There is one major open issue left: MODSEQ fetch response as the result of STORE/UID STORE of a flag in any IMAP session: what _type_ of modseq should be returned: private, shared, both? This is related to the change 2) between 05 and 06. Comments? Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: by above.proper.com (8.11.6/8.11.3) id g15I0AM02848 for ietf-imapext-bks; Tue, 5 Feb 2002 10:00:10 -0800 (PST) Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g15I08302843 for ; Tue, 5 Feb 2002 10:00:08 -0800 (PST) Received: from messagingdirect.com (gagarin.esys.ca [198.161.92.84]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id g15I07j02995; Tue, 5 Feb 2002 11:00:07 -0700 Message-ID: <3C601DA9.800398B5@messagingdirect.com> Date: Tue, 05 Feb 2002 11:00:10 -0700 From: Alexey Melnikov Organization: ACI WorldWide / MessagingDirect X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: ietf-imapext@imc.org Subject: Re: I-D ACTION:draft-ietf-imapext-acl-02.txt References: <200202051451.JAA01899@ietf.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: A new revision is out. Major changes in this version: 1). Changed ACL capability name to ACL2= Added registry for the rules. Described two rules: UNION (union of the positive minus union of negative), MOST-SPECIFIC (most specific identifier describes the rights). 2). Added "t" right for performing STORE \Deleted. Changed "d" to be a macro for "x", "t" and "e". Alexey Melnikov __________________________________________ R & D, ACI Worldwide (formerly MessagingDirect Ltd.) phone 780.424.4922 x357 I speak for myself only, not for my employer. __________________________________________ Received: by above.proper.com (8.11.6/8.11.3) id g15EpoM23056 for ietf-imapext-bks; Tue, 5 Feb 2002 06:51:50 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g15Epm323052 for ; Tue, 5 Feb 2002 06:51:48 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01899; Tue, 5 Feb 2002 09:51:46 -0500 (EST) Message-Id: <200202051451.JAA01899@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-ietf-imapext-acl-02.txt Date: Tue, 05 Feb 2002 09:51:46 -0500 Sender: owner-ietf-imapext@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --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 : IMAP4 ACL extension Author(s) : A. Melnikov Filename : draft-ietf-imapext-acl-02.txt Pages : 9 Date : 04-Feb-02 The ACL extension of the Internet Message Access Protocol [IMAP4] permits access control lists to be manipulated through the IMAP protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imapext-acl-02.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-ietf-imapext-acl-02.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-ietf-imapext-acl-02.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: <20020204134227.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imapext-acl-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imapext-acl-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020204134227.I-D@ietf.org> --OtherAccess-- --NextPart--