draft-ietf-sieve-vacation-seconds-02.txt   draft-ietf-sieve-vacation-seconds-03.txt 
Sieve working group R. George Sieve working group R. George
Internet-Draft Internet-Draft B. Leiba
Intended status: Standards Track B. Leiba Intended status: Standards Track Huawei Technologies
Expires: April 16, 2011 Huawei Technologies Expires: May 27, 2011 November 23, 2010
October 13, 2010
Sieve Vacation Extension: "Seconds" parameter Sieve Vacation Extension: "Seconds" parameter
draft-ietf-sieve-vacation-seconds-02 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 This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 32
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 April 16, 2011. This Internet-Draft will expire on May 27, 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 3, line 12 skipping to change at page 3, line 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 6 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 more frequently.
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 upper-case key words "MUST", "MUST NOT", "REQUIRED", "SHALL", The upper-case key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"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].
skipping to change at page 3, line 47 skipping to change at page 3, line 46
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, and/or a maximum value to be used if a smaller value is specified, and/or a maximum value to be
used if a larger value is specified. If a site imposes a maximum used if a larger value is specified. If a site imposes a maximum
value, that value MUST be at least 86400 (one day). value, that value MUST be at least 86400 (one day).
If 0 is specified and used, it means that all auto-replies are sent, If ":seconds 0" is specified and used, it means that all auto-replies
and no attempt is made to suppress consecutive replies. This changes are sent, and no attempt is made to suppress consecutive replies.
the base vacation specification, which does not allow ":days 0"; the This differs from the base vacation specification, which does not
change is necessary to allow operation of an auto-responder (see allow a time period of zero (":days 0" is forbidden); the change is
[I-D.ietf-sieve-autoreply]). necessary to allow operation of an auto-responder (see
[I-D.ietf-sieve-autoreply], and note especially example 4 in section
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]
skipping to change at page 5, line 34 skipping to change at page 5, line 34
RFC number: this RFC RFC number: this RFC
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
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] [I-D.ietf-sieve-autoreply]
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", draft-ietf-sieve-autoreply-02 (work in functionality", draft-ietf-sieve-autoreply-02 (work in
progress), October 2010. progress), October 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
Bangalore, Karnataka 560071
India
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. 9 change blocks. 
16 lines changed or deleted 20 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/