headers
Internet-Drafts | 2 Jul 2002 12:33
Picon
Favicon

I-D ACTION:draft-shapira-snap-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: Simple Notification and Alarm Protocol (SNAP)
	Author(s)	: N. Shapira 
	Filename	: draft-shapira-snap-04.txt
	Pages		: 30
	Date		: 01-Jul-02
	
This memo suggests a protocol for messaging notification in
which a messaging system (e.g. email server, voice mail system, 
etc.) notifies a notification service, and through it the user,
that changes have occurred in a user's mailbox (new message
arrived, mailbox is full, etc.). The protocol aims to provide the
end-user with unified notification of events occurring on different
messaging systems.
A mailing list has been established to discuss this draft and
promote the issue of Notification to RFC. To subscribe, send
email with 'subscribe snap' to majordomo <at> lists.neystadt.org
or using web at http://www.neystadt.org/cgi-bin/majordomo.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-shapira-snap-04.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-shapira-snap-04.txt".
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 2 Jul 2002 12:32
Picon
Favicon

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

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: IMAP4 rev1 û STATUS-COUNTERS Extension
	Author(s)	: J. Neystadt, A. Melnikov
	Filename	: draft-neystadt-imap-status-counters-01.txt
	Pages		: 10
	Date		: 01-Jul-02
	
The STATUS-COUNTERS extends IMAP4rev1Æs STATUS command. This 
extension adds the following functionality: 
Enable MUA to get mailbox counters per groups of messages, grouped 
according to the value of Message-Context header field. For 
example, the MUA can find out that the Inbox contains 5 unseen fax 
messages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-neystadt-imap-status-counters-01.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-neystadt-imap-status-counters-01.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
(Continue reading)

Permalink | Reply | 7 comments |
headers
Internet-Drafts | 3 Jul 2002 12:30
Picon
Favicon

I-D ACTION:draft-ietf-imapext-acl-05.txt

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-05.txt
	Pages		: 9
	Date		: 02-Jul-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-05.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-05.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.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Alexey Melnikov | 5 Jul 2002 23:59

Re: I-D ACTION:draft-ietf-imapext-acl-05.txt


Internet-Drafts <at> ietf.org wrote:

> 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-05.txt
>         Pages           : 9
>         Date            : 02-Jul-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-05.txt
>

List of changes (can be found in Appendix):

  21. Added mail client security considerations when dealing with special
      identifier "anyone".

  22. Clarified that negative rights are not the same as DELETEACL (ACL DELETE).

  23. Removed the requirement to check the "r" right for CHECK, SEARCH and
      FETCH, as this is required for SELECT/EXAMINE to be successful.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rob Siemborski | 12 Jul 2002 19:53
Picon

ANNOTATEMORE Wildcards


I've been doing some work on our implementation of ANNOTATEMORE, and I've
been having trouble deciding what to do with some globs.

My concerns focus mostly around the integration of the mailbox names into
entry names.  If '.' is being used as the mailbox hierarchy delimiter,
does % fail to match on '/' and '.'?  Does it include or exclude '}'?

Does '/mailbox/%/foo' resolve to the same thing as '/mailbox/{*}/foo' or
'/mailbox/{%}/foo'

What if only one of the braces is missing?

Does '/mailbox/{user.%/foo' work equivilantly to '/mailbox/{user.*}/foo'
or '/mailbox/{user.%}/foo'?

Also, is it really necessary to allow '/mail%/{user.foo}/foo' as a
pattern?  Personally, I don't see any use for wildcards at all in the
first level of mailbox and server annotations, especially since mailbox
annotations have the second level of mailbox names before you get to the
actual entry names.

I propose the following change:

Allow wildcards only in the following locations (denoted by the * below):

/mailbox/{*}/*
/server/*

For mailbox annotations, inside of the braces % will refuse to match the
(Continue reading)

Permalink | Reply | 0 comments |

Gmane