[Jmap] Comments on draft-ietf-jmap-quotas-03

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 11 July 2022 18:00 UTC

Return-Path: <alexey.melnikov@isode.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 1235CC18872E for <jmap@ietfa.amsl.com>; Mon, 11 Jul 2022 11:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HbihphuF1fa8 for <jmap@ietfa.amsl.com>; Mon, 11 Jul 2022 11:00:31 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id E4B7AC18872A for <jmap@ietf.org>; Mon, 11 Jul 2022 11:00:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1657562429; d=isode.com; s=june2016; i=@isode.com; bh=xs8unmPi0Qj+NHj1GLPggZSCqge46KT/wcvdY6Vm3pw=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=ajowqWzvkFusJoZGidqAsK3MTNACrUQywAUHrI9MIHsWoVd+umQpzwGLuKuwk/GwwXVwvA jTnRd4fgEZBb3Ossrcy7H1YvZj/A0O/pYgIONbNoiuSP7ARkI9Bu6K0det8zcEvQgSphLH NJlhwKGCHVbiE+TQjJyj6kQvb/oY/pk=;
Received: from [192.168.1.222] (host31-49-219-107.range31-49.btcentralplus.com [31.49.219.107]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <YsxlPQAeCU6j@waldorf.isode.com>; Mon, 11 Jul 2022 19:00:29 +0100
Message-ID: <8a894856-9ab1-bfc3-13fc-847cca1e6040@isode.com>
Date: Mon, 11 Jul 2022 19:00:18 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
To: rcordier@linagora.com
From: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: "jmap@ietf.org" <jmap@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/00DqQhmfYep4B37dJ9LyMJCd8-E>
Subject: [Jmap] Comments on draft-ietf-jmap-quotas-03
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 11 Jul 2022 18:00:36 -0000

Hi,

I read the whole document thinking about whether it would be compatible 
with IMAP QUOTA implementations. It looks like it is compatible.

Some minor comments on the draft (can be considered WGLC comments):

1) In Section 2:

*softLimit*: UnsignedInt|null The soft limit set by this quota object. 
It can be used to still allow some operations, but refusing some others. 
What is allowed or not is up to the server. If set, it should be higher 
than the warnLimit but lower than the limit.

  -- The description is sufficiently vague that I struggle to imagine a 
use case. Can the document provide 1 or 2 examples?

2) In Section 2.5.1 (example):

  "resourceType": "size",

  I thought "size" is not a valid resource type. Should it be changed to 
"octets"?

3) The "Security Considerations" section is light on content. I think 
several things from Section 8 of RFC 9208 apply. In particular, use of 
scope "domain" or "global" can disclose some information on other 
accounts in the same domain/on the same server.

Best Regards,

Alexey