idnits 2.17.00 (12 Aug 2021) /tmp/idnits60185/draft-bosch-managesieve-quota-maxstorage-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5804, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5804, updated by this document, for RFC5378 checks: 2008-10-20) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 25, 2011) is 3952 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) == Missing Reference: 'RFCXXXX' is mentioned on line 135, but not defined Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Bosch 3 Internet-Draft July 25, 2011 4 Updates: 5804 (if approved) 5 Intended status: Standards Track 6 Expires: January 26, 2012 8 ManageSieve Protocol: QUOTA/MAXSTORAGE Response Code 9 draft-bosch-managesieve-quota-maxstorage-00 11 Abstract 13 This document defines the new QUOTA/MAXSTORAGE response code for the 14 MangeSieve protocol. It indicates that the total amount of storage 15 occupied by the user's private Sieve scripts exceeds the site-defined 16 quota constraint. 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 This Internet-Draft will expire on January 26, 2012. 41 Copyright Notice 43 Copyright (c) 2011 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the BSD License. 56 1. Introduction 58 Sieve [RFC5228] scripts allow users to filter incoming email. Using 59 the ManageSieve protocol [RFC5804], users can securely manage their 60 Sieve scripts on a remote server. This protocol allows a user to 61 have multiple scripts on the server. To limit the resources required 62 for script storage and execution, the server may refuse to accept a 63 newly uploaded script based on site-defined quota constraints. 65 All queries from a ManageSieve client are replied to with either an 66 OK, NO, or BYE response. Each response may be followed by a response 67 code to describe the event in a more detailed machine-parsable 68 fashion (see [RFC5804], Section 1.3). The ManageSieve protocol 69 defines specific response codes to notify the client about exceeded 70 quota. The following quota response codes are currently defined: 72 QUOTA This generic response code is returned to 73 indicate that some unspecified quota is exceeded. 74 This is used when no more detailed response code 75 is applicable. 77 QUOTA/MAXSIZE This response code is returned when the size of 78 the currently uploaded script exceeds the limit. 80 QUOTA/MAXSCRIPTS This response code is returned when the number of 81 private scripts of this user exceeds the limit. 83 This document defines a new quota response code that indicates that 84 the total amount of storage occupied by the user's private Sieve 85 scripts exceeds the site-defined quota constraint. 87 2. The QUOTA/MAXSTORAGE Response Code 89 This document defines the following new response code for ManageSieve 90 ([RFC5804], Section 1.3): 92 QUOTA/MAXSTORAGE 94 If this response code is returned in the NO/BYE response, it means 95 that the command would have placed the user above the site-defined 96 limit on the total amount of storage occupied by the user's private 97 Sieve scripts. If this response code is returned in the OK response, 98 it can mean that the user is near its quota or that the user exceeded 99 its quota, but the server supports soft quotas. This response code 100 is a more specific version of the QUOTA response code defined in 101 [RFC5804]. 103 This extends the ManageSieve ABNF ([RFC5804], Section 4) as follows: 105 resp-code =/ "QUOTA/MAXSTORAGE" 106 ; resp-code is defined in [RFC5804] 108 3. Acknowledgements 110 Thanks to Alexey Melnikov for comments and suggestions. 112 4. IANA Considerations 114 The following requests IANA to register a new ManageSieve response 115 code according to the IANA registration template specified in 116 [RFC5804]: 118 To: iana@iana.org 119 Subject: ManageSieve Response Code Registration 121 Please register the following ManageSieve response code: 123 Response Code: QUOTA/MAXSTORAGE 124 Arguments (use ABNF to specify syntax, or the word NONE if none can 125 be specified): NONE 126 Purpose: If this response code is returned in the NO/BYE 127 response, it means that the command would have placed 128 the user above the site-defined limit on the total 129 amount of storage occupied by the user's private Sieve 130 scripts. If this response code is returned in the OK 131 response, it can mean that the user is near its quota 132 or that the user exceeded its quota, but the server 133 supports soft quotas. This response code is a more 134 specific version of the QUOTA response code. 135 Published Specification(s): [RFCXXXX] 136 Person & email address to contact for further information: 137 Stephan Bosch 139 Author/Change controller: IESG. 141 5. Security Considerations 143 Security considerations are discussed in [RFC5804]. This document 144 only registers a new response code for the ManageSieve protocol and 145 as such it does not introduce any additional security concerns. 147 6. References 149 6.1. Normative References 151 [RFC5804] Melnikov, A. and T. Martin, "A Protocol for Remotely 152 Managing Sieve Scripts", RFC 5804, July 2010. 154 6.2. Informative References 156 [RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering 157 Language", RFC 5228, January 2008. 159 Author's Address 161 Stephan Bosch 162 Enschede, 163 NL 165 Email: stephan@rename-it.nl