Re: [Jmap] Feedback on the quota draft

"Neil Jenkins" <neilj@fastmailteam.com> Thu, 21 November 2019 12:44 UTC

Return-Path: <neilj@fastmailteam.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DCEB1208BA for <jmap@ietfa.amsl.com>; Thu, 21 Nov 2019 04:44:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=JCZ+MOhW; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=WkP/GV8Q
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHNG2RnZI0Ja for <jmap@ietfa.amsl.com>; Thu, 21 Nov 2019 04:44:40 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A41BC1208B9 for <jmap@ietf.org>; Thu, 21 Nov 2019 04:44:40 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id C289A21FC3 for <jmap@ietf.org>; Thu, 21 Nov 2019 07:44:39 -0500 (EST)
Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Thu, 21 Nov 2019 07:44:39 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=fWyxAtR Aa4Gr/vyHuUaZNlUEg8bMLFm3E9AtazwRoaU=; b=JCZ+MOhWCMBeRFLNok4KBZ6 Qa8tif9T3JiViQNUAWCMHiBxXrCD7mVOCRUODdlKIL/gqHcjR4bvZOJtrB6ubXpA +bZ9/OzAqVW6Mw0RctHtobBjgI+1O5uvtRjImUSysM8qZ0Iicz1Bp71BhLYkjl+X qjG4S0iigeid4rVG9IQqFwqLpLIE7W5m3itSyT3+UYiCWMTzYSnLlZlVURGiA8Uy tBlQDQvk4m+0th0YT0CtJPSYXcGUmd1kfQSSlxsS7WR+x3cpjjiv/hRlnWrNzBnU utJuXz70zRvXvrd8Co7GBGzZLEcgs7DKs3we47I8wOO22S0W6qV4f5r5fV44eCQ= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=fWyxAt RAa4Gr/vyHuUaZNlUEg8bMLFm3E9AtazwRoaU=; b=WkP/GV8QiU4QFfwR2Ht2/m kAlWcAEpjKK/hTwYt/C2VYxPyu4vgCadppYoVOc1szRSjfEdMIBsn23dtWNtsrLv 4t1HwzLmEdqijlG1fbXjuKssb18EVPcHpGDDgh2Nxv4JTb9BM08EtaN+vm89Jp0L lxnoUjdlmtjhYEjv3EeYuw0YB+GzURpG6XcbVorXX6W5Q3vgjdrc5omikR8GRV4C plM/rlLI5VXi0F/rpciP2Iyq7RkPWhVVSZkyrNVyg367DNV3F6pqvkvUMmA3xKlv BkzaYbremEJFR5RM6qGjfUkAPJ04jRc9RkHMV7IamEhXdWsCCV6DbVz/uE3SfJQA ==
X-ME-Sender: <xms:t4bWXQ0GgZv12zMhPxkXc8-UPXuCREpo-ZK-pgWQ8OslMlswLF1VHQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehvddggeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucfrrghrrghmpehmrghilhhfrhhomhepnhgvihhljhesfhgrshhtmhgrihhlthgvrghm rdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:t4bWXa5ek5_pOrT90AhtJ3kz26NJtvTWjDG0XiRMpNEA8VBmjlGdnw> <xmx:t4bWXbcrahLcU7Ai62ftG2Nplqj0iQJH6kTWziXniS0KLRsrEIU95Q> <xmx:t4bWXWZfN6DnNaDCQB93t3DX5xzNx4egNdWW0ryfe8XvarqkEZhDvw> <xmx:t4bWXSPBNosd-Iwx0WhtbLfJ_yJA0SxgqY-tWbcGxZDZEcrUldlAJg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 71C1030045A; Thu, 21 Nov 2019 07:44:39 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1
Mime-Version: 1.0
Message-Id: <a59329d7-148b-4889-8064-2a637b0c3032@dogfood.fastmail.com>
In-Reply-To: <cb566662-c4cd-46b8-83db-170c9c91f19f@dogfood.fastmail.com>
References: <cb566662-c4cd-46b8-83db-170c9c91f19f@dogfood.fastmail.com>
Date: Thu, 21 Nov 2019 20:44:19 +0800
From: Neil Jenkins <neilj@fastmailteam.com>
To: IETF JMAP Mailing List <jmap@ietf.org>
Content-Type: multipart/alternative; boundary="2053f58bfd004240b05a302efe4de023"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/gdTf3gCCHhwNLK8ukRehIUYvzeY>
Subject: Re: [Jmap] Feedback on the quota draft
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 12:44:42 -0000

On Wed, 20 Nov 2019, at 19:20, Bron Gondwana wrote:
> *Resource Types*
> 
> The IMAP quota draft defines three types of resources for quotas, and also a registry where more can be described. The initial types are "STORAGE" (units 1024 octets), "MESSAGE" (number of individual emails) and "MAILBOX" (number of mailboxes). It maybe viable to use the same registry.
> 
> Of course, then you get issues like what should you call it for Calendar or Addressbook? Should the limits be given DAVish names like "COLLECTION" and "RESOURCE" such that MESSAGE becomes "RESOURCE" and "MAILBOX" becomes "COLLECTION"? in JMAP quotas?

This is completely redundant if we have the data types property that you mentioned earlier (which I think we should do). The only thing you need is a property to say whether this quota is a "count" or "bytes". e.g. You may have a quota of max 50 Calendar objects and another quota that limits Email and CalendarEvent storage to a shared 50 GB.

> Also: should we do storage in bytes, or do 1024 octets for our storage numbers in JMAP as well so they map identically to the definition in the registry?

I would prefer bytes.

Neil.