Sieve Notification Mechanism: SIP MESSAGE
draft-melnikov-sieve-notify-sip-message-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alexey Melnikov , Henning Schulzrinne , Qian Sun | ||
| Last updated | 2010-04-08 (Latest revision 2008-02-18) | ||
| Replaced by | draft-ietf-sieve-notify-sip-message | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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].
Authors
Alexey Melnikov
Henning Schulzrinne
Qian Sun
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)