draft-ietf-sieve-vacation-seconds-00.txt   draft-ietf-sieve-vacation-seconds-01.txt 
Sieve working group R. George Sieve working group R. George
Internet-Draft B. Leiba Internet-Draft
Intended status: Standards Track Huawei Technologies Intended status: Standards Track B. Leiba
Expires: December 25, 2010 June 23, 2010 Expires: April 15, 2011 Huawei Technologies
October 12, 2010
Sieve Vacation Extension: "Seconds" parameter Sieve Vacation Extension: "Seconds" parameter
draft-ietf-sieve-vacation-seconds-00 draft-ietf-sieve-vacation-seconds-01
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 This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 25, 2010. This Internet-Draft will expire on April 15, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 2, line 19 skipping to change at page 2, line 19
2. 'Seconds' Parameter . . . . . . . . . . . . . . . . . . . . . 3 2. 'Seconds' Parameter . . . . . . . . . . . . . . . . . . . . . 3
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5.1. Registration of Sieve Extension . . . . . . . . . . . . . . . 5 5.1. Registration of Sieve Extension . . . . . . . . . . . . . . . 5
6. Normative References . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 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 for shorter-term situations ("in a generate "vacation" replies for shorter-term situations ("in a
meeting", for example, or "out to lunch"). meeting", for example, or "out to lunch").
This extension defines a ":seconds" parameter to provide more This extension defines a ":seconds" parameter to provide more
granularity for such situations. granularity for such situations.
1.1. Terminology Used in This Document 1.1. Terminology Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The upper-case key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119].
2. 'Seconds' Parameter 2. '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" and ":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 MUST be accepted
without error, but sites MAY define a minimum value to actually be without error, but sites MAY define a minimum value to actually be
used if a smaller value is specified. If 0 is specified and used, it used if a smaller value is specified, and/or a maximum value to be
means that all auto-replies are sent, and no attempt is made to used if a larger value is specified. If a site imposes a maximum
suppress consecutive replies. value, that value MUST be at least 86400 (one day).
If 0 is specified and used, it means that all auto-replies are sent,
and no attempt is made to suppress consecutive replies. This changes
the base vacation specification, which does not allow ":days 0"; the
change is necessary to allow operation of an auto-responder (see
[I-D.ietf-sieve-autoreply]).
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]
skipping to change at page 5, line 10 skipping to change at page 5, line 10
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
possible, usually within one business day."; possible, usually within one business day.";
4. Security Considerations 4. Security Considerations
Security considerations for the Sieve Vacation extension [RFC5230] Security considerations for the Sieve Vacation extension [RFC5230]
apply equally here. In addition, implementations SHOULD consider the apply equally here. In addition, implementations SHOULD consider the
number of auto-replies that might be generated by allowing small number of auto-replies that might be generated by allowing small
values of ":seconds" (including 0). values of ":seconds" (including 0), and MAY impose additional limits
on that number. See the Security Considerations section of RFC 3834
[RFC3834] for a fuller discussion.
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: this RFC
Contact address: The Sieve discussion list Contact address: The Sieve discussion list <sieve@ietf.org>
<ietf-mta-filters@imc.org>
6. Normative References 6. 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.
[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
[I-D.ietf-sieve-autoreply]
George, R., Leiba, B., and A. Melnikov, "Sieve Email
Filtering: Use of Presence Information with Auto Responder
functionality", draft-ietf-sieve-autoreply-00 (work in
progress), June 2010.
[RFC3834] Moore, K., "Recommendations for Automatic Responses to
Electronic Mail", RFC 3834, August 2004.
Authors' Addresses Authors' Addresses
Robins George Robins George
Huawei Technologies
Huawei Base, Bantian, Longgang District
Shenzhen, Guangdong 518129
P. R. China
Phone: +86-755-28788314 Email: robinsgv@gmail.com
Email: robinsg@huawei.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. 13 change blocks. 
23 lines changed or deleted 43 lines changed or added

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