Sieve Notification Mechanism: SIP MESSAGE

Document Type Replaced Internet-Draft (individual)
Authors Alexey Melnikov  , Henning Schulzrinne  , Qian Sun 
Last updated 2010-04-08 (latest revision 2008-02-18)
Replaced by RFC 6468
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sieve-notify-sip-message
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent over the SIP MESSAGE.Conventions Used in this Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].


Alexey Melnikov (
Henning Schulzrinne (
Qian Sun (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)