IETF Logo Mail Archive

Re: [Jmap] Call for adoption: JMAP QUOTA

"Bron Gondwana" <brong@fastmailteam.com> Fri, 13 September 2019 02:29 UTC

Return-Path: <brong@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 812211201A3 for <jmap@ietfa.amsl.com>; Thu, 12 Sep 2019 19:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, URIBL_BLOCKED=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=0P9lw6MT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=zp7t9bZt
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 ljiiWi2lpZfe for <jmap@ietfa.amsl.com>; Thu, 12 Sep 2019 19:29:20 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1616112001A for <jmap@ietf.org>; Thu, 12 Sep 2019 19:29:20 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 4B477649; Thu, 12 Sep 2019 22:29:19 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Thu, 12 Sep 2019 22:29:19 -0400
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=fm3; bh=EIPxoJ4 gOyFRaUUNWu5hXPzXhk+M0ULkNw3qqkf8rWE=; b=0P9lw6MTEr49mb+UBUihUKZ XM5MhyYhZ3P9RE0ouix9+Ue346Tyup61XFyqTS9dwbQBqrp2ukIrJM0Ox5e120i9 BcnKTuzqNJ/7x1bRI0x5r6QleEFYlAnkWoQGUpmrFm05Zp9B/3YES2UUpb6m2m5R jp5ulBMq/mfjyLAQq/rmLA23CqrTYHYPp2hwwCRnEw+xfSdkp/iafRzOu9EUjixL ydaOgGQV5GEg9/1XFyFhDj+8whaHTepqJJjBo48x+9+QP5XWEcZ/PkLtc4PNSQPe /1LacfcpSfPvzuoKLBL4o0UE7ZNMGpmfrbDfBzrlEqadHZFX0iqTDSFGsRWHxQA= =
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=fm3; bh=EIPxoJ 4gOyFRaUUNWu5hXPzXhk+M0ULkNw3qqkf8rWE=; b=zp7t9bZt+qYEi4QQZ2m0mw pUZf2mumfh4/T+4S+t7TsZDwwTGPgSkEuk/ACurZpMPw3FeByGjDColAJqXTy37c uYE17u/F6ibBqOlvMT2kuDRkmr7+qeORtQvd9Zqa2ZxDoaKFiQMd36lZBCtSakcq uzvrcCxIm1fmFM2aNdBVHB8/o80Kntj1QKahNAcIqlR1bZj/imHgyKAhxRZ+Tq/2 jdYVSlcv5q7caShUlO3L9Fdrdtzdp26wxw9oSDeuUmZyI6Z/75ScvX4OSCbKgLvM ELnY45h54njQRcUdHwY8YWziQUq1D7FksCU9ekpvM70XWkHByryLCYOxOz1DxmsA ==
X-ME-Sender: <xms:_v56XTYsTD3ZAeTNynLES4gllYElKFo6MZJ6XORR-lqTn9mJrN5CTg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrtdeigdeitdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerreejnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucffohhmrghinhepghhithhhuhgsrdgtohhmpdhivghtfhdrohhrghenucfrrghrrghm pehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmnecuve hluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:_v56XetDmuApbUCuYInxa_ZaokXZVAquM2d2TA2cvScVdpbvoYgn6A> <xmx:_v56XYsWV7DBYISUbZpQCdmioE7sCmVE6dSko16cN4yOmUKE8AHIUQ> <xmx:_v56XbcaDX6pEbUA21EqUaHXiOToq0CZ0NqlUDbce4xTUpDpoPciVQ> <xmx:_v56XaN9eZ35LxXL1lZPM_VE_PmmGIo1JT22oiyV8iU9Y1gcJ7Z-nQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 7B2121875B7; Thu, 12 Sep 2019 22:29:18 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-237-gf35468d-fmstable-20190912v1
Mime-Version: 1.0
Message-Id: <6241bec3-4b61-4833-bc2e-2877566bf6fd@beta.fastmail.com>
In-Reply-To: <0100016d259b980f-a2bc55f5-320e-4b67-bc51-1e327deb6762-000000@email.amazonses.com>
References: <d90d5d6e-3c1a-4d90-875f-fc55de3c7c6f@beta.fastmail.com> <mail.5722a9d9-aaf5-4433-8f61-8d7a72d77a72@storage.wm.amazon.com> <mail.5722a9d9-aaf5-4433-8f61-8d7a72d77a72@storage.wm.amazon.com> <0100016d259b980f-a2bc55f5-320e-4b67-bc51-1e327deb6762-000000@email.amazonses.com>
Date: Fri, 13 Sep 2019 12:28:57 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: John van der Kamp <jkamp@amazon.nl>, "jmap@ietf.org" <jmap@ietf.org>
Content-Type: multipart/alternative; boundary="f1b3cc04035b48b2a3bda02a92216e01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/kZVkzc_g4Hq5KA6Vc0TQ8nKTTA8>
Subject: Re: [Jmap] Call for adoption: JMAP QUOTA
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: Fri, 13 Sep 2019 02:29:23 -0000

Yes, definitely. There's going to need to be some thought to get this working correctly, and extensible to new datatypes like the underway JMAP Calendars, and the soon to come JMAP Contacts!

Cheers,

Bron.

On Thu, Sep 12, 2019, at 23:13, John van der Kamp wrote:
> Some services use multiple levels of quota. 1st level may act as a warning, notifying the user he’s close to its quota unless actions are taken. 2nd level would block outgoing messages. 3rd and last level also blocks incoming emails bouncing those to the sender. Only the last level would be required, the rest optional. It looks like this is missing from the spec. Would it be worth considering?

> 

> John

> 

> *From:* Jmap [mailto:jmap-bounces@ietf.org] *On Behalf Of *Bron Gondwana
> *Sent:* Friday, 6 September, 2019 02:37
> *To:* jmap@ietf.org
> *Subject:* [Jmap] Call for adoption: JMAP QUOTA

> 

> Just to make it official!

> 

> This is a call for adoption for a specification for exposing (and potentially also managing) quotas over JMAP. As there are already multiple people in favour per the thread at https://mailarchive.ietf.org/arch/msg/jmap/G4C83gJEgjrjxi52J7UKaMc9TpY I am asking now if there are any objections.

> 

> If you do have objections, please make them by Friday, 20 September (2 weeks from today). If there are no objections we will adopt a draft at that point.

> 

> As a starting point we will work from https://github.com/linagora/jmap/pull/19.

> 

> I believe this work is within our charter, specifically:

> 

>> Extensions to the existing core and* mail* JMAP specifications are also

>> within scope for this working group, for example any additional parts

>> of SIEVE, *IMAP*, SMTP submission, as well as transport of JMAP over

>> WSS (WebSocket over TLS, RFC 6455).

> 

> Quota exists as part of IMAP (RFC2087), so is in scope.

> 

> This proposed work will also take into account the work on IMAP quota being done in the EXTRA working group on https://datatracker.ietf.org/doc/draft-ietf-extra-quota/

> 

> Regards,

> 

> Bron.

> 

> --

>  Bron Gondwana, CEO, Fastmail Pty Ltd

> brong@fastmailteam.com

> 

> 

> _______________________________________________
> Jmap mailing list
> Jmap@ietf.org
> https://www.ietf.org/mailman/listinfo/jmap
> 
> 
> 
> Amazon Development Center (Netherlands) B.V., Johanna Westerdijkplein 1, 2521 EN The Hague, Registration No. Chamber of Commerce 56869649, VAT: NL 852339859B01
> 
> 

--
 Bron Gondwana, CEO, Fastmail Pty Ltd
 brong@fastmailteam.com

v2.23.0 | Report a Bug | By Email