[Fwd: IMAPEXT bar BOF in Minneapolis]

As we just discussed with Pere, we should also discuss CHANNEL and
BINARY.

-------- Original Message --------
Subject: IMAPEXT bar BOF in Minneapolis
Date: Sun, 17 Mar 2002 18:36:38 -0700
From: Alexey Melnikov <[email protected]>
Organization: ACI WorldWide / MessagingDirect
To: IMAP Extensions WG <[email protected]>


Monday around 16.30 near the message board. (This should start after
SASL bar BOF, I believe a lot of people interested in IMAPEXT will
attend SASL as well).

Tentative agenda:

IMAP ACL2 issues (in no particular order):
 1). REPLACEACL
 2). Setting an ACL on a mailbox hierarchy.
 3). How to encode user names starting with "-" and "$".
 4). 'r' to read QUOTA and ACL?
 5). 'a' to read ACL as well.
 6). Which set of rights correspond to READ-WRITE?
      Cyrus and our MessagingDirect server: if either "w" or "t" are
allowed for the current user
      Communigate: when only "s" allowed.
 7). Subscription and listing:
      LIST - 'l' right
      LSUB - 'l'? (if subscription is not an attribute of a mailbox?)
      SUBSCRIBE: Cyrus requires either 'l' or 'r'. Communigate requires
no rights.
      UNSUBSCRIBE - always allowed?
 8). COPY MUST check 'w'/'t'/'s' when copying flags? (Make it SHOULD as
no known implementation
     check for 'w'/'d'/'s'?)
 9). ACL and LISTEXT/ANNOTATEMORE:
   Cyrus wrote:
     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.
10). Replace "anonymous" with $anonymous?
11). Separate "world" vs. "anonymous" access

There are more questions but I have to dig them out.

CONDSTORE issues:
 1). How user defined flags (keywords) map to annotations? (Currently
draft suggests to use "-" as prefix).

 2). I had to extend the syntax for FETCH/SEARCH/STORE to allow to
     specify whether private or shared flag should be used
     for the conditional operation. This is a result of a change in one
of the latest ANNOTATE revisions.
     The change removed default annotation type for STORE operation.

 3). What entry-type-resp (i.e. "private" or "shared") should be used in
unsolicited flag responses?
      What about STORE/UID STORE on flags?

 4). SEARCH: MODSEQ XXX OR KEYWORDS $Fff

     Return MODSEQ response code for all found messages (simplest, but
requires that modsequence of every found message is obtained, no
optimizations allowed)? What about SEARCH NOT MODSEQ YYY?

ANNOTATE/ANNOTATEMORE issues.

Regards,
Alexey Melnikov
__________________________________________
R & D, ACI Worldwide/MessagingDirect
Richmond, Surrey, UK
Phone: +44 20 8332 4508

I speak for myself only, not for my employer.
__________________________________________