From nobody Wed Oct 23 14:50:53 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 8B344120DDE for ; Wed, 23 Oct 2019 14:50:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.101 X-Spam-Level: X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net 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 H9pu5z0L_UUP for ; Wed, 23 Oct 2019 14:50:45 -0700 (PDT) Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC2AA120E0B for ; Wed, 23 Oct 2019 14:50:43 -0700 (PDT) Received: from steel.local ([IPv6:2601:647:4300:2290:cd96:b454:a08:1d66]) (authenticated bits=0) by v2.bluepopcorn.net (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x9NLogA9031829 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 23 Oct 2019 14:50:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1571867443; bh=EJwZkt9kINM+QVw1YKkwWM2BaM5va4ywaq2uSHqRT+A=; h=To:From:Subject:Date; b=Vmc+60eUNhGqiX7jW8VUCAJtKlfe3tDFPJOE3OfVDbaOePOFew75sEa/wVWBM/YTb hqIOUXu1QUo1F+NmuCWpAnLs3cmNe9mIIb0bBRF3kafwIlEOeXS0ql0yv4x6tmHpU9 qnJr4rZmBH9Ensyqh5hGqy27kLJqtTLHMEZmPbz8= To: jmap@ietf.org From: Jim Fenton Openpgp: preference=signencrypt Autocrypt: addr=fenton@bluepopcorn.net; prefer-encrypt=mutual; keydata= mQINBFJNz0MBEADME6UoNSsTvSDJOdzL4yWfH4HTTOOZZPUcM/at38j4joeBb2PdatlwCBtk 9ZjupxFK+Qh5NZC19Oa6CHo0vlqw7V1hx1MUhmSPbzKRcNFhJu0KcQdniI8qmsqoG50IELXN BPI5OEZ3chYHpoXXi2+VCkjXJyeoqRNwNdv6QPGg6O1FMbB+AcIZj3x5U18LnJnXv1i+1vBq CxbMP43VmryPf8BLufcEciXpMEHydHbrEBZb/r7SBkUhdQXjxRNcWOLeYvOVUOOrr1c+jvqm DEbTWUJVRnUro/WpZQBffFnymR0jjkdAa8eOVl/nF2oMLbaBsOMvxCRSSEcGhuqwbEappNVT 1nuBTbkJT/GGcXxc+lEx9uNj86oYC4384VZJMTd1BRI4qPXImNZCIdmpKegK743B6xxN6Qh1 Tg167pn9429JENQE/AFIVX5B/gpsg7Aq+3rmz9H6GbfovPvFV3TBTgsHCHAMC8XU+S4fhcqN PN0lbUeyb7g6wxaE+dYqC7TExx7G3prw4v66y0qS7ow/Cfw8XXOEkaFQ4XwP7nvfILT+9CcU yS8I40vlDFU9Wnt56CbGz0ZVQgHnwyPXL+S9kCcIwRLFx1M79s6T6qwX1TXadfpbi1uIw7XG TiPDT8Pk6i2y22oSSROyYD4D+wOhVkkvO0S8iZ3+LhAYUx86nwARAQABtCNKaW0gRmVudG9u IDxmZW50b25AYmx1ZXBvcGNvcm4ubmV0PokCVQQTAQIAPwIbAwYLCQgHAwIGFQgCCQoLBBYC AwECHgECF4AWIQS1nUkJe2fEXbvBaacbJaiwFdCfvgUCXVD9ggUJDORhvgAKCRAbJaiwFdCf vgiSEACd3Nem63zL2C6daCFfRzOANkf30Q8AvaRVwhfdFxs+5vETCzbqctrtIAHeqncXjm9G uEJWxecAiHZXKoWUEFECMp3+Saznw0np+c722M4k9xI+mxqbcE0qgpYQgA8zbS/Lbds3f/bk /00jrQg4VMkumONlh+RZVwxAsnWp8efrJsNTn0QOPZavAkPEN59wfyWQ3O4pNY8i3zum8Wge 8NS4BBMyG0fmjWgUq0K2QrTD4AKBslM2IWCLECypP1AOfHKmmTACKFOnzJJ4KspUw3hdBnS1 fvudUC8u26Q3T6rHosRqxGmgW7sQWwAusgMSa/A6zxR6soEBSsMT5Tf+VHebuz1FWE4ogrvJ InvewfYSCYzOQamYYGArcBtAzU00pUzW2Or7SlwZPHHy2EfMd0zvT7mwSYLwwwcCsWc1O/CI xHGea7PBgO3TdR0Ex254yc+NTyxF3isBC/fodF9aNWF6x6SV3VKYJ3U2uqS9ga85dZz8Qeps MwlSEGRVhVVWGbSxy0GxV5Up0yX4vl0kI0c7Tt57JCOoRBpn/lTK/7IEtZK6/uiw98KCy+BM uF7HPsgXjd/AQjSsZIJgDyVY/y7niduqhW2izNEdhV77htVbKHRf2SfJQNudWOIcOhUTlddH kOSjet+MDso61JxrFV4j/8wFno7NwpPIhD//HvKAiLkCDQRSTc9DARAAwZaXYs3OzGlpqvSH 3HR9GjSzIeP0EmsBCjpfIdZbQBwQ3ZREiMGInNxV+xkdjLDg0ctrWzUCUe3plWe5NJkpjqm+ KMc7GKhyeWJ5MZRtVrh0VpFTqi8UwYPWumAYqE1y/U1me/zHpfG9EDwdSYqMkPF76Fy5W+vh ZP2ILKaY8qWSLyH8TPl5mFGBypfT8Q6UuzlRs2aTbsTtBX/qwH7gztMRJSjQtYo20AqCgBBH IA/0xV5qDH7CVYyKyPQ4tJLQ8/xyTysUS5fewrj8lZo/G9SaNtC3CEvrJYwyA0nvYB6+hJPM qMP/tyRXM/9XY3qO4Vxuc+m5fYbTZa5GYAZNNuB5dvqI1U0sFTWBEbpAeabqCQ40ZnFSj+t1 tBuwfj4ey/oJ78WRyg5+VTvPKRRubOmZcnzj5yfTS3VGxAZb4Nsj1S2f3KLP0Z+Cv4dt893I 2JWTChw7jA1omF0QTQaBq140n084PFndBHudrZ3cz+APC89iie2HQ4jGQldXZXnGySHnHlA+ WUyZ9wgOplW9F4Q/Lps1bnuh5VttPVpNfjX8hiV48al+b+ut4nfzXAripIRWF3TL72/6JqgE KNhRKyRn0S6BidieSyHWzqJR3Roi/YNTvyXyLh6i6jtByb3FbnhYf/9olobDpj0E+kTemLrw owre85gwupSphqlzVSUAEQEAAYkCPAQYAQIAJgIbDBYhBLWdSQl7Z8Rdu8FppxslqLAV0J++ BQJdUP9SBQkM5GOPAAoJEBslqLAV0J++vZoP/1shJ+5iImGzvGUTTDJcAX6Wha+22QP0G51Z QGZbeB0gE+gDmRwd2yw0cO3y1sPoTJliUSuZ3DFIjv8CLBgDlrkUnijBWbi5YznsAZkH0vKG ESGzinJC6y/Nzf2TZokKiOaYrTYcZx8x2wxjNO+zsihm/rvhV/YnHEYd9dlV/MjAL3xtHU/9 fNcTDtF3RchADyVCxlqrRUkFj61dHxU+U5JRftyIliLltsy2Nlr4uAsxNX+tpAH2D2HLmjwx bV2fpTnFCVImtuo6ZqNZ8SMk1Xq0fBBdo3acBw42kL/qGIKS9x3NWEy8vsmQXn0QqNBd1Q62 9ghm82mHMTRKnOXqkMgICpZ0HffPf3p7zMkEqWptgEHxE6ZHm9hJMGEf8RED9DCYh+N1uFaM 7ndQPPFKlj80sGmNF9+01mO53hrxeL/WAdGox/STpTb2BDpiyrLdT/2R0vJNEfMxBBYlw1gc g8mPEwHwZ940/qql7e41TkDGUZa2a1WegKLj8hK1pgDDBptcdIvlvuk284jOZ2/jDyaBDsMf 310OoJchJ3977odtSCArybQIwMjTx0rv6dqjsuqP89jqlrGV6izqf1n4p4FNrBSWOSRGaoWD JJVHL4YUhP44G5xDBCtp3TqatLa5F2Rgxj50EFIzOuu9Pg1tBCPP1G+0EiikVTdDkC63X4RG Message-ID: Date: Wed, 23 Oct 2019 14:50:37 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: [Jmap] WGLC on draft-ietf-jmap-websocket-03 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, 23 Oct 2019 21:50:52 -0000 Since there was consensus in Montreal that this is ready to go: This starts a 2 week Working Group Last Call on draft-ietf-jmap-websocket-03. Please provide your feedback on this document by November 6, 2019. -Jim (and Bron) From nobody Fri Oct 25 14:14:05 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 C755012082E; Fri, 25 Oct 2019 14:12:05 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: jmap@ietf.org, aamelnikov@fastmail.fm X-Test-IDTracker: no X-IETF-IDTracker: 6.108.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <157203792581.2724.3322925912997791049.idtracker@ietfa.amsl.com> Date: Fri, 25 Oct 2019 14:12:05 -0700 Archived-At: Subject: [Jmap] jmap - Requested session has been scheduled 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: Fri, 25 Oct 2019 21:12:10 -0000 Dear Bron Gondwana, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. jmap Session 1 (1:00 requested) Tuesday, 19 November 2019, Afternoon Session III 1710-1840 Room Name: Orchard size: 50 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/106/sessions/jmap.ics Request Information: --------------------------------------------------------- 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. --------------------------------------------------------- From nobody Mon Oct 28 00:08:32 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 D9C0412002E; Mon, 28 Oct 2019 00:08:25 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.108.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <157224650580.19966.17670159316495543755@ietfa.amsl.com> Date: Mon, 28 Oct 2019 00:08:25 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-calendars-01.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, 28 Oct 2019 07:08:26 -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 Calendars Authors : Neil Jenkins Michael Douglass Filename : draft-ietf-jmap-calendars-01.txt Pages : 37 Date : 2019-10-28 Abstract: This document specifies a data model for synchronizing calendar data with a server using JMAP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jmap-calendars/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-jmap-calendars-01 https://datatracker.ietf.org/doc/html/draft-ietf-jmap-calendars-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jmap-calendars-01 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 Oct 28 00:48: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 3E94C120041 for ; Mon, 28 Oct 2019 00:48:43 -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=KuvZnsmj; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=bGphOfN1 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 UUKwG5NZ3vNh for ; Mon, 28 Oct 2019 00:48:41 -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 CC75112002E for ; Mon, 28 Oct 2019 00:48:41 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 0CEEA47B for ; Mon, 28 Oct 2019 03:48:38 -0400 (EDT) Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Mon, 28 Oct 2019 03:48:39 -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=fm1; bh=1z0kigU 32kcGFfbKa74ybHhRBjuPPpZxrS0HkX2RdPA=; b=KuvZnsmjHDD5AzOtG7uRtzf DiOCcqqqwpHdg2GJaPE4Z+HaGgxCupgxnHE0OptRjvFuZL0aFEOmFwf8t9iajLYY zdDzcnkSsBOvCNgQ9NuD7hnI5cEqbUtHQ2Uyi5X5iEn5Avl3BrDptxujl8pQGBg+ rp/LgKLeL685/nRqh0BFiOn3L3yMUVNkF3KYlHqHDJmJ51h/RXmE7qJDxtlS3tiw oj4zAXZ0MSYnmW8Lwex5ntkDb0q2eTLpy4lGn/vbYzEiG6E44/Oep1fbWlaclnb+ dKLzZebYNqXFzFB8ok6l4pedPPMxvMRN5W8q/AGa8CVFQMT4ckHKpYQY/2SU28Q= = 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=fm1; bh=1z0kig U32kcGFfbKa74ybHhRBjuPPpZxrS0HkX2RdPA=; b=bGphOfN1WQf9RIt5sEUj+q L+3EJ4dZ2ULVnx/jo53Vk8UCgPHnE7/Ql8yZhgBCmsFWXxUsJCIgHLEsJO3KpndW xisVE2ZNZD1zaqmtiTjGbKmVTYIoxQHooPmTGnRk94aALPgq5K0pei1YvdlUAnzI +BN+IB769AFnnfWdDfsSdEr0TWMeH2eRn46si1jP+CHGuzK0poAG+XVK2cYFJqcW T8TwWElCPHUfcYm1mC7VZJZvcUcZYFZdAsZYeYTb8z18bIqcSTTam8wJ/QQHnAbJ eAPT3AloTXWoru9hyx2faE9w9ahcagehyUDRReT2bPpZjtrRti7obTnlx9s40PIA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrleekgdduudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucffohhmrghinhepihgvthhfrdhorhhgnecurfgrrhgrmhepmhgrihhlfhhrohhmpehn vghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomhenucevlhhushhtvghrufhiiigvpe dt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 2A74B4052CC; Mon, 28 Oct 2019 03:48:38 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-470-gedfae93-fmstable-20191021v4 Mime-Version: 1.0 Message-Id: In-Reply-To: <157224650580.19966.17670159316495543755@ietfa.amsl.com> References: <157224650580.19966.17670159316495543755@ietfa.amsl.com> Date: Mon, 28 Oct 2019 18:48:17 +1100 From: "Neil Jenkins" To: "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=e81048737bac4f5d86b22c783563e983 Archived-At: Subject: Re: [Jmap] I-D Action: draft-ietf-jmap-calendars-01.txt 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, 28 Oct 2019 07:48:43 -0000 --e81048737bac4f5d86b22c783563e983 Content-Type: text/plain Hi all, I've just published a big update to the JMAP calendars spec that fleshes out all the functionality I think is required. There are still a few TODOs to fill in, refinements needed and implementation experience required, but I think the bulk of it is there. Please have a read and post any comments on the mailing list here or bring them to IETF106 where we will discuss any open issues, missing functionality, tricky edge cases etc. Cheers, Neil. --e81048737bac4f5d86b22c783563e983 Content-Type: text/html
Hi all,

I've just published a big update to the JMAP calendars spec that fleshes out all the functionality I think is required. There are still a few TODOs to fill in, refinements needed and implementation experience required, but I think the bulk of it is there. Please have a read and post any comments on the mailing list here or bring them to IETF106 where we will discuss any open issues, missing functionality, tricky edge cases etc.

Cheers,
Neil.
--e81048737bac4f5d86b22c783563e983-- From nobody Mon Oct 28 22:21: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 1F60F1200B1 for ; Mon, 28 Oct 2019 22:21:00 -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=wMUh0Pnm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=R8vkIl75 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 R9jQfWzn27nC for ; Mon, 28 Oct 2019 22:20:58 -0700 (PDT) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FAD5120043 for ; Mon, 28 Oct 2019 22:20:58 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 7B75E396 for ; Tue, 29 Oct 2019 01:20:57 -0400 (EDT) Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Tue, 29 Oct 2019 01:20:57 -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=fm1; bh=0ZhQirn Nmg7bgEUu9C4Y0SpButE9O01iliX2H7rrQds=; b=wMUh0PnmqfLWQiNBzHMMtew 4g7m8BBvY8sPr/98o8fLBe+dcqx1lmJO7rk5aTtBE8awlco640EFlfasXHneSlJh GM/EQH8bWmH5I05vI5j7jbs2+IdWlsMJJ8ulMfasMmdlOtfn81n/Nre/i4gYKgrO BejFjeMMWdogEqPbYGit6eaTvcthsYUEVqJoJOJGdMO3j3ygco3Ko2OmFiX2Wx1n L4mwHZ9vazG/7v4IGCG0iztkLWnbd0wgSol8vpdQrCETDvzkoSaLwwbGgBGEybMq tWmq4sRJGaFnTW0npkXsbzzioDo6QChdSdekqkghU1tK04DwV+UE3+jHK4Ai1mw= = 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=fm1; bh=0ZhQir nNmg7bgEUu9C4Y0SpButE9O01iliX2H7rrQds=; b=R8vkIl753d+k0pZ8mxBJIX BaxdOil0JPPsfldoqCDWdfqCC/EOiFj6CF1D8ODZKeFatQCb3zcLP0VBwYXqWY2P 135brswf4l/sag/OB9g7WgBuyUOK1w1VWpRF4svfAaHE685t6J8iy2Lh0XsqW/qS vQDlYUSXABOzwHna8d+I1Z7x7A26yRLceUVBEM2kx9z40GH+E4WbQ89iMP5qWqzm RAGLogB8vGZoUdoP8iJOP0NERbgGtfZdjFL2ovWaroYauIjnffz6GOIFIPfMef// ddmMt4wm0lzqZ1h8hCNVuslIQTq4JOiuV3cE7dJYcwxeofDSAJWn8YxR864wUPbA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddttddgkeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucfrrghrrghmpehmrghilhhfrhhomhepnhgvihhljhesfhgrshhtmhgrihhlthgvrghm rdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id C6930406E4B; Tue, 29 Oct 2019 01:20:56 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-512-g193a140-fmstable-20191028v1 Mime-Version: 1.0 Message-Id: In-Reply-To: <156984226896.429.13366509735221679840@ietfa.amsl.com> References: <156984226896.429.13366509735221679840@ietfa.amsl.com> Date: Tue, 29 Oct 2019 16:20:36 +1100 From: "Neil Jenkins" To: "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=700a52d852a04e58902730ac8acff729 Archived-At: Subject: Re: [Jmap] I-D Action: draft-ietf-jmap-quotas-00.txt 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: Tue, 29 Oct 2019 05:21:00 -0000 --700a52d852a04e58902730ac8acff729 Content-Type: text/plain Some feedback on this draft: * It's mail-specific at the moment, but could probably be made pretty generic, which I think would be more useful. e.g. Instead of "mesageCount" and "mesageStorageSize" we'd just have "size" or "count" as the types of quota, which could apply to any object type. Then you have another property on the Quota object that lists the data type(s) it applies to. * I'm a bit unclear on how "usedScope" and "limitScope" could be different and what this would mean in practice (and if this is actually done in the real world). * I'm not sure I see the purpose of the "quotaIds" property addition to the Mailbox object. I feel it would be cleaner not to add this (but add a property to the Quota object to indicate a subscope if it only applies to a subset of the objects of that type in the account). Cheers, Neil. --700a52d852a04e58902730ac8acff729 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Some feedback o= n this draft:

  • It's mail-specific at the = moment, but could probably be made pretty generic, which I think would b= e more useful. e.g. Instead of "mesageCount" and "mesageStorageSize" we'= d just have "size" or "count" as the types of quota, which could apply t= o any object type. Then you have another property on the Quota obje= ct that lists the data type(s) it applies to.
  • I'm a bit unclear = on how "usedScope" and "limitScope" could be different and what this wou= ld mean in practice (and if this is actually done in the real world).
  • I'm not sure I see the purpose of the "quotaIds" property addi= tion to the Mailbox object. I feel it would be cleaner not to add this (= but add a property to the Quota object to indicate a subscope if it only= applies to a subset of the objects of that type in the account).

Cheers,
Neil.
<= /html> --700a52d852a04e58902730ac8acff729-- From nobody Tue Oct 29 00:42:36 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 91CF51200BA for ; Tue, 29 Oct 2019 00:42:34 -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 KVc6NVTN-645 for ; Tue, 29 Oct 2019 00:42:32 -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 850D212007C for ; Tue, 29 Oct 2019 00:42:32 -0700 (PDT) Received: from linagora.com (unknown [10.233.69.202]) by outgoing.linagora.com (Postfix) with ESMTP id 4903C3B for ; Tue, 29 Oct 2019 07:42:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linagora.com; s=s20181122; t=1572334950; bh=WDglFLM6sZsg4Vhkzp9B0L1+qPUk83+9ljzVWmK5am8=; h=From:Reply-To:To:Subject:Date:References:From; b=qFCbc9C3fq4swgg4yuXTM7+z2B6FXtwEh4bv0AzLSojVL1675V69TmZp5tws5drA2 GZATfsP7jNBdMue+pXZdwwLbNXpVjzLJc5cfbffq05tR6Eeg8U5YyszzzykE0jJiK9 nbGKaYAqcXlQatZXSWyIjS8UMIXU83ejqvjBIV2GEMx4Tq0fjg8JlRRvbIiA+Pivzd zd8QfjgGqtGp+47p0KT8ypbWQWY2TxFrew/rR6Z69mjI4pzCV2JVv66uawwaY4bX4n eKyaLylVaLZeXh4kf20Km9XvmkGdHfVA+N/nybbp9xIl7L/ZlpqdNeSWvcMPhrp7dW aR5OX6LOwS5qA== 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: IETF JMAP Mailing List Message-ID: Date: Tue, 29 Oct 2019 07:42:22 +0000 References: <156984226896.429.13366509735221679840@ietfa.amsl.com> Archived-At: Subject: Re: [Jmap] I-D Action: draft-ietf-jmap-quotas-00.txt 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: Tue, 29 Oct 2019 07:42:35 -0000

Hi Neil,

Le 29 octobre 2019 12:20, de neilj@fastmailteam= =2Ecom

Some feedback on this draft:

  • It's mail-specific at the moment, but could probab= ly be made pretty generic, which I think would be more useful=2E e=2Eg=2E = Instead of "mesageCount" and "mesageStorageSize" we'd just have "size" or = "count" as the types of quota, which could apply to any object type=2E The= n you have another property on the Quota object that lists the data t= ype(s) it applies to=2E


+1

=
  • I'm a bit unclear on how "usedScope" and "limitScope" could be dif= ferent and what this would mean in practice (and if this is actually done = in the real world)=2E


For instance imagine th= at I define that users of my email server will not store more than 2 GB of = data

Bobs stores 1 GB of mail in his mailboxes thus have a 50% size= quota=2E The upper bound is the generic limit user on this mailserver has= =2E (limitSope is "global" , usedScope "personal")

Alice asked for = a 10 GB quota upper bound, specififc to her=2E Given that she has 1 GB ema= il, she has 10% size quota (limitSope is "personal" , usedScope "personal"= )

Imagine now that a mail provider proposes cold storage for achive= d mailbox=2E  It could be interesting to expose two quota on an accou= nt: (limitSope: personal , usedScope :personal) & (limitSope: persona= l/archive , usedScope :personal/archive) (JMAP custom vendor extension) - The client supporting the extension will be able to correctly con= textualize both quota, and display correct explanation in a UI
 - = The not aware client will  be able to recognise "the default quota" t= hat applies for the account, and will be able to explein that another quot= a applies, though the exact definition of it is unknown=2E

Another = example where it could be useful is if I have a cloud provider email subs= cription for a enterprise=2E We can imagine offers like "1TB company wide,= define user quota as you wish"=2E

As far as I understand it, IMAP = quota RFC limit itself to expressing the limitation=2E There is no explana= tion of the "why" behind it despite potentially complex combination possib= ilities=2E I have no idea if this is a problem, and thus if it should be a= ddressed though=2E


  • I'm not sure I se= e the purpose of the "quotaIds" property addition to the Mailbox object=2E= I feel it would be cleaner not to add this (but add a property to the Quo= ta object to indicate a subscope if it only applies to a subset of the obj= ects of that type in the account)=2E


Why would= it be cleaner?

From a client perspective, I can back reference the = quotaIds after a mailboxes/get call, which is easy to implement=2E

= While if I have a quota that lists entities it applies to I got a quota o= bject change every time a new entity aplies this quota=2E Is this desirabl= e or useful?


Cheers,
N= eil=2E


Cheers,

Benoit

From nobody Tue Oct 29 17:58:42 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 8248B1200A3 for ; Tue, 29 Oct 2019 17:58:40 -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=K5wc+IXx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=MB5UOaM2 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 ngBP9p-e-TLu for ; Tue, 29 Oct 2019 17:58:38 -0700 (PDT) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50702120052 for ; Tue, 29 Oct 2019 17:58:38 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 7F42921CC3 for ; Tue, 29 Oct 2019 20:58:37 -0400 (EDT) Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Tue, 29 Oct 2019 20:58:37 -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=fm1; bh=GGQoc/q gBaZN2NvJWZfv9zvkeRqd5SFJZNCBi7yMC3U=; b=K5wc+IXxQi1tmzE4kdIAU1Z 8vb6KE854jRTcHRmG+eSRGPTbLYlhSOynAevaw8xqlw36tkEfiv1UW83Cizwldzo SycaOSzHxR9h1LEexRVU6NE+5KALwnEAbyiXAndPWn9ySCsL+tLJqFOVoCCLLARy HNfVbclc2A3+PQA9Ls4h895avyc3RU/4iAbKfq6k1rEGSc9ZOBEZKFfOnOb0hg1m 0aBMWE4vR1dlWRLdUfJtvInP6KEklS4UoHDTVS9WKMBoeMfRZs2j7eoX0gm/7+9q /ik4diURlBG4y25wLvCFJbxS6Yl59LstugwbIGUwJMXjdhrGl/4YaY+KINmuOwA= = 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=fm1; bh=GGQoc/ qgBaZN2NvJWZfv9zvkeRqd5SFJZNCBi7yMC3U=; b=MB5UOaM2TzuyipBgimkTg6 XXwTdollak4LYuCREw3roRAM0+9GECIsw5w50gX0OsZl2ytd+NT9SRT/vAMsZR4P zA1tf1EyZ7zIWK3370DP7NzTbNfyN/PBK7kjLDn3TpXydso2HUarZ4u7lxc1cPG0 7HQZ6/oCKcYsZRFKogI2B5OgHt0MXUtDjAH812DLAkcMxy2+KCvja+Uy2lQSY8Cw JNtEeuDbpU26BvJ6BJqTouH51fxDH/FW3qhiqNtqRaqUIfCFAM/RgQ+o2v00VRn6 bn1oYyvrH753+xlzYIK7FxJokwLynqvq4MiJb4EfWIHBUPmMfhxBny3wm+D5WY6g == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddtvddgvdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucfrrghrrghmpehmrghilhhfrhhomhepnhgvihhljhesfhgrshhtmhgrihhlthgvrghm rdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 40047300096; Tue, 29 Oct 2019 20:58:36 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-512-g193a140-fmstable-20191028v1 Mime-Version: 1.0 Message-Id: <8a6148de-989f-4315-882a-666e5d2558ab@dogfood.fastmail.com> In-Reply-To: References: <156984226896.429.13366509735221679840@ietfa.amsl.com> Date: Wed, 30 Oct 2019 11:58:16 +1100 From: "Neil Jenkins" To: "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=51f094d9512b4f97abed70a6175f25d6 Archived-At: Subject: Re: [Jmap] I-D Action: draft-ietf-jmap-quotas-00.txt 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, 30 Oct 2019 00:58:41 -0000 --51f094d9512b4f97abed70a6175f25d6 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable On Tue, 29 Oct 2019, at 18:42, Beno=C3=AEt TELLIER wrote: > For instance imagine that I define that users of my email server will = not store more than 2 GB of data >=20 > Bobs stores 1 GB of mail in his mailboxes thus have a 50% size quota. = The upper bound is the generic limit user on this mailserver has. (limit= Sope is "global" , usedScope "personal") That doesn't sound like a global scope to me: it's a personal scope. It = would be a global scope if there was 2 GB quota shared between different= accounts and the usage in any counted towards it (like a Family iCloud = account for example). But then you need to show the global usage too, ot= herwise it's not very useful! > - The client supporting the extension will be able to correctly conte= xtualize both quota, and display correct explanation in a UI I'm not quite sure what you imagine such a UI would look like. I'm strug= gling to think of anything that would be understandable by >10% users. C= an you point to an example? > From a client perspective, I can back reference the quotaIds after a m= ailboxes/get call, which is easy to implement.=20 >=20 > While if I have a quota that lists entities it applies to I got a quot= a object change every time a new entity aplies this quota. Is this desir= able or useful? This all comes down to how fine-grained we need allow quota-scopes to be= . The simple option is something like: I have a 5GB quota that applies t= o the Email and CalendarEvent data types, and I am using 3GB of this. If= you want different quotas to apply to different Email objects in the ac= count depending on which mailbox(es) they are in it gets more complicate= d (especially with the multi-mailbox situation). I'd rather avoid it if = we don't need it, but if we do we should first define exactly what seman= tics we need and then work out the best representation. Neil. --51f094d9512b4f97abed70a6175f25d6 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
On Tue, 29 Oct = 2019, at 18:42, Beno=C3=AEt TELLIER wrote:

For instance imagine that I define that user= s of my email server will not store more than 2 GB of data

Bobs stores 1 GB of mail in his mailboxes thus have a 50% size quota. The upper bound is the generic limit user on this mailserver has. (limitSope= is "global" , usedScope "personal")

<= br>
That doesn't sound like a global scope to me: it's a perso= nal scope. It would be a global scope if there was 2 GB quota shared bet= ween different accounts and the usage in any counted towards it (like a = Family iCloud account for example). But then you need to show the global= usage too, otherwise it's not very useful!

 - The client supporting the extension will be able to correctly contextualize both quota, and display correct explanation in a UI


I'm not quite sure what you imagine such a = UI would look like. I'm struggling to think of anything that would be un= derstandable by >10% users. Can you point to an example?

From a clien= t perspective, I can back reference the quotaIds after a mailboxes/get c= all, which is easy to implement.

While if I have a quota that lists entities it applies to I got a quota object change every time a new entity aplies this quota. Is this desirable or useful?


Th= is all comes down to how fine-grained we need allow quota-scopes to be. = The simple option is something like: I have a 5GB quota that applies to = the Email and CalendarEvent data types, and I am using 3GB of this. If y= ou want different quotas to apply to different Email objects in the acco= unt depending on which mailbox(es) they are in it gets more complicated = (especially with the multi-mailbox situation). I'd rather avoid it if we= don't need it, but if we do we should first define exactly what semanti= cs we need and then work out the best representation.

=
Neil.
--51f094d9512b4f97abed70a6175f25d6--