Network Working Group P. Saint-Andre
Internet-Draft Jabber Software Foundation
Expires: June 8, 2006 A. Melnikov
Isode Limited
December 5, 2005
Sieve Notifications via the Extensible Messaging and Presence Protocol
(XMPP)
draft-saintandre-sieve-notify-xmpp-00
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 8, 2006.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document describes a profile of the Sieve extension for instant
notifications to be used with the Extensible Messaging and Presence
Protocol (XMPP).
Saint-Andre & Melnikov Expires June 8, 2006 [Page 1]
Internet-Draft SIEVE-XMPP December 2005
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Internationalization Considerations . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1 Normative References . . . . . . . . . . . . . . . . . . . 5
6.2 Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . 7
Saint-Andre & Melnikov Expires June 8, 2006 [Page 2]
Internet-Draft SIEVE-XMPP December 2005
1. Introduction
1.1 Overview
[SIEVE-NOTIFY] defines a [SIEVE] extension for instant notifications
to be generated when a new message has arrived in an email inbox. In
particular, [SIEVE-NOTIFY] defines the "notify" action but does not
specify which technology or technologies to use for such
notifications; instead, it leaves the definition of specific
notification methods up to "profiles" of [SIEVE-NOTIFY]. This
document defines one such profile, for the Extensible Messaging and
Presence Protocol (XMPP) as defined in [XMPP].
1.2 Terminology
This document inherits terminology from [SIEVE], [SIEVE-NOTIFY], and
[XMPP].
The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in RFC 2119 [TERMS].
2. Definition
In order to send Sieve notifications to an XMPP entity, the format of
the notify action shall be as follows:
o The ":method" tag MUST be specified and its value MUST be a URI
that conforms to the xmpp URI scheme (as specified in [XMPP-URI])
and that identifies an XMPP account associated with the email
inbox.
o The ":id" tag MAY be specified.
o The ":priority" tag MAY be specified.
o The ":message" tag MAY be specified.
The notify action SHOULD be mapped to XMPP elements and attributes as
follows:
o The notification MUST be an XMPP stanza.
o The value of the ":id" tag SHOULD NOT be translated into XMPP
syntax.
o The value of the ":priority" tag MAY be translated into XMPP
syntax; if it is so translated, it SHOULD be encapsulated as the
value of an [XMPP-SHIM] header named "Priority" and its value
SHOULD be consistent with [RFC1327] (namely, "normal", "non-
urgent", or "urgent").
Saint-Andre & Melnikov Expires June 8, 2006 [Page 3]
Internet-Draft SIEVE-XMPP December 2005
o The value of the ":message" tag MUST be translated into the XML
character data of the XMPP stanza's