JMAP for Quotas
draft-ietf-jmap-quotas-00

Document Type Active Internet-Draft (jmap WG)
Last updated 2019-09-30
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
JMAP                                                     R. Cordier, Ed.
Internet-Draft                                            M. Bailly, Ed.
Intended status: Standards Track                                Linagora
Expires: March 8, 2020                                 September 5, 2019

                            JMAP for Quotas
                       draft-ietf-jmap-quotas-00

Abstract

   This document specifies a data model for handling quotas on mailboxes
   with a server using JMAP.

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 https://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 March 8, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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.

Cordier & Bailly          Expires March 8, 2020                 [Page 1]
Internet-Draft                 JMAP Quotas                September 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational conventions  . . . . . . . . . . . . . . . . .   2
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
       1.2.1.  Quota . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Addition to the capabilities object . . . . . . . . . . .   3
       1.3.1.  urn::ietf::params::jmap::quota  . . . . . . . . . . .   3
   2.  Quota definition  . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  The Scope Data Type . . . . . . . . . . . . . . . . . . .   3
     2.2.  The Quota Object  . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.4.  Quota/get . . . . . . . . . . . . . . . . . . . . . . . .   4
       2.4.1.  Example . . . . . . . . . . . . . . . . . . . . . . .   5
     2.5.  Quota/changes . . . . . . . . . . . . . . . . . . . . . .   5
       2.5.1.  Example . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Addition to the Mailbox object  . . . . . . . . . . . . . . .   6
   4.  Security considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  JMAP Capability Registration for "quota"  . . . . . . . .   6
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   JMAP ([RFC8620] - JSON Meta Application Protocol) is a generic
   protocol for synchronising data, such as mail, calendars or contacts,
   between a client and a server.  It is optimised for mobile and web
   environments, and aims to provide a consistent interface to different
   data types.

   This specification defines a data model for handling mail quotas over
   JMAP, allowing you to read and explain quota information.

   This specification does not address quota administration, which
   should be handled by other means.

1.1.  Notational conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   Type signatures, examples and property descriptions in this document
   follow the conventions established in section 1.1 of [RFC8620].  Data

Cordier & Bailly          Expires March 8, 2020                 [Page 2]
Internet-Draft                 JMAP Quotas                September 2019

   types defined in the core specification are also used in this
   document.

   Servers MUST support all properties specified for the new data types
   defined in this document.

1.2.  Terminology

1.2.1.  Quota

   A quota is a numeric upper limit that the server is enforcing.
Show full document text