Sieve Notification Mechanism: SIP MESSAGE
RFC 6468

Approval announcement
Draft of message to be sent after approval:

From: The IESG <>
To: IETF-Announce <>
Cc: RFC Editor <>,
    sieve mailing list <>,
    sieve chair <>
Subject: Protocol Action: 'Sieve Notification Mechanism: SIP MESSAGE' to Proposed Standard (draft-ietf-sieve-notify-sip-message-08.txt)

The IESG has approved the following document:
- 'Sieve Notification Mechanism: SIP MESSAGE'
  (draft-ietf-sieve-notify-sip-message-08.txt) as a Proposed Standard

This document is the product of the Sieve Mail Filtering Language Working

The IESG contact persons are Pete Resnick and Peter Saint-Andre.

A URL of this Internet Draft is:

Technical Summary

    The Sieve scripting language is used to filter email messages. One action that can be 
executed on matching messages is sending of a notification, which can be sent using 
different mechanisms. This document describes a profile of the Sieve extension for 
notifications, to allow notifications to be sent over SIP MESSAGE.

Working Group Summary

    This extension started as an individual submission in 2007 and was
    adopted as a WG document in 2008. The basic premise has remained the
    same throughout all revisions of the document.
    This extension adds an additional notification method to the SIEVE
    Notify extension (RFC5435) that enables use of SIP as a notification
    mechanism. There were no major issues with the SIEVE aspects of this
    extension, given experience with developing other notification
    mechanisms (already published as RFCs). The one major area of concern
    was the use of the SIP URI itself. Following an initial WG last call
    where this issue was brought up, the authors solicited reviews from
    relevant RAI area experts. The authors' documented the issues in the -03
    draft for further WG discussions which resolved the issues, resulting in
    the current -04 document, which underwent another WG last call.

Document Quality

    There are no known implementations of this extension at present. Various vendors 
have expressed interest in implementing this extension, however it is not currently a 
top priority for any of them.


Document Shepherd: Cyrus Daboo <>
AD: Pete Resnick <>