idnits 2.17.1 draft-ietf-sieve-vacation-seconds-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (October 12, 2010) is 4943 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-04) exists of draft-ietf-sieve-autoreply-00 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Sieve working group R. George 3 Internet-Draft 4 Intended status: Standards Track B. Leiba 5 Expires: April 15, 2011 Huawei Technologies 6 October 12, 2010 8 Sieve Vacation Extension: "Seconds" parameter 9 draft-ietf-sieve-vacation-seconds-01 11 Abstract 13 This document describes a further extension to the Sieve Vacation 14 extension, allowing multiple auto-replies to the same sender in a 15 single day by adding a ":seconds" parameter. 17 Status of this Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on April 15, 2011. 34 Copyright Notice 36 Copyright (c) 2010 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 52 1.1. Terminology Used in This Document . . . . . . . . . . . . . . 3 54 2. 'Seconds' Parameter . . . . . . . . . . . . . . . . . . . . . 3 56 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 61 5.1. Registration of Sieve Extension . . . . . . . . . . . . . . . 5 63 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 6.1. Normative References . . . . . . . . . . . . . . . . . . . . 5 65 6.2. Informative References . . . . . . . . . . . . . . . . . . . 5 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 6 69 1. Introduction 71 The Sieve [RFC5228] Vacation extension [RFC5230] defines a mechanism 72 to generate automatic replies to incoming email messages. Through 73 the ":days" parameter, it limits the number of auto-replies to the 74 same sender to one per [n] days, for a specified number of days. But 75 there are cases when one needs more granularity, if one would like to 76 generate "vacation" replies for shorter-term situations ("in a 77 meeting", for example, or "out to lunch"). 79 This extension defines a ":seconds" parameter to provide more 80 granularity for such situations. 82 1.1. Terminology Used in This Document 84 The upper-case key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 85 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 86 "OPTIONAL" in this document are to be interpreted as described in RFC 87 2119 [RFC2119]. 89 2. 'Seconds' Parameter 91 The purpose of the ":seconds" parameter is to specify the minimum 92 time interval (in seconds) between consecutive auto-replies to a 93 given sender. The ":seconds" value, if specified, is used instead of 94 the ":days" value, and works in a similar way (see the Vacation 95 extension [RFC5230] for details). Only one of ":days" and ":seconds" 96 is allowed -- use of both parameters in the same vacation action MUST 97 result in a Sieve processing error. 99 The capability string associated with this extension is "vacation- 100 seconds". Note that "vacation-seconds" implies "vacation", and a 101 script with "vacation-seconds" in a "require" list can omit 102 "vacation" from that list. 104 The time value is specified in seconds, and MUST be greater than or 105 equal to 0 and less than 2**31. All valid values MUST be accepted 106 without error, but sites MAY define a minimum value to actually be 107 used if a smaller value is specified, and/or a maximum value to be 108 used if a larger value is specified. If a site imposes a maximum 109 value, that value MUST be at least 86400 (one day). 111 If 0 is specified and used, it means that all auto-replies are sent, 112 and no attempt is made to suppress consecutive replies. This changes 113 the base vacation specification, which does not allow ":days 0"; the 114 change is necessary to allow operation of an auto-responder (see 115 [I-D.ietf-sieve-autoreply]). 117 If ":seconds" and ":days" are both omitted, a site-defined interval 118 is used (see [RFC5230]). 120 Usage: vacation [":days" number | ":seconds" number] 121 [":subject" string] 122 [":from" string] 123 [":addresses" string-list] 124 [":mime"] 125 [":handle" string] 126 128 3. Examples 130 This example will automatically reply to senders with a message that 131 the recipient is in a meeting. Multiple replies to the same sender 132 will only be sent every half hour (1800 seconds). 134 require ["vacation-seconds"]; 135 vacation :addresses ["tjs@example.edu", "ts4z@landru.example.edu"] 136 :seconds 1800 137 "I am in a meeting, and do not have access to email."; 139 This example is used to send an acknowledgment to every message 140 received. A :seconds value of zero is used to reply to every 141 message, with no removal of duplicates to the same sender. This 142 requires that the Sieve engine allow an interval of zero; if it does 143 not, and it imposes a minimum value, not every message will receive 144 an auto-reply. 146 require ["vacation-seconds"]; 148 vacation :handle "auto-resp" :seconds 0 149 "Your request has been received. A service 150 representative will contact you as soon as 151 possible, usually within one business day."; 153 4. Security Considerations 155 Security considerations for the Sieve Vacation extension [RFC5230] 156 apply equally here. In addition, implementations SHOULD consider the 157 number of auto-replies that might be generated by allowing small 158 values of ":seconds" (including 0), and MAY impose additional limits 159 on that number. See the Security Considerations section of RFC 3834 160 [RFC3834] for a fuller discussion. 162 5. IANA Considerations 164 5.1. Registration of Sieve Extension 166 To: iana@iana.org 167 Subject: Registration of new Sieve extension 168 Capability name: vacation-seconds 169 Description: adds the ":seconds" parameter to the Sieve Vacation 170 extension. Implementations that support this MUST also support 171 "vacation". 172 RFC number: this RFC 173 Contact address: The Sieve discussion list 175 6. References 177 6.1. Normative References 179 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 180 Requirement Levels", BCP 14, RFC 2119, March 1997. 182 [RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering 183 Language", RFC 5228, January 2008. 185 [RFC5230] Showalter, T. and N. Freed, "Sieve Email Filtering: 186 Vacation Extension", RFC 5230, January 2008. 188 6.2. Informative References 190 [I-D.ietf-sieve-autoreply] 191 George, R., Leiba, B., and A. Melnikov, "Sieve Email 192 Filtering: Use of Presence Information with Auto Responder 193 functionality", draft-ietf-sieve-autoreply-00 (work in 194 progress), June 2010. 196 [RFC3834] Moore, K., "Recommendations for Automatic Responses to 197 Electronic Mail", RFC 3834, August 2004. 199 Authors' Addresses 201 Robins George 203 Email: robinsgv@gmail.com 205 Barry Leiba 206 Huawei Technologies 208 Phone: +1 646 827 0648 209 Email: barryleiba@computer.org 210 URI: http://internetmessagingtechnology.org/