idnits 2.17.1 draft-ietf-sieve-vacation-seconds-00.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 date (June 23, 2010) is 5057 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 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 B. Leiba 4 Intended status: Standards Track Huawei Technologies 5 Expires: December 25, 2010 June 23, 2010 7 Sieve Vacation Extension: "Seconds" parameter 8 draft-ietf-sieve-vacation-seconds-00 10 Abstract 12 This document describes a further extension to the Sieve Vacation 13 extension, allowing multiple auto-replies to the same sender in a 14 single day by adding a ":seconds" parameter. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on December 25, 2010. 33 Copyright Notice 35 Copyright (c) 2010 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 51 1.1. Terminology Used in This Document . . . . . . . . . . . . . . 3 53 2. 'Seconds' Parameter . . . . . . . . . . . . . . . . . . . . . 3 55 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 59 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 60 5.1. Registration of Sieve Extension . . . . . . . . . . . . . . . 5 62 6. Normative References . . . . . . . . . . . . . . . . . . . . 5 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 5 66 1. Introduction 68 The Sieve [RFC5228] Vacation extension [RFC5230] defines a mechanism 69 to generate automatic replies to incoming email messages. Through 70 the ":days" parameter, it limits the number of auto-replies to the 71 same sender to one per [n] days, for a specified number of days. But 72 there are cases when one needs more granularity, if one would like to 73 generate "vacation" replies for shorter-term situations ("in a 74 meeting", for example, or "out to lunch"). 76 This extension defines a ":seconds" parameter to provide more 77 granularity for such situations. 79 1.1. Terminology Used in This Document 81 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 82 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 83 document are to be interpreted as described in RFC 2119 [RFC2119]. 85 2. 'Seconds' Parameter 87 The purpose of the ":seconds" parameter is to specify the minimum 88 time interval (in seconds) between consecutive auto-replies to a 89 given sender. The ":seconds" value, if specified, is used instead of 90 the ":days" value, and works in a similar way (see the Vacation 91 extension [RFC5230] for details). Only one of ":days" and ":seconds" 92 is allowed -- use of both parameters in the same vacation action MUST 93 result in a Sieve processing error. 95 The capability string associated with this extension is "vacation- 96 seconds". Note that "vacation-seconds" implies "vacation", and a 97 script with "vacation-seconds" in a "require" list can omit 98 "vacation" from that list. 100 The time value is specified in seconds, and MUST be greater than or 101 equal to 0 and less than 2**31. All valid values MUST be accepted 102 without error, but sites MAY define a minimum value to actually be 103 used if a smaller value is specified. If 0 is specified and used, it 104 means that all auto-replies are sent, and no attempt is made to 105 suppress consecutive replies. 107 If ":seconds" and ":days" are both omitted, a site-defined interval 108 is used (see [RFC5230]). 110 Usage: vacation [":days" number | ":seconds" number] 111 [":subject" string] 112 [":from" string] 113 [":addresses" string-list] 114 [":mime"] 115 [":handle" string] 116 118 3. Examples 120 This example will automatically reply to senders with a message that 121 the recipient is in a meeting. Multiple replies to the same sender 122 will only be sent every half hour (1800 seconds). 124 require ["vacation-seconds"]; 125 vacation :addresses ["tjs@example.edu", "ts4z@landru.example.edu"] 126 :seconds 1800 127 "I am in a meeting, and do not have access to email."; 129 This example is used to send an acknowledgment to every message 130 received. A :seconds value of zero is used to reply to every 131 message, with no removal of duplicates to the same sender. This 132 requires that the Sieve engine allow an interval of zero; if it does 133 not, and it imposes a minimum value, not every message will receive 134 an auto-reply. 136 require ["vacation-seconds"]; 138 vacation :handle "auto-resp" :seconds 0 139 "Your request has been received. A service 140 representative will contact you as soon as 141 possible, usually within one business day."; 143 4. Security Considerations 145 Security considerations for the Sieve Vacation extension [RFC5230] 146 apply equally here. In addition, implementations SHOULD consider the 147 number of auto-replies that might be generated by allowing small 148 values of ":seconds" (including 0). 150 5. IANA Considerations 152 5.1. Registration of Sieve Extension 154 To: iana@iana.org 155 Subject: Registration of new Sieve extension 156 Capability name: vacation-seconds 157 Description: adds the ":seconds" parameter to the Sieve Vacation 158 extension. Implementations that support this MUST also support 159 "vacation". 160 RFC number: this RFC 161 Contact address: The Sieve discussion list 162 164 6. Normative References 166 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 167 Requirement Levels", BCP 14, RFC 2119, March 1997. 169 [RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering 170 Language", RFC 5228, January 2008. 172 [RFC5230] Showalter, T. and N. Freed, "Sieve Email Filtering: 173 Vacation Extension", RFC 5230, January 2008. 175 Authors' Addresses 177 Robins George 178 Huawei Technologies 179 Huawei Base, Bantian, Longgang District 180 Shenzhen, Guangdong 518129 181 P. R. China 183 Phone: +86-755-28788314 184 Email: robinsg@huawei.com 185 Barry Leiba 186 Huawei Technologies 188 Phone: +1 646 827 0648 189 Email: barryleiba@computer.org 190 URI: http://internetmessagingtechnology.org/