From nobody Wed Sep 4 00:22:43 2019 Return-Path: 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 E94E01200C4 for ; Wed, 4 Sep 2019 00:22:41 -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 lY7SAeGXHzWR for ; Wed, 4 Sep 2019 00:22:40 -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 1D4DC1200B9 for ; Wed, 4 Sep 2019 00:22:38 -0700 (PDT) Received: from linagora.com (unknown [10.233.69.202]) by outgoing.linagora.com (Postfix) with ESMTP id 0B8E73B for ; Wed, 4 Sep 2019 07:22:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linagora.com; s=s20181122; t=1567581756; bh=uD7Ucot33mEvCjk02ENNuWWPWuyngYgpRKqDH0+TDfk=; h=From:Reply-To:To:Subject:Date:From; b=mOIRDpqXdcbDYcWEAhybdLagOQX5VTrzEJK2SREhM7G90c/aboE+CTYPivtUyXpif ISthuwfdTZ0rvplRiAVyhDWHgRrJQb8TLYO6E+FIMvevUtAsCj01L/I9MSrpZ8113g ud68n8JeNTZ+2nKaoIw7FxhmF3uQ7QH9OG0W88wqKRNVT7/fbxNlZLTJV6S8RYYwod zpZBY19oL+qECAV69BQ8vAdhNCobk5uv2z0Bv0h5ZhvSXxbX4AMYKfZttaxdvMJzH1 CB2HrMgWObqPuT77pymQxhMCes3GsImeO1qvwaWkbZcbhWg6SPgBioCmQOMk7GQM+o OJme+klFT0ixw== MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Ren=E9_CORDIER?= Sender: =?ISO-8859-1?Q?Ren=E9_CORDIER?= Reply-To: rcordier@linagora.com To: "jmap@ietf.org" Message-ID: Date: Wed, 4 Sep 2019 07:20:52 +0000 Archived-At: Subject: [Jmap] Proposition: JMAP quotas specifications draft X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Sep 2019 07:22:42 -0000

Hello everybody,

With some colleagues at Linagora, we felt the ne= ed of having an addition to JMAP regarding Quotas=2E We want to be able to = give mail clients using JMAP a way of getting and displaying quotas of a us= er's mailbox in a context where it allows us to explain, as much as possibl= e, the business rule behind the quota to the final user=2E

So we br= ainstormed and wrote a draft regarding JMAP Quotas specifications=2E But be= fore submitting officially anything, we would like to discuss it with the r= est of the JMAP community=2E We would be really happy if other people from = the JMAP working group could review it, giving feedbacks, so that we could = arrive to a consensus all together so that this extension could provide use= ful not only to us, but also to the rest of the community=2E

You wil= l be able to find our draft of the specification in the form of a markdown = here : https://github=2Ecom/linagora/jmap/pull/19

Thank you and plea= se don't hesitate to take some time to discuss it with us !

Best reg= ards,

Rene=2E

From nobody Wed Sep 4 06:54:54 2019 Return-Path: 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 E7388120170 for ; Wed, 4 Sep 2019 06:54:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.698 X-Spam-Level: X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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=fastmail.fm header.b=OYKm23Vf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=s0h0nRBR 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 wvVOuRpYPuXd for ; Wed, 4 Sep 2019 06:54:46 -0700 (PDT) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 867A6120106 for ; Wed, 4 Sep 2019 06:54:46 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id B5AA921F6D; Wed, 4 Sep 2019 09:54:45 -0400 (EDT) Received: from imap1 ([10.202.2.51]) by compute7.internal (MEProxy); Wed, 04 Sep 2019 09:54:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm1; bh=XeJExEkiWgGYJrEhWHC6x15zTWFtaBD Kwh86PcmtIVA=; b=OYKm23Vfft5ZUpIkD83F7jO/NZlhtKL05R9PgP8K1ZuLXSS Fp9tG2sk8F8nTlPnRqioC/DPWN24nzfj9dj/HzY4hhW6qUjQzZUpLKb0FVrBmeKp x7lvdEKWL6gAl0OHnR852ybNtPQed5WEpCbZr+vSK7MuJ3r0aNDArRsRgQryz6m+ WrW3zY4Tm3PZkcQnwQtFZHQqOr+uD7s6sLMCNd6B+7GAMV8N+4qDDgfgYn24K9xE RIaW435Ux5P7g9LrUF6SCKtyl8YD7vF3STOSumnPQH8pAQISE0vJdNA9T5+tHxT9 P/J1QHw5f7cNzQKBOJ1EK7eBfyMHJ8lT3sS1r/A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=XeJExE kiWgGYJrEhWHC6x15zTWFtaBDKwh86PcmtIVA=; b=s0h0nRBRC5k3t9QnKsiBPK N1BHLqZRgqpwEJRMiPjCu1azm5qt1dl92cuvB4m2MN29ak3q3RpmCSSfBwyvcKLj DGzk6GgLpwW7/eVXjnmX1Wmle1XCsl7UeAPk6uUdKmXR1LorSuXgFvwn3eZSxTNN 5wVnRbqg0wnnD3HSlJTozwOA3qy3h5WEsa0Yxa+ut78Nt+KvV2qfAcTrePBkrlhY V/MbyAPlR3yeACqAHFIrgB0WsSLHetP3QYaowrputnkFbtJLXpe8tDbtpYMlevw7 S0kPDRUxMDJLF0eVHfisEmbn/5eKqwZWLO8l3eltnbDuaAhUHq/7WPFvVQfzUUAg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejhedgieekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdetlhgv gigvhicuofgvlhhnihhkohhvfdcuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrd hfmheqnecuffhomhgrihhnpehgihhthhhusgdrtghomhdpihgvthhfrdhorhhgnecurfgr rhgrmhepmhgrihhlfhhrohhmpegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmh enucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 30025C200A4; Wed, 4 Sep 2019 09:54:45 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-186-gf4cb3c3-fmstable-20190904v1 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Wed, 04 Sep 2019 14:54:06 +0100 From: "Alexey Melnikov" To: =?UTF-8?Q?Ren=C3=A9_CORDIER?= Cc: "jmap@ietf.org" Content-Type: multipart/alternative; boundary=bd2058d75f304a32b5f41f7a96298815 Archived-At: Subject: Re: [Jmap] Proposition: JMAP quotas specifications draft X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Sep 2019 13:54:49 -0000 --bd2058d75f304a32b5f41f7a96298815 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Ren=C3=A9, On Wed, Sep 4, 2019, at 8:20 AM, Ren=C3=A9 CORDIER wrote: > Hello everybody, >=20 > With some colleagues at Linagora, we felt the need of having an additi= on to JMAP regarding Quotas. We want to be able to give mail clients usi= ng JMAP a way of getting and displaying quotas of a user's mailbox in a = context where it allows us to explain, as much as possible, the business= rule behind the quota to the final user.=20 >=20 > So we brainstormed and wrote a draft regarding JMAP Quotas specificati= ons. But before submitting officially anything, we would like to discuss= it with the rest of the JMAP community. We would be really happy if oth= er people from the JMAP working group could review it, giving feedbacks,= so that we could arrive to a consensus all together so that this extens= ion could provide useful not only to us, but also to the rest of the com= munity. >=20 > You will be able to find our draft of the specification in the form of= a markdown here : https://github.com/linagora/jmap/pull/19 >=20 > Thank you and please don't hesitate to take some time to discuss it wi= th us ! This is useful work and I think it would be worth working on in the JMAP= WG. I suggest the text and terminology should be syncrhonized with my draft = in the EXTRA WG: https://datatracker.ietf.org/doc/draft-ietf-extra-quota/?include_text=3D= 1 Best Regards, Alexey >=20 > Best regards, >=20 > Rene. > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap >=20 --bd2058d75f304a32b5f41f7a96298815 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Ren=C3=A9,

On Wed, Sep 4, 2019, at 8:20 AM, Ren=C3=A9 CORDI= ER wrote:

Hello= everybody,

With some colleagues at Linagor= a, we felt the need of having an addition to JMAP regarding Quotas. We w= ant to be able to give mail clients using JMAP a way of getting and disp= laying quotas of a user's mailbox in a context where it allows us to exp= lain, as much as possible, the business rule behind the quota to the fin= al user.

So we brainstormed and wrote a dr= aft regarding JMAP Quotas specifications. But before submitting official= ly anything, we would like to discuss it with the rest of the JMAP commu= nity. We would be really happy if other people from the JMAP working gro= up could review it, giving feedbacks, so that we could arrive to a conse= nsus all together so that this extension could provide useful not only t= o us, but also to the rest of the community.

You will be able to find our draft of the specification in the form of= a markdown here : https://github.com/linagora/jmap/pull/19

Thank you and please don't hesitate to take some time t= o discuss it with us !

This is useful = work and I think it would be worth working on in the JMAP WG.
<= div>
I suggest the text and terminology should be syncrhon= ized with my draft in the EXTRA WG:
https://data= tracker.ietf.org/doc/draft-ietf-extra-quota/?include_text=3D1

Best Regards,
Alexey

=


Bes= t regards,

Rene.

_____= __________________________________________
Jmap mailing li= st
Jmap@ietf.org
https://www.ietf.org/mailma= n/listinfo/jmap


--bd2058d75f304a32b5f41f7a96298815-- From nobody Wed Sep 4 15:15:52 2019 Return-Path: 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 04766120099 for ; Wed, 4 Sep 2019 15:15:50 -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=WwA4arCt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JMFrgafM 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 IrDtfmeQsVm0 for ; Wed, 4 Sep 2019 15:15:47 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 509AA120077 for ; Wed, 4 Sep 2019 15:15:47 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id AFEEC22106 for ; Wed, 4 Sep 2019 18:15:46 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Wed, 04 Sep 2019 18:15:46 -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=NZRHQ3a RI+5Ro6/rbs62MLK715DQbvTANZQtYHvyHNU=; b=WwA4arCty55fYa5I+rWl7H4 u0CYUvClVq4QRkfsJ1Hk3erGB3LSX6MYCIwPyfiJHetPvZ1tuXd9UHXTNDn79M+Z U0/N1ZGidTs7bnj0CYdvdcIrdCjlasVVlRoBBkd3OMuxTjUx3puLHtjdbUDTQbZs xkLmEkm1OM4irCp/Z/Ludro5mpoF5TRcKaoyQpgBwxBDSzMmgqHDJ9E1UMCAvE2c 9gOeVIEW4+eNmSjdczPtXwIp5vrmh/nErmytytyZnY8bhnV9kHzlXegGJl+Yjclp FCEaBCwsdRVKdEK8H6XWAxrR1nsm+soip8JonHLhDRvqW4YGF1lhNeZI3+xfpzQ= = 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=NZRHQ3 aRI+5Ro6/rbs62MLK715DQbvTANZQtYHvyHNU=; b=JMFrgafMnXHPIWD5DUTzem ZaKu/f5KPvdJk5XM/ltLTjhioWM4VXQU1rwzBY1uO/QW1ZMrj81l8ycLyP4hy5qK Dh2iTxQPDm87rUSw/RBl8eZ82QIIaAHEJMq+jDWJZUyCFLjDJwhNX36p31aOfZYr pJg/kiwXZHg29UFo1gJQXN0Joa2n48USLj2gxaMrODcLEAEGwWXJ/DxuZnqiuIsD YheLrO3ICwFkYBaSjre8R1ILS3d1BWES8fYOnm2zvQ1yz0ySKIorB27o5jzBrs06 U4A98hYiDdTyd3dGokwmrP+hPtMdokUjRiZlDMxgIq2sLIBi4Aw9Ve4ayMctD/oQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejiedgtdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerreejnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucffohhmrghinhepghhithhhuhgsrdgtoh hmpdhivghtfhdrohhrghenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgr shhtmhgrihhlthgvrghmrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4628B180091; Wed, 4 Sep 2019 18:15:46 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-186-gf4cb3c3-fmstable-20190904v1 Mime-Version: 1.0 Message-Id: <872c1105-e88f-4962-9c53-1f51e6c0362f@www.fastmail.com> In-Reply-To: References: Date: Thu, 05 Sep 2019 08:15:25 +1000 From: "Bron Gondwana" To: jmap@ietf.org Content-Type: multipart/alternative; boundary=f79a2cfecd4f47f7bb15ea2b7af9a209 Archived-At: Subject: Re: [Jmap] Proposition: JMAP quotas specifications draft X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Sep 2019 22:15:50 -0000 --f79a2cfecd4f47f7bb15ea2b7af9a209 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Definitely agree that it's worthwhile work. We have a Quota spec interna= lly at Fastmail which we'd be happy to go over and see if there's stuff = we want to propose to add to your draft. I'm happy to do a call for adoption in the group straight away for this = - knowing that there may be some design rounds as well :) Cheers, Bron. On Wed, Sep 4, 2019, at 23:54, Alexey Melnikov wrote: > Hi Ren=C3=A9, >=20 > On Wed, Sep 4, 2019, at 8:20 AM, Ren=C3=A9 CORDIER wrote: >>=20 >> Hello everybody, >>=20 >> With some colleagues at Linagora, we felt the need of having an addit= ion to JMAP regarding Quotas. We want to be able to give mail clients us= ing JMAP a way of getting and displaying quotas of a user's mailbox in a= context where it allows us to explain, as much as possible, the busines= s rule behind the quota to the final user.=20 >>=20 >> So we brainstormed and wrote a draft regarding JMAP Quotas specificat= ions. But before submitting officially anything, we would like to discus= s it with the rest of the JMAP community. We would be really happy if ot= her people from the JMAP working group could review it, giving feedbacks= , so that we could arrive to a consensus all together so that this exten= sion could provide useful not only to us, but also to the rest of the co= mmunity. >>=20 >> You will be able to find our draft of the specification in the form o= f a markdown here : https://github.com/linagora/jmap/pull/19 >>=20 >> Thank you and please don't hesitate to take some time to discuss it w= ith us ! >>=20 > This is useful work and I think it would be worth working on in the JM= AP WG. >=20 > I suggest the text and terminology should be syncrhonized with my draf= t in the EXTRA WG: > https://datatracker.ietf.org/doc/draft-ietf-extra-quota/?include_text=3D= 1 >=20 > Best Regards, > Alexey >=20 >>=20 >>=20 >> Best regards, >>=20 >> Rene. >>=20 >> _______________________________________________ >> Jmap mailing list >> Jmap@ietf.org >> https://www.ietf.org/mailman/listinfo/jmap >>=20 >=20 > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap >=20 -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com --f79a2cfecd4f47f7bb15ea2b7af9a209 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
Definitely agree that it's worthwhile work.  We = have a Quota spec internally at Fastmail which we'd be happy to go over = and see if there's stuff we want to propose to add to your draft.

I'm happy to do a call for adoption in the group straight away = for this - knowing that there may be some design rounds as well :)

Cheers,

Bron.

On Wed, Sep 4, = 2019, at 23:54, Alexey Melnikov wrote:
Hi Ren=C3=A9,

On Wed, Sep = 4, 2019, at 8:20 AM, Ren=C3=A9 CORDIER wrote:


Hello everybody,
With some colleagues at Linagora, we felt the need of having= an addition to JMAP regarding Quotas. We want to be able to give mail c= lients using JMAP a way of getting and displaying quotas of a user's mai= lbox in a context where it allows us to explain, as much as possible, th= e business rule behind the quota to the final user.

<= /div>
So we brainstormed and wrote a draft regarding JMAP Quotas spe= cifications. But before submitting officially anything, we would like to= discuss it with the rest of the JMAP community. We would be really happ= y if other people from the JMAP working group could review it, giving fe= edbacks, so that we could arrive to a consensus all together so that thi= s extension could provide useful not only to us, but also to the rest of= the community.

You will be able to find ou= r draft of the specification in the form of a markdown here : https://gi= thub.com/linagora/jmap/pull/19

Thank you an= d please don't hesitate to take some time to discuss it with us !


This is useful work and I think it would= be worth working on in the JMAP WG.

I sugg= est the text and terminology should be syncrhonized with my draft in the= EXTRA WG:

Best Regards,
Alexey



Best regards,=

Rene.


___________= ____________________________________
Jmap mailing list
=
Jmap@ietf.org
https://www.ietf.org/mailman/list= info/jmap


_____= __________________________________________
Jmap mailing li= st
Jmap@ietf.org
https://www.ietf.org/mailma= n/listinfo/jmap


--
  Bron Gondwana, CEO, Fastma= il Pty Ltd
  brong@fastmailteam.c= om


--f79a2cfecd4f47f7bb15ea2b7af9a209-- From nobody Wed Sep 4 20:26:32 2019 Return-Path: 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 AA10312009E for ; Wed, 4 Sep 2019 20:26:20 -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 Rtijmuu526Ln for ; Wed, 4 Sep 2019 20:26:18 -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 928F5120033 for ; Wed, 4 Sep 2019 20:25:59 -0700 (PDT) Received: from linagora.com (unknown [10.233.69.202]) by outgoing.linagora.com (Postfix) with ESMTP id 939623B for ; Thu, 5 Sep 2019 03:25:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linagora.com; s=s20181122; t=1567653956; bh=HgJcQfg40oB7oeCbQ1iqVfxDpgiqOq19pRAQas54tAs=; h=From:Reply-To:To:Subject:Date:References:From; b=foJJIVOSc1Ovc3vbtb9V6hAqf20ZI3i52F+rUv/m5uIPEFt6L36Y/ik5NTPyBChUL uDNfYvbA5LHmENHqjiHqo5vcuxc832R1oZHXIbGgkyUkTx2OFyJS8yu+7124EVmP66 mAilFtRn0Gtrr3ocW9BiukM3bBYVjObtpjb8BGvFAdysOx/TPUnvbvgxfQFsidTNNq 6udpX3DF7JK/A3bOKDQG7CDx6dY+V/QPQ/klI3O2dbT/CKtPdo5GQbyNUfxyII+Meb O9kGOHJTiYY/Wrf5Wl8BdoC/zqzBwA8pJJbcQVKrIvWThOyKtqevjtmrkqDGUS9k9y JB+0UvIeq8k/w== MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Ren=E9_CORDIER?= Sender: =?ISO-8859-1?Q?Ren=E9_CORDIER?= Reply-To: rcordier@linagora.com To: "jmap@ietf.org" Message-ID: Date: Thu, 5 Sep 2019 03:25:54 +0000 References: Archived-At: Subject: Re: [Jmap] Proposition: JMAP quotas specifications draft X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Sep 2019 03:26:21 -0000

Hi guys,

Thank you a lot for your feedbacks, I highly appreciate i= t=2E

Sure don't hesitate to share points you want to discuss, especi= ally if you have an internal Quota spec which means you gave it some seriou= s thoughts on it already as well :)

Best regards,

Rene=2E
Le 5 septembre 2019 05:15, de brong@fastmailteam=2Ecom

Definitely agree that= it's worthwhile work=2E  We have a Quota spec internally at Fastmail = which we'd be happy to go over and see if there's stuff we want to propose = to add to your draft=2E

I'm happy to do a call for adoption in = the group straight away for this - knowing that there may be some design ro= unds as well :)

Cheers,

Bron=2E


O= n Wed, Sep 4, 2019, at 23:54, Alexey Melnikov wrote:
Hi Ren=C3=A9,

On W= ed, Sep 4, 2019, at 8:20 AM, Ren=C3=A9 CORDIER wrote:


Hello everybody,
<= br>
With some colleagues at Linagora, we felt the need of having = an addition to JMAP regarding Quotas=2E We want to be able to give mail cli= ents using JMAP a way of getting and displaying quotas of a user's mailbox = in a context where it allows us to explain, as much as possible, the busine= ss rule behind the quota to the final user=2E

So we brainstormed and wrote a draft regarding JMAP Quotas specifications= =2E But before submitting officially anything, we would like to discuss it = with the rest of the JMAP community=2E We would be really happy if other pe= ople from the JMAP working group could review it, giving feedbacks, so that= we could arrive to a consensus all together so that this extension could p= rovide useful not only to us, but also to the rest of the community=2E
<= /div>

You will be able to find our draft of the specific= ation in the form of a markdown here : https://github=2Ecom/linagora/jmap/p= ull/19

Thank you and please don't hesitate to = take some time to discuss it with us !


This is useful work and I think it would be worth working on in the JMAP = WG=2E

I suggest the text and terminology shoul= d be syncrhonized with my draft in the EXTRA WG:

Best Regards,
Alexey



Best regards,

Rene=2E


_______________________________________________
Jmap mailing list
Jmap@ietf=2Eorg
https:/= /www=2Eietf=2Eorg/mailman/listinfo/jmap


_______________________________________________
Jmap mailing list
Jmap@ietf=2Eorg
http= s://www=2Eietf=2Eorg/mailman/listinfo/jmap


--
  Bron Gon= dwana, CEO, Fastmail Pty Ltd
  brong= @fastmailteam=2Ecom


From nobody Thu Sep 5 17:37:11 2019 Return-Path: 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 E8C55120071 for ; Thu, 5 Sep 2019 17:37:09 -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=Zs86wF60; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Oqh+ZXMS 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 KxctNjoDiVIb for ; Thu, 5 Sep 2019 17:37:08 -0700 (PDT) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31693120043 for ; Thu, 5 Sep 2019 17:37:08 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 7EB50657 for ; Thu, 5 Sep 2019 20:37:07 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Thu, 05 Sep 2019 20:37:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:date:from:to:subject :content-type; s=fm3; bh=oSU+LBoT6Kv1fKE9McHiKtuxR474ijnwVydTt7e lJsQ=; b=Zs86wF60jUgUMygISIUMvwTIIlyUzMkjwEf74F506dJ2KpN7ql4nd1p vy7L98pE8LQsXISOyidh+Fn2YFswWXsXcXDXC0mBIbtHYxd+5QmvO4sweir1mRM2 YywCfaul19P2o/mgWrPhpSNtKsfMMw9TXe88ptX/NPft7l3ECG6+FQTItFhDnJ1K oURZOZNwGzgpZhxzTeFfpwz0ialn6h4FHLHnqjExC/lLQI8nTC/YpAb9nBilb7w8 jTipTllzUqs/swbacA5KJ5yaEjoCZBf4/qg/X+ZXkYWFOHswRQx7seKkLTzBqEfk 8q0D7VfZ3j0elejzC/H3jjKHssOsvrg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=oSU+LBoT6Kv1fKE9McHiKtuxR474i jnwVydTt7elJsQ=; b=Oqh+ZXMSp+ICjltOqdWBXt63wzIXdyZveGvSoEWbzn/iz Xk4d+FxbK4xo9oX15TDz2knwNC7ktVNEHT2oN6L+52PA0oOZwscvZ44br6kW+TtC ejzviAL1UCfrBBPorrOsCqiCgaOSIkz2O9n2WyKuHZtkg5qPJE/RztQigw2oZQ/J osSxqTTlwrFR/SvXAnVWtHe7hgdXJFGFhn2bue8oqJ4iB3SQ5WWrh1ZbOaXeGlDp uuWbaBwSZnOR3GAcIndEZm2rCkRV5ref8J2zswR3wUr8Rq4gMl6oC3So+9qWNJRy 3voQsDwqBsfYtgEAXE4i7syhHI+8t7H99sPir91hA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejkedgvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsegrtderre erredtnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghesfhgr shhtmhgrihhlthgvrghmrdgtohhmqeenucffohhmrghinhepghhithhhuhgsrdgtohhmpd hivghtfhdrohhrghenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshht mhgrihhlthgvrghmrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id AA110180091; Thu, 5 Sep 2019 20:37:06 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-188-g385deb1-fmstable-20190905v2 Mime-Version: 1.0 Message-Id: Date: Fri, 06 Sep 2019 10:36:46 +1000 From: "Bron Gondwana" To: jmap@ietf.org Content-Type: multipart/alternative; boundary=ded41a9e984a42a490cc73a48c6f928a Archived-At: Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 00:37:10 -0000 --ded41a9e984a42a490cc73a48c6f928a Content-Type: text/plain 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 --ded41a9e984a42a490cc73a48c6f928a Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Just to make it official!

This is a call fo= r adoption for a specification for exposing (and potentially also managi= ng) quotas over JMAP.  As there are already multiple people in favo= ur per the thread at https://mailarchive.ietf.org/arch/msg/jm= ap/G4C83gJEgjrjxi52J7UKaMc9TpY I am asking now if there are any obje= ctions.

If you do have objections, please make them by Frid= ay, 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 h= ttps://github.com/linagora/jmap/pull/19.

I believe th= is work is within our charter, specifically:

Extensions to the existing core and mail JMAP speci= fications are also
within sco= pe for this working group, for example any additional parts
of SIEVE, IMAP, SMTP submission, a= s well as transport of JMAP over
WSS (WebSocket over TLS, RFC 6455).

Quot= a exists as part of IMAP (RFC2087), so is in scope.

This pr= oposed work will also take into account the work on IMAP quota being don= e in the EXTRA working group on https://datatracker.ietf.org/doc/draft-ietf= -extra-quota/

<= div style=3D"font-family:Arial;">Regards,

Bron.
=

--
  Bron Go= ndwana, CEO, Fastmail Pty Ltd
  b= rong@fastmailteam.com

=

--ded41a9e984a42a490cc73a48c6f928a-- From nobody Fri Sep 6 01:07:45 2019 Return-Path: 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 8DCC4120098 for ; Fri, 6 Sep 2019 01:07:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no 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 Sf8alBLlYIe6 for ; Fri, 6 Sep 2019 01:07:42 -0700 (PDT) Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A67C12007C for ; Fri, 6 Sep 2019 01:07:41 -0700 (PDT) Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 33758C00EE; Fri, 6 Sep 2019 09:10:56 +0100 (IST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1567757456; bh=KdPQrTtccZV5bNiYhWeinsybqvVp5kyJ5NtO/cdCG7o=; h=From:To:Subject:Date:References:From; b=ZkWk0gixoabjF9Uctf2ZWLN6DAgRMBhycO3J9sq0uzB4QzmsAEim379iGddyW+Ljw jt9hX8p+pSwHMnuBfO55CguVWoHhqdm0K1YI2MzegK2LPKcMxsqGB1Acp69cJTO9rn /UR/BeiGEo2AgW56pA90JRX+1ADVzao4lQol4wBQ= Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1567757455-18747-18745/9/79; Fri, 6 Sep 2019 08:10:55 +0000 From: Arnt Gulbrandsen To: jmap@ietf.org Date: Fri, 6 Sep 2019 10:07:36 +0200 Message-Id: <3JsDnKuuU8BmlOR/U+XAJdVesldOC/B2YytQRSYoHQc=.sha-256@antelope.email> References: Mime-Version: 1.0 Content-Type: text/plain; format=flowed Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 08:07:43 -0000 If this is adopted, then I believe action item number one should be to consider why the IMAP equivalent was poorly supported, and number two to write principles for how to prevent the same problem (s). Arnt From nobody Thu Sep 12 19:29:24 2019 Return-Path: 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 ; 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 ; 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 ; 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: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrtdeigdeitdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerreejnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucffohhmrghinhepghhithhhuhgsrdgtohhmpdhivghtfhdrohhrghenucfrrghrrghm pehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmnecuve hluhhsthgvrhfuihiivgeptd X-ME-Proxy: 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: <0100016d259b980f-a2bc55f5-320e-4b67-bc51-1e327deb6762-000000@email.amazonses.com> Date: Fri, 13 Sep 2019 12:28:57 +1000 From: "Bron Gondwana" To: "John van der Kamp" , "jmap@ietf.org" Content-Type: multipart/alternative; boundary=f1b3cc04035b48b2a3bda02a92216e01 Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Sep 2019 02:29:23 -0000 --f1b3cc04035b48b2a3bda02a92216e01 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Yes, definitely. There's going to need to be some thought to get this wo= rking 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 war= ning, notifying the user he=E2=80=99s close to its quota unless actions = are taken. 2nd level would block outgoing messages. 3rd and last level a= lso blocks incoming emails bouncing those to the sender. Only the last l= evel would be required, the rest optional. It looks like this is missing= from the spec. Would it be worth considering? >=20 > John >=20 > *From:* Jmap [mailto:jmap-bounces@ietf.org] *On Behalf Of *Bron Gondwa= na > *Sent:* Friday, 6 September, 2019 02:37 > *To:* jmap@ietf.org > *Subject:* [Jmap] Call for adoption: JMAP QUOTA >=20 > Just to make it official! >=20 > This is a call for adoption for a specification for exposing (and pote= ntially also managing) quotas over JMAP. As there are already multiple p= eople in favour per the thread at https://mailarchive.ietf.org/arch/msg/= jmap/G4C83gJEgjrjxi52J7UKaMc9TpY I am asking now if there are any object= ions. >=20 > 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. >=20 > As a starting point we will work from https://github.com/linagora/jmap= /pull/19. >=20 > I believe this work is within our charter, specifically: >=20 >> Extensions to the existing core and* mail* JMAP specifications are al= so >> 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). >=20 > Quota exists as part of IMAP (RFC2087), so is in scope. >=20 > 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/do= c/draft-ietf-extra-quota/ >=20 > Regards, >=20 > Bron. >=20 > -- > Bron Gondwana, CEO, Fastmail Pty Ltd > brong@fastmailteam.com >=20 >=20 > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap >=20 >=20 >=20 > Amazon Development Center (Netherlands) B.V., Johanna Westerdijkplein = 1, 2521 EN The Hague, Registration No. Chamber of Commerce 56869649, VAT= : NL 852339859B01 >=20 >=20 -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com --f1b3cc04035b48b2a3bda02a92216e01 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
Yes, definitely.  There's going to need to be so= me thought to get this working correctly, and extensible to new datatype= s like the underway JMAP Calendars, and the soon to come JMAP Contacts!<= br>

Cheers,

Br= on.

On Thu, Se= p 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=E2=80=99s 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 leve= l would be required, the rest optional. It looks like this is missing fr= om the spec. Would it be worth considering?

=

 <= /span>

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 adopt= ion: JMAP QUOTA

&= nbsp;

Just to make it official!

 

=

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

 

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

<= p class=3D"qt-MsoNormal"> 

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

 <= br>

I believe this work is with= in our charter, specifically:

 

Extensions to the e= xisting core and mail JMAP specifications are also

=

within scope for this working grou= p, for example any additional parts

of SIEVE, IMAP, SMTP submission, as well as trans= port of JMAP over

WS= S (WebSocket over TLS, RFC 6455).

=

 

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

 

<= /div>

This proposed work will also take i= nto 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



Amazon Development Center (Net=
herlands) B.V., Johanna Westerdijkplein 1, 2521 EN The Hague, Registrati=
on No. Chamber of Commerce 56869649, VAT: NL 852339859B01



--
  Bron Gondwana, CEO, Fas= tmail Pty Ltd
  brong@fastmailtea= m.com


--f1b3cc04035b48b2a3bda02a92216e01-- From nobody Thu Sep 12 19:54:16 2019 Return-Path: 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 ; 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 ; 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 ; 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 ; 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: =?ISO-8859-1?Q?Beno=EEt_TELLIER?= Sender: =?ISO-8859-1?Q?Beno=EEt_TELLIER?= Reply-To: btellier@linagora.com To: "jmap@ietf.org" Message-ID: Date: Fri, 13 Sep 2019 02:54:03 +0000 References: <0100016d259b980f-a2bc55f5-320e-4b67-bc51-1e327deb6762-000000@email.amazonses.com> Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Sep 2019 02:54:15 -0000

Agree, there is no need to get this specific to emails=2E

L= e 13 septembre 2019 09:28, de brong@fastmailteam=2Ecom
Yes, I'm pretty sure the consensus was this is ready for WGLC.

Neil.
--26ad092db9f744639bec7fdb783c5333-- From nobody Mon Sep 30 01:41:51 2019 Return-Path: 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 ; 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 ; 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 ; 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 ; 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: =?ISO-8859-1?Q?Ren=E9_CORDIER?= Sender: =?ISO-8859-1?Q?Ren=E9_CORDIER?= Reply-To: rcordier@linagora.com To: "jmap@ietf.org" Message-ID: Date: Mon, 30 Sep 2019 08:41:42 +0000 References: Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 ad= option that will definitely deserve some attention, like multiple levels of= quotas, or trying to understand why quotas with IMAP were not widely suppo= rted and what can we do to change it with JMAP=2E

But I don't rememb= er seeing any strong objection to it ! The vote was supposed to finish Frid= ay 20th of September=2E Is it reasonable to ask to move forward then?

Regards,

Rene=2E

Le 6 septembre 2019 07:36, de brong@fa= stmailteam=2Ecom
Just to make it official!

This is a call for adoption fo= r a specification for exposing (and potentially also managing) quotas over = JMAP=2E  As there are already multiple people in favour per the thread= at https://mailarchive=2Eietf=2Eorg/arch/msg/jmap/G4C83gJEgjrj= xi52J7UKaMc9TpY I am asking now if there are any objections=2E

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

As a starting point we will work from https://github=2Ecom/linago= ra/jmap/pull/19=2E

I believe this work is within our charte= r, specifically:

Extensions to the ex= isting core and mail JMAP specifications are also
within scope for this working group, for example a= ny additional parts
of SIEVE, IMAP, SMTP submission, as well as transport of JMAP over
WSS (WebSocket over TLS, RFC 6455)=2E

Quota exists as part of IMAP (RFC2087), so is in scope=2E=

This proposed work will also take into account the work on IMA= P quota being done in the EXTRA working group on https://datatracker=2Eietf= =2Eorg/doc/draft-ietf-extra-quota/

Regards,

Bro= n=2E

--
 = Bron Gondwana, CEO, Fastmail Pty Ltd
&nb= sp; brong@fastmailteam=2Ecom


From nobody Mon Sep 30 03:39:00 2019 Return-Path: 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 1BFB81201E5 for ; Mon, 30 Sep 2019 03:38:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=rEMS9K1T; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=U3LHG4sc 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 YWuoCfN68Xg8 for ; Mon, 30 Sep 2019 03:38:57 -0700 (PDT) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19A2812006B for ; Mon, 30 Sep 2019 03:38:57 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id E62C7676 for ; Mon, 30 Sep 2019 06:38:53 -0400 (EDT) Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Mon, 30 Sep 2019 06:38:54 -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=afaOFlS Hvcu44R1wtxGuTYpvOXgpWogN5mE9TxmpSKA=; b=rEMS9K1TbKiyHlyCLIuWJ68 MIjq8Gz8BWwXX9+CCm/q8oHqhsyjd4kwfHHPJtRKAmvjblIws2kuoPhTwyHUl6tU J8OVDae4+6OyKAj1q5NJZokOdlthLmhGoFLS1Etjnd1LBQji4t4irL2zPJgF4etb Tjcs7ckDzOuZJuGPpsKVXonzzHcd1NoW63rHmwhNYL+/d+5cYj7J3MTDE7vcdvDw edfX0/PiEOj4BaIX2C3a4Y15ha8a5PIVAZ8dHmvvmyAjG6FlREWq1enh8HDMfYZS 212A8mZw+1mr0CLguhIFGua/15m7eVxdGh9E6I07Hh5mhUN+NmhVFI0NHxcf2ng= = 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=afaOFl SHvcu44R1wtxGuTYpvOXgpWogN5mE9TxmpSKA=; b=U3LHG4sc+DsnJV6oGLL4Pb fTAr8vap93Z/vn9IzVJMYUMTS+A9D87VMZCAl6qXR8/2uUrbEju4pYKHVoILCT5V xI2no3ajjb4rKQ0P4ie3BO+4n3AjhUI0VWFY2tOj7RfLO+R2JK86XjDAUwlKeFJf ZwUqcv8yPSHb3V4ayNDcxGh58bavYd/kpew27MvzFZ1rpgAcfslcxsQsfYDQ7HWB jFuX76yh6IwdtwdaV0nU/a1Qi8+hwdDvlRyvDK+lQXLgTRuyOFN5i5hwBPUgdiFb 5u+JHAHVxPkpnCos5ci52IfZLWvrQyRbXyQ1VtncVSoaAjAzKNxO0qfFOTDvgyVw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgedvgddvjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuffhomhgrihhnpehgihhthhhusgdrtghomh dpihgvthhfrdhorhhgnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghs thhmrghilhhtvggrmhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3803F308DEB; Mon, 30 Sep 2019 06:38:53 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-319-g87cda76-fmnext-20190926v2 Mime-Version: 1.0 Message-Id: <9d37d5c2-2929-494a-90e5-053b675a55cf@www.fastmail.com> In-Reply-To: References: Date: Mon, 30 Sep 2019 20:38:42 +1000 From: "Bron Gondwana" To: jmap@ietf.org Content-Type: multipart/alternative; boundary=43a89163539f4e4680f50e97b8d1ccb8 Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Sep 2019 10:38:59 -0000 --43a89163539f4e4680f50e97b8d1ccb8 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable For sure! Sorry I forgot to move forward on it. If you could upload it w= ith the name draft-ietf-jmap-quota then we can start work on the next re= vision :) It will obviously be on the agenda for Singapore as well. Cheers, Bron. On Mon, Sep 30, 2019, at 18:41, Ren=C3=A9 CORDIER wrote: > Hi everybody, > I believe I saw some concerns during the call for adoption that will d= efinitely deserve some attention, like multiple levels of quotas, or try= ing to understand why quotas with IMAP were not widely supported and wha= t 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! >>=20 >> This is a call for adoption for a specification for exposing (and pot= entially 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 objec= tions. >>=20 >> 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. >>=20 >> As a starting point we will work from https://github.com/linagora/jma= p/pull/19. >>=20 >> I believe this work is within our charter, specifically: >>=20 >>> Extensions to the existing core and* mail* JMAP specifications are a= lso >>> within scope for this working group, for example any additional part= s >>> of SIEVE, *IMAP*, SMTP submission, as well as transport of JMAP over= >>> WSS (WebSocket over TLS, RFC 6455). >>=20 >> Quota exists as part of IMAP (RFC2087), so is in scope. >>=20 >> 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/d= oc/draft-ietf-extra-quota/ >>=20 >> Regards, >>=20 >> Bron. >>=20 >> -- >> Bron Gondwana, CEO, Fastmail Pty Ltd >> brong@fastmailteam.com >>=20 >>=20 > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap >=20 -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com --43a89163539f4e4680f50e97b8d1ccb8 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
For sure! Sorry I forgot to move forward on it. = If you could upload it with the name draft-ietf-jmap-quota then we can = start work on the next revision :)

It will obviously be o= n the agenda for Singapore as well.

Cheers,

Bron.
<= /div>

On Mon, Sep 30, 20= 19, at 18:41, Ren=C3=A9 CORDIER wrote:

Hi everybody,

I believe I saw some concerns dur= ing the call for adoption that will definitely deserve some attention, l= ike multiple levels of quotas, or trying to understand why quotas with I= MAP 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 t= o ask to move forward then?

Regards,

Rene.

Le 6 septembre 2019 07:36, de bron= g@fastmailteam.com
Just to make it official!

This is a call for ado= ption for a specification for exposing (and potentially also managing) q= uotas over JMAP.  As there are already multiple people in favour pe= r the thread at https://mailarchive.ietf.org/arch/msg/jmap/G4= C83gJEgjrjxi52J7UKaMc9TpY I am asking now if there are any objection= s.

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 http= s://github.com/linagora/jmap/pull/19.

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

Extensions to the existing core and mail JMAP specific= ations are also
within scope = for this working group, for example any additional parts
of SIEVE, IMAP, SMTP submission, as w= ell as transport of JMAP over
WSS (WebSocket over TLS, RFC 6455).

Quota e= xists as part of IMAP (RFC2087), so is in scope.

This pro= posed 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.
<= div style=3D"font-family:Arial;">
--
 = Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com

<= div>_______________________________________________
Jmap m= ailing list
Jmap@ietf.org
https://www.ietf.o= rg/mailman/listinfo/jmap


--
  Bron Gondwana, CE= O, Fastmail Pty Ltd
  brong@fastm= ailteam.com


--43a89163539f4e4680f50e97b8d1ccb8-- From nobody Mon Sep 30 04:17:58 2019 Return-Path: X-Original-To: jmap@ietf.org Delivered-To: jmap@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB0812021D; Mon, 30 Sep 2019 04:17:49 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: internet-drafts@ietf.org To: Cc: jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.103.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <156984226896.429.13366509735221679840@ietfa.amsl.com> Date: Mon, 30 Sep 2019 04:17:49 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-quotas-00.txt X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Sep 2019 11:17:49 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the JSON Mail Access Protocol WG of the IETF. Title : JMAP for Quotas Authors : René Cordier Michael Bailly Filename : draft-ietf-jmap-quotas-00.txt Pages : 7 Date : 2019-09-05 Abstract: This document specifies a data model for handling quotas on mailboxes with a server using JMAP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-quotas/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-jmap-quotas-00 https://datatracker.ietf.org/doc/html/draft-ietf-jmap-quotas-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Sep 30 21:48:03 2019 Return-Path: X-Original-To: jmap@ietf.org Delivered-To: jmap@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AFC612002E; Mon, 30 Sep 2019 21:48:01 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: jmap@ietf.org, brong@fastmailteam.com, jmap-chairs@ietf.org, aamelnikov@fastmail.fm X-Test-IDTracker: no X-IETF-IDTracker: 6.103.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <156990528109.24132.6509905397045618523.idtracker@ietfa.amsl.com> Date: Mon, 30 Sep 2019 21:48:01 -0700 Archived-At: Subject: [Jmap] jmap - New Meeting Session Request for IETF 106 X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.29 List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2019 04:48:01 -0000 A new meeting session request has just been submitted by Bron Gondwana, a Chair of the jmap working group. --------------------------------------------------------- Working Group Name: JSON Mail Access Protocol Area Name: Applications and Real-Time Area Session Requester: Bron Gondwana Number of Sessions: 1 Length of Session(s): 1 Hour Number of Attendees: 20 Conflicts to Avoid: Chair Conflict: doh oauth saag iasa2 dmarc artarea uta dispatch extra calext Technology Overlap: tls httpbis ace lamps core t2trg People who must be present: Alexey Melnikov Jim Fenton Neil Jenkins Bron Gondwana Resources Requested: Special Requests: Jim has nomcom all Friday, so we can't do Friday. ---------------------------------------------------------