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

[René CORDIER <[e-mail]>]

Hi Alexey,

Thank you for the time you took reviewing the draft and for your comments, I will try to take the time to address them before the next IETF session.

Best regards,

Rene.

On July 12, 2022 1:00 AM, from [e-mail]

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