Internet Engineering Task Force (IETF) R. George
Request for Comments: 6132 B. Leiba
Category: Standards Track Huawei Technologies
ISSN: 2070-1721 July 2011
Sieve Notification Using Presence Information
Abstract
This is a further extension to the Sieve mail filtering language
Notification extension, defining presence information that may be
checked through the notify_method_capability feature.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6132.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
George & Leiba Standards Track [Page 1]RFC 6132 Sieve Notify: Presence July 2011Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology Used in This Document . . . . . . . . . . . . . 2
2. Testing Presence Information . . . . . . . . . . . . . . . . . 2
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . . 8
1. Introduction
Sometimes, it's desirable to tailor Sieve [RFC5228] notifications to
a user's current situation. Presence information provides some
information about the user that would be useful to have access to in
these cases. The Notification extension [RFC5435] defines a
mechanism to test for presence (the notify_method_capability
feature), and defines one test for presence (the "online"
notification-capability, described in Section 5 of RFC 5435). This
extension defines more presence tests by registering additional
notification-capability parameters in the IANA registry, allowing
testing of a wider variety of presence information.
1.1. Terminology Used in This Document
The upper-case 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
[RFC2119].
2. Testing Presence Information
This extension uses the notify_method_capability test, as defined in
the Sieve [RFC5228] Notify extension [RFC5435], to test presence
information. When a Sieve event occurs (mail arrives) for a user, a
Sieve script running on behalf of that user can present the user's
presence URI (in the "notification-uri" parameter) and test a
specific item of notification presence as defined below (in the
"notification-capability" parameter) against one or more values (in
the "key-list" parameter).
George & Leiba Standards Track [Page 2]RFC 6132 Sieve Notify: Presence July 2011
This document defines an initial set of items of notification
presence, which may be specified in the notification-capability
parameter. It is expected that future extensions will add additional
datatracker.ietf.org