Re: [Jmap] Call for adoption: JMAP QUOTA

René CORDIER <rcordier@linagora.com> Mon, 30 September 2019 08:41 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 DB69712013B for <jmap@ietfa.amsl.com>; Mon, 30 Sep 2019 01:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.522
X-Spam-Level:
X-Spam-Status: No, score=-1.522 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] 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 m6VfWC8uz_lU for <jmap@ietfa.amsl.com>; Mon, 30 Sep 2019 01:41:47 -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 CE80412013A for <jmap@ietf.org>; Mon, 30 Sep 2019 01:41:46 -0700 (PDT)
Received: from linagora.com (unknown [10.233.69.202]) by outgoing.linagora.com (Postfix) with ESMTP id 8339A3B for <jmap@ietf.org>; Mon, 30 Sep 2019 08:41:43 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linagora.com; s=s20181122; t=1569832903; bh=xhN7KWbXsoswoMzsBSS1pDb/0kEpE/FGK3ObXAYo848=; h=From:Reply-To:To:Subject:Date:References:From; b=USQnoWE36GV7JHcsulY/nZzhDidSO6uHBlIwDjgbSXdEwOebERzJ2B3f6lDpTuM4S NnSqaRUyLqXJHfAfhUr4vJlVytK5WX4YaHZMLCH2dQyfuJ8ybZfRsqbc2m2RoDzo09 dyFhXONESYuNHp+iUFWkrWOf01rKHQg1Q2MWoQJM3PQhL75UBEvYovstwQfcmOwGg4 TTAwdKPCcsp7hogsh9uTQaCMwecPS9np+PMvKoVyHGiNuulvSvaHAMdVqrEgLXzfsG OyBrbyttc/eCiXkTsI4nlrL8sougwkDzt1Uz5DMqDOeBx738Kn73x8MLbuBkOU6aU5 7AxQwZLkbLcsg==
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: René CORDIER <rcordier@linagora.com>
Sender: René CORDIER <rcordier@linagora.com>
Reply-To: rcordier@linagora.com
To: "jmap@ietf.org" <jmap@ietf.org>
Message-ID: <Mime4j.4f.af7c7bf6b92224d0.16d81551f61@linagora.com>
Date: Mon, 30 Sep 2019 08:41:42 +0000
References:
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/84yjgbyx-voFF7zUa3mnlNjcpAg>
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: Mon, 30 Sep 2019 08:41:49 -0000

Hi everybody,

I believe I saw some concerns during the call for adoption that will definitely deserve some attention, like multiple levels of quotas, or trying to understand why quotas with IMAP were not widely supported and what can we do to change it with JMAP.

But I don't remember seeing any strong objection to it ! The vote was supposed to finish Friday 20th of September. Is it reasonable to ask to move forward then?

Regards,

Rene.

Le 6 septembre 2019 07:36, de brong@fastmailteam.com
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