IETF Logo Mail Archive

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

René CORDIER <rcordier@linagora.com> Tue, 26 July 2022 03:14 UTC

Return-Path: <rcordier@linagora.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 D08BFC185733 for <jmap@ietfa.amsl.com>; Mon, 25 Jul 2022 20:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.226
X-Spam-Level:
X-Spam-Status: No, score=-6.226 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=linagora.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 dnkEAWM_5a-3 for <jmap@ietfa.amsl.com>; Mon, 25 Jul 2022 20:14:07 -0700 (PDT)
Received: from smtp.linagora.com (smtp.linagora.com [54.36.8.78]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57390C18571C for <jmap@ietf.org>; Mon, 25 Jul 2022 20:14:05 -0700 (PDT)
Received: from ?Open?PaaS?SMTP?server?for?Linagora? (unknown [51.83.109.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.linagora.com (Postfix) with ESMTPSA id A8A9C3EE1D; Tue, 26 Jul 2022 05:14:02 +0200 (CEST)
DKIM-Signature: a=rsa-sha256; b=WiDbnWi3h4iMhkt2+MVxmyCyizVJkB/GrFZGvzbFalAiF+rsWksU/jDFAXsTZsYa8Xo86fFDol/lfgAila3xU5+oovwri64qesIzDPsQHZuZLuB48ZJoj1TYi5Ss2tX9YupHNNQIqvdKezoMqt09vN88HIPgA79sc8YDzOX8ZPOU8IS6XACqRevEAwVsR19IF3Qzvo1ALHhZ76/8U0r5z9OWHveNxi9s9LH6gBmvcKE3j30UYRPCDStPz4VO/bTmOC79Rq2O/RDgcR1cFo7Q0mm+y5PNBcO4PZ5vBBChichy5u+45NAq86p+FE771AKpdtoJFZKGlvz4v92yYZ2Pdg==; s=smtpoutjames; d=linagora.com; v=1; bh=WwkO1ijB8RalOucKeFF3SXmC2/ZI9rHI9gKDhvEtu/g=; h=from : reply-to : subject : date : to : cc : resent-date : resent-from : resent-sender : resent-to : resent-cc : in-reply-to : references : list-id : list-help : list-unsubscribe : list-subscribe : list-post : list-owner : list-archive;
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-LINAGORA-Copy-Delivery-Done: 1
From: René CORDIER <rcordier@linagora.com>
Sender: René CORDIER <rcordier@linagora.com>
Reply-To: rcordier@linagora.com
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: "jmap@ietf.org" <jmap@ietf.org>
Message-ID: <Mime4j.ab.2b5033c96c955ab8.182387f4736@linagora.com>
Date: Tue, 26 Jul 2022 03:14:01 +0000
References: <8a894856-9ab1-bfc3-13fc-847cca1e6040@isode.com>
In-Reply-To: <8a894856-9ab1-bfc3-13fc-847cca1e6040@isode.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Hk7xwMYNbxCF6WQU1mF5XxDhQIk>
Subject: Re: [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: Tue, 26 Jul 2022 03:14:12 -0000

Hi Alexey,

I took a bit of time to try to fix your comments before the IETF this thursday. You can find them here: https://github.com/jmapio/jmap/pull/368" target="_blank" rel="nofollow">https://github.com/jmapio/jmap/pull/368

I will try to answer inline to your points as well.

Best regards,

Rene.

On July 12, 2022 1:00 AM, from alexey.melnikov@isode.com

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?


For example, it could be used for blocking outgoing events of an entity (sending emails, creating calendar events, ...) while still receiving incoming events (receiving emails, receiving calendars events, ...)


2) In Section 2.5.1 (example):

 "resourceType": "size",

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


Good catch! I missed that one when we changed from size 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.

I looked at the RFC 9208 and added what I found pertinent for this draft. Let me know if you have still a problem with this section.


Best Regards,

Alexey

_______________________________________________
Jmap mailing list
Jmap@ietf.org
https://www.ietf.org/mailman/listinfo/jmap

v2.23.0 | Report a Bug | By Email