[Top] [All Lists]

Re: I-D ACTION:draft-ietf-sieve-notify-07.txt

2007-02-26 04:59:15

Internet-Drafts(_at_)ietf(_dot_)org wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of 
the IETF.

        Title           : Sieve Extension: Notifications
        Author(s)       : A. Melnikov, et al.
        Filename        : draft-ietf-sieve-notify-07.txt
        Pages           : 18
        Date            : 2007-2-21
Users go to great lengths to be notified as quickly as possible that
  they have received new mail.  Most of these methods involve polling
  to check for new messages periodically.  A push method handled by the
  final delivery agent gives users quicker notifications and saves
  server resources.  This document does not specify the notification
  method but it is expected that using existing instant messaging
  infrastructure such as XMPP, or SMS messages will be popular.  This
  draft describes an extension to the Sieve mail filtering language
  that allows users to give specific rules for how and when
  notifications should be sent.

A URL for this Internet-Draft is:
Barry and I recently submitted -07. We believe this version addresses all issues brought up during WGLC.

I would like to issue an additional 1 week WGLC on this version of the document.

In particular, I would like to bring people's attention to the following 3 changes:

1). New notify_method_capability test.

2). One major editorial change is the removal of extract_text test, as per WG discussion. The replacement test or action is more likely to move to the MIME loops document, but this decision is not final.

3). Regarding describing interaction of the notify action parameters with URI parameters in the method parameter: Looking through comments received during WGLC, I found no single agreeable solution. Pretty much everybody wanted different behavior. So sieve-notify was updated to list available choices, but not prescribe any specific behavior, which is left up to specifications describing notification methods. Once the new Sieve notify is deployed and we get some implementation experience with different notification methods, some consensus might emerge. At which point sieve-notify-bis can prescribe a specific behavior.

<Prev in Thread] Current Thread [Next in Thread>