Network Working Group S. Bosch
Internet-Draft July 25, 2011
Updates: 5804 (if approved)
Intended status: Standards Track
Expires: January 26, 2012

ManageSieve Protocol: QUOTA/MAXSTORAGE Response Code
draft-bosch-managesieve-quota-maxstorage-00

Abstract

This document defines the new QUOTA/MAXSTORAGE response code for the MangeSieve protocol. It indicates that the total amount of storage occupied by the user's private Sieve scripts exceeds the site-defined quota constraint.

Status of this Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on January 26, 2012.

Copyright Notice

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

1. Introduction

Sieve [RFC5228] scripts allow users to filter incoming email. Using the ManageSieve protocol [RFC5804], users can securely manage their Sieve scripts on a remote server. This protocol allows a user to have multiple scripts on the server. To limit the resources required for script storage and execution, the server may refuse to accept a newly uploaded script based on site-defined quota constraints.

All queries from a ManageSieve client are replied to with either an OK, NO, or BYE response. Each response may be followed by a response code to describe the event in a more detailed machine-parsable fashion (see [RFC5804], Section 1.3). The ManageSieve protocol defines specific response codes to notify the client about exceeded quota. The following quota response codes are currently defined:

QUOTA
This generic response code is returned to indicate that some unspecified quota is exceeded. This is used when no more detailed response code is applicable.
QUOTA/MAXSIZE
This response code is returned when the size of the currently uploaded script exceeds the limit.
QUOTA/MAXSCRIPTS
This response code is returned when the number of private scripts of this user exceeds the limit.

This document defines a new quota response code that indicates that the total amount of storage occupied by the user's private Sieve scripts exceeds the site-defined quota constraint.

2. The QUOTA/MAXSTORAGE Response Code

This document defines the following new response code for ManageSieve ([RFC5804], Section 1.3):

QUOTA/MAXSTORAGE

If this response code is returned in the NO/BYE response, it means that the command would have placed the user above the site-defined limit on the total amount of storage occupied by the user's private Sieve scripts. If this response code is returned in the OK response, it can mean that the user is near its quota or that the user exceeded its quota, but the server supports soft quotas. This response code is a more specific version of the QUOTA response code defined in [RFC5804].

This extends the ManageSieve ABNF ([RFC5804], Section 4) as follows:

resp-code          =/ "QUOTA/MAXSTORAGE"
             ; resp-code is defined in [RFC5804]

3. Acknowledgements

Thanks to Alexey Melnikov for comments and suggestions.

4. IANA Considerations

The following requests IANA to register a new ManageSieve response code according to the IANA registration template specified in [RFC5804]:

To: iana@iana.org
Subject: ManageSieve Response Code Registration

Please register the following ManageSieve response code:

Response Code:
QUOTA/MAXSTORAGE
Arguments (use ABNF to specify syntax, or the word NONE if none can be specified):
NONE
Purpose:
If this response code is returned in the NO/BYE response, it means that the command would have placed the user above the site-defined limit on the total amount of storage occupied by the user's private Sieve scripts. If this response code is returned in the OK response, it can mean that the user is near its quota or that the user exceeded its quota, but the server supports soft quotas. This response code is a more specific version of the QUOTA response code.
Published Specification(s):
[RFCXXXX]
Person & email address to contact for further information:

Stephan Bosch <stephan@rename-it.nl>
Author/Change controller:
IESG.

5. Security Considerations

Security considerations are discussed in [RFC5804]. This document only registers a new response code for the ManageSieve protocol and as such it does not introduce any additional security concerns.

6. References

6.1. Normative References

[RFC5804] Melnikov, A. and T. Martin, "A Protocol for Remotely Managing Sieve Scripts", RFC 5804, July 2010.

6.2. Informative References

[RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering Language", RFC 5228, January 2008.

Author's Address

Stephan Bosch Enschede, NL EMail: stephan@rename-it.nl

Table of Contents