draft-ietf-sieve-vacation-seconds-03.txt   rfc6131.txt 
Sieve working group R. George Internet Engineering Task Force (IETF) R. George
Internet-Draft B. Leiba Request for Comments: 6131 B. Leiba
Intended status: Standards Track Huawei Technologies Category: Standards Track Huawei Technologies
Expires: May 27, 2011 November 23, 2010 ISSN: 2070-1721 July 2011
Sieve Vacation Extension: "Seconds" parameter Sieve Vacation Extension: "Seconds" Parameter
draft-ietf-sieve-vacation-seconds-03
Abstract Abstract
This document describes a further extension to the Sieve Vacation This document describes a further extension to the Sieve Vacation
extension, allowing multiple auto-replies to the same sender in a extension, allowing multiple auto-replies to the same sender in a
single day by adding a ":seconds" parameter. single day by adding a ":seconds" parameter.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on May 27, 2011. 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/rfc6131.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology Used in This Document . . . . . . . . . . . . . . 3 1.1. Terminology Used in This Document . . . . . . . . . . . . . 2
2. The ':seconds' Parameter . . . . . . . . . . . . . . . . . . . 2
2. The ':seconds' Parameter . . . . . . . . . . . . . . . . . . 3 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Registration of Sieve Extension . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . . 5
5.1. Registration of Sieve Extension . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
The Sieve [RFC5228] Vacation extension [RFC5230] defines a mechanism The Sieve [RFC5228] Vacation extension [RFC5230] defines a mechanism
to generate automatic replies to incoming email messages. Through to generate automatic replies to incoming email messages. Through
the ":days" parameter, it limits the number of auto-replies to the the ":days" parameter, it limits the number of auto-replies to the
same sender to one per [n] days, for a specified number of days. But same sender to one per [n] days, for a specified number of days. But
there are cases when one needs more granularity, if one would like to there are cases when one needs more granularity, if one would like to
generate "vacation" replies more frequently. generate "vacation" replies more frequently.
skipping to change at page 3, line 30 skipping to change at page 2, line 43
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC "OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119]. 2119 [RFC2119].
2. The ':seconds' Parameter 2. The ':seconds' Parameter
The purpose of the ":seconds" parameter is to specify the minimum The purpose of the ":seconds" parameter is to specify the minimum
time interval (in seconds) between consecutive auto-replies to a time interval (in seconds) between consecutive auto-replies to a
given sender. The ":seconds" value, if specified, is used instead of given sender. The ":seconds" value, if specified, is used instead of
the ":days" value, and works in a similar way (see the Vacation the ":days" value, and works in a similar way (see the Vacation
extension [RFC5230] for details). Only one of ":days" and ":seconds" extension [RFC5230] for details). Only one of ":days" or ":seconds"
is allowed -- use of both parameters in the same vacation action MUST is allowed -- use of both parameters in the same vacation action MUST
result in a Sieve processing error. result in a Sieve processing error.
The capability string associated with this extension is "vacation- The capability string associated with this extension is "vacation-
seconds". Note that "vacation-seconds" implies "vacation", and a seconds". Note that "vacation-seconds" implies "vacation", and a
script with "vacation-seconds" in a "require" list can omit script with "vacation-seconds" in a "require" list can omit
"vacation" from that list. "vacation" from that list.
The time value is specified in seconds, and MUST be greater than or The time value is specified in seconds, and MUST be greater than or
equal to 0 and less than 2**31. All valid values MUST be accepted equal to 0 and less than 2**31. All valid values, from 0 to 2**31,
without error, but sites MAY define a minimum value to actually be MUST be accepted without error. Sites MAY define a minimum effective
used if a smaller value is specified, and/or a maximum value to be value and/or a maximum effective value. If a site chooses to do
used if a larger value is specified. If a site imposes a maximum that:
value, that value MUST be at least 86400 (one day).
1. Call the value specified "v(spec)".
2. Call the minimum effective value "v(min)".
3. Call the maximum effective value "v(max)".
4. Call the actual effective value used by the processor "v(eff)".
5. The following apply for determining v(eff):
* If 0 <= v(spec) < v(min), then v(eff) = v(min).
* If v(min) <= v(spec) <= v(max), then v(eff) = v(spec).
* If v(max) < v(spec) <= 2**31, then v(eff) = v(max).
If a site imposes a maximum effective value, that value MUST be at
least 86400 (one day).
If ":seconds 0" is specified and used, it means that all auto-replies If ":seconds 0" is specified and used, it means that all auto-replies
are sent, and no attempt is made to suppress consecutive replies. are sent, and no attempt is made to suppress consecutive replies.
This differs from the base vacation specification, which does not This differs from the base vacation specification, which does not
allow a time period of zero (":days 0" is forbidden); the change is allow a time period of zero (":days 0" is forbidden); the change is
necessary to allow operation of an auto-responder (see necessary to allow operation of an auto-responder (see [RFC6133], and
[I-D.ietf-sieve-autoreply], and note especially example 4 in section note especially example 4 in section 3 of that document).
3 of that document).
If ":seconds" and ":days" are both omitted, a site-defined interval If ":seconds" and ":days" are both omitted, a site-defined interval
is used (see [RFC5230]). is used (see [RFC5230]).
Usage: vacation [":days" number | ":seconds" number] Usage: vacation [":days" number | ":seconds" number]
[":subject" string] [":subject" string]
[":from" string] [":from" string]
[":addresses" string-list] [":addresses" string-list]
[":mime"] [":mime"]
[":handle" string] [":handle" string]
<reason: string> <reason: string>
3. Examples 3. Examples
This example will automatically reply to senders with a message that The following example will automatically reply to senders with a
the recipient is in a meeting. Multiple replies to the same sender message that the recipient is in a meeting. Multiple replies to the
will only be sent every half hour (1800 seconds). same sender will only be sent every half hour (1800 seconds).
require ["vacation-seconds"]; require ["vacation-seconds"];
vacation :addresses ["tjs@example.edu", "ts4z@landru.example.edu"] vacation :addresses ["tjs@example.edu", "ts4z@landru.example.edu"]
:seconds 1800 :seconds 1800
"I am in a meeting, and do not have access to email."; "I am in a meeting, and do not have access to email.";
This example is used to send an acknowledgment to every message The following example is used to send an acknowledgment to every
received. A :seconds value of zero is used to reply to every message received. A :seconds value of zero is used to reply to every
message, with no removal of duplicates to the same sender. This message, with no removal of duplicates to the same sender. This
requires that the Sieve engine allow an interval of zero; if it does requires that the Sieve engine allow an interval of zero; if it does
not, and it imposes a minimum value, not every message will receive not, and it imposes a minimum value, not every message will receive
an auto-reply. an auto-reply.
require ["vacation-seconds"]; require ["vacation-seconds"];
vacation :handle "auto-resp" :seconds 0 vacation :handle "auto-resp" :seconds 0
"Your request has been received. A service "Your request has been received. A service
representative will contact you as soon as representative will contact you as soon as
skipping to change at page 5, line 24 skipping to change at page 4, line 49
5. IANA Considerations 5. IANA Considerations
5.1. Registration of Sieve Extension 5.1. Registration of Sieve Extension
To: iana@iana.org To: iana@iana.org
Subject: Registration of new Sieve extension Subject: Registration of new Sieve extension
Capability name: vacation-seconds Capability name: vacation-seconds
Description: adds the ":seconds" parameter to the Sieve Vacation Description: adds the ":seconds" parameter to the Sieve Vacation
extension. Implementations that support this MUST also support extension. Implementations that support this MUST also support
"vacation". "vacation".
RFC number: this RFC RFC number: RFC 6131
Contact address: The Sieve discussion list <sieve@ietf.org> Contact address: The Sieve discussion list <sieve@ietf.org>
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3834] Moore, K., "Recommendations for Automatic Responses to [RFC3834] Moore, K., "Recommendations for Automatic Responses to
Electronic Mail", RFC 3834, August 2004. Electronic Mail", RFC 3834, August 2004.
[RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering [RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering
Language", RFC 5228, January 2008. Language", RFC 5228, January 2008.
[RFC5230] Showalter, T. and N. Freed, "Sieve Email Filtering: [RFC5230] Showalter, T. and N. Freed, "Sieve Email Filtering:
Vacation Extension", RFC 5230, January 2008. Vacation Extension", RFC 5230, January 2008.
6.2. Informative References 6.2. Informative References
[I-D.ietf-sieve-autoreply] [RFC6133] George, R., Leiba, B., and A. Melnikov, "Sieve Email
George, R., Leiba, B., and A. Melnikov, "Sieve Email Filtering: Use of Presence Information with Auto-Responder
Filtering: Use of Presence Information with Auto Responder Functionality", RFC 6133, July 2011.
functionality", draft-ietf-sieve-autoreply-02 (work in
progress), October 2010.
Authors' Addresses Authors' Addresses
Robins George Robins George
Huawei Technologies Huawei Technologies
Bangalore, Karnataka 560071 Bangalore, Karnataka 560071
India India
Phone: +91-080-41117676 Phone: +91-080-41117676
Email: robinsgv@gmail.com EMail: robinsgv@gmail.com
Barry Leiba Barry Leiba
Huawei Technologies Huawei Technologies
Phone: +1 646 827 0648 Phone: +1 646 827 0648
Email: barryleiba@computer.org EMail: barryleiba@computer.org
URI: http://internetmessagingtechnology.org/ URI: http://internetmessagingtechnology.org/
 End of changes. 17 change blocks. 
59 lines changed or deleted 63 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/