Re: [Jmap] Call for adoption: JMAP QUOTA

Benoît TELLIER <btellier@linagora.com> Fri, 13 September 2019 02:54 UTC

Return-Path: <btellier@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 B455D12003F for <jmap@ietfa.amsl.com>; Thu, 12 Sep 2019 19:54:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.521
X-Spam-Level:
X-Spam-Status: No, score=-1.521 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, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=linagora.com
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 kTeaa2EhVKUQ for <jmap@ietfa.amsl.com>; Thu, 12 Sep 2019 19:54:12 -0700 (PDT)
Received: from outgoing.linagora.com (outgoing.linagora.com [51.75.198.246]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75D3512001A for <jmap@ietf.org>; Thu, 12 Sep 2019 19:54:12 -0700 (PDT)
Received: from linagora.com (unknown [10.233.69.202]) by outgoing.linagora.com (Postfix) with ESMTP id 8F13A3B for <jmap@ietf.org>; Fri, 13 Sep 2019 02:54:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linagora.com; s=s20181122; t=1568343249; bh=7iX/xVyhtjhUxxBDy9Qmvi2F+N7wPDQfyLThZYRyJRg=; h=From:Reply-To:To:Subject:Date:References:From; b=QTNJ1WoqR8Xbt0X+0IaCmc3wPdl5Nbb6jFPed+pcypidk2hdPxdgjvEGyH3KB3ybg qyjdfBJjdTTgUPJtLF21kkNHddpxFnQLidI1i4BoEcX9M2ZCaik0yqEpbC/xOAGX45 qUqzIlEABH1lwVXKVkqW/ZjAqfExbrX25kPozwDoV0PzqcTxWP8MqX8cHrtM5UNbE+ UUg0prxddIyPW9/lUiQmt8euCE70NFvpidWeXWeLmzuheplY4I9iOcnhpmSEazh9sR hzbNJTDoD9EN/Q//uL0CVSi/2moboBkVAuRo/x3qrfrvNsUYsc58kfk4zWvDZLaOSV NVJDamlBRK/xA==
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: Benoît TELLIER <btellier@linagora.com>
Sender: Benoît TELLIER <btellier@linagora.com>
Reply-To: btellier@linagora.com
To: "jmap@ietf.org" <jmap@ietf.org>
Message-ID: <Mime4j.1e.36a5e2f6a87458f9.16d288abbc7@linagora.com>
Date: Fri, 13 Sep 2019 02:54:03 +0000
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>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/p1LT6NnBioppfA7EZroJmVG-7SQ>
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:54:15 -0000

Agree, there is no need to get this specific to emails.

Le 13 septembre 2019 09:28, de brong@fastmailteam.com
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" rel="nofollow">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" rel="nofollow">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/" rel="nofollow">https://datatracker.ietf.org/doc/draft-ietf-extra-quota/

 

Regards,

 

Bron.

 

--

  Bron Gondwana, CEO, Fastmail Pty Ltd

 

 

_______________________________________________
Jmap mailing list



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