Re: I-D ACTION:draft-neystadt-imap-status-counters-00.txt

Hello,

> It certainly does seem to be very much specialized for VPIM, and doesn't
seem
> to make adequate attempt to leverage existing mechanisms.  For example,
why
> not use IMAP keyword flags in association with delivery mechanisms that
set
> those flags, and then just extend STATUS to count other flags besides
\Recent
> and (not) \Seen.

I think your proposal is very good for Unseen and may be Important (new flag
or reuse \Flagged). BTW is \Flagged semantics is really "importance". If I
make my server (by Sieve or other mechanism) turn \Flagged on all messages
with "Importance: High" header, would that be ok. What are other uses for it
today?

Now there is a problem with Message-Context - since it is an extensible list
of values (new ones can be added ad-hoc) then message flags will have to be
added per each of them each time new values are added. In my proposal server
sends response per all detected Message-Contexts. In your way we will have
to introduce some mechanism for MUA to enumerate them. In additoin flags are
not "typed" so MUA can't distinuigh between say $MDNSent and $Fax-Message
which is confusing.

Another issue is that \Seen changes dynamically. So in order to query for
counter of \Seen fax messgase we will have to pass a boolean expression of
flags to this new STATUS extension. For example:

C: STATUS abc COUNTERS[(\Seen AND $Fax-Message) (\Seen AND \Flagged AND
$Fax-Message) ...]

This is long and somewhat cumbersome.

> > In draft-1, could you the non-ascii junk? I see various | and F
> > characters.
>
> I have to echo this comment; I don't know what produced that junk but it
is
> there and it is annoying.

I apologize again.

John Neystadt
[email protected]
http://www.neystadt.org/john/



----------------------------------------------------------
This message was sent to you, since you are subscribed to
[email protected]. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo