From nobody Thu Apr 4 03:01:56 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 E72FD12003F for ; Thu, 4 Apr 2019 03:01:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 KICJcNlHri4U for ; Thu, 4 Apr 2019 03:01:52 -0700 (PDT) Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC52120005 for ; Thu, 4 Apr 2019 03:01:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1554372111; d=isode.com; s=june2016; i=@isode.com; bh=wq4hi2XZtNKJShmyEvvG/qZzwllitqJSWyk5T7xCPCU=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=BmVxXV5kWWeLyzpIMGcWovQGYbcOSfa1oR2i+rAcY0QDMKnb5qEMI0UhSm40mzEH5vbOIr Ve9+nSaztXGMx6YXG0qkmYcPI3UVV8CUda3qsQLXa+ZFlC3ow+44KW+enuRif+uGeIj5/n Bj9dEfHZG8crdDAmhOdBPempZH6493c=; Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id ; Thu, 4 Apr 2019 11:01:51 +0100 To: "jmap@ietf.org" Cc: Jim Fenton , Bron Gondwana From: Alexey Melnikov Message-ID: <5dea4b29-c62d-3a47-ca83-902b9ac03ce2@isode.com> Date: Thu, 4 Apr 2019 11:01:30 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB Archived-At: Subject: [Jmap] New co-chair for JMAP WG 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, 04 Apr 2019 10:01:54 -0000 Hi all, After discussing candidates with Barry and Bron and I am pleased to announce that Jim Fenton agreed to co-chair JMAP WG. Please welcome him! Best Regards, Alexey From nobody Thu Apr 4 03:09: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 8601612003F for ; Thu, 4 Apr 2019 03:09: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=J7X/N3l7; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=S39GbEvU 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 v8KrhFXFff02 for ; Thu, 4 Apr 2019 03:09:20 -0700 (PDT) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FF05120005 for ; Thu, 4 Apr 2019 03:09:20 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id B039E6237 for ; Thu, 4 Apr 2019 06:09:19 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Thu, 04 Apr 2019 06:09: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=fm2; bh=KW7f48p 3RjJbSRACnSYz1s84gHUxkMKjmyX3vSyu3rc=; b=J7X/N3l7SQlPzBqTx4Uumie CP8HxqCuN2T+/ugkRwQFT2TTaf79gIKDm0h5/d8hTwyL3ZKEqBkOkzDcacx3git7 bpFrmLAs6v67zLFmknssDDbONlq2P4AC0Yxanshjj3mtLuSbId1E2gMpihQ+EcNC mO+99k8KO6I+Q/7d6Ui3DbFAThEEKNJiGPVML8R+NybAap4f5VL7Jy+LA5mIsB/3 a2nf5f5TFMJZc/L70BjabF9EeMssvqgt0ZZJsu3GBkWo6+LK4u8oW8iXuPXAaygv C65UTcDr0KZV6QpPyrkmy0SBnVTeccv2aH17rnwF7pQxBSbQHI7oAEqkXhmgKNg= = 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=fm2; bh=KW7f48 p3RjJbSRACnSYz1s84gHUxkMKjmyX3vSyu3rc=; b=S39GbEvUXji002v0+J+FXL 8Akpgm7b5kQ7taIcZKehtC1r2wn8afLr4TNt9JaFFXLUAk/4PvlRrzmPVLR7T1tt pTW5dSGMBgXXiebcbZBFRnO1gtx1721e/Hruni9kY3mEGzejz1T4ePSRSAqFMsSe 46VOsetw+IlpdpYGt48PzuosEcUsvSetTdjhgFwZRH7YdMdWz6wCSQ6X4pHe2jef KxkX7IhGd4lc5kvSXY/AAQjpc2Ug7qyhsqbDvEu9lXEvz9TMlNM/w5UdVdELy94k ryNyKdcgBuCkeZvmrk+houSNZxaK3xj3WSocT7A8IxjgyJrb2WLf6/1GHm6P1tJw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrtdehgddvgeculddtuddrgedutddrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfgg fkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigr nhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomheqnecuffhomhgrih hnpehivghtfhdrohhrghenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgr shhtmhgrihhlthgvrghmrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id DB68E204D8; Thu, 4 Apr 2019 06:09:18 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-329-gf4aae99-fmstable-20190329v1 Mime-Version: 1.0 X-Me-Personality: 56629417 Message-Id: In-Reply-To: <5dea4b29-c62d-3a47-ca83-902b9ac03ce2@isode.com> References: <5dea4b29-c62d-3a47-ca83-902b9ac03ce2@isode.com> Date: Thu, 04 Apr 2019 06:09:18 -0400 From: "Bron Gondwana" To: jmap@ietf.org Content-Type: multipart/alternative; boundary=b3451839ca1444c89fc5d752ad34ffbb Archived-At: Subject: Re: [Jmap] New co-chair for JMAP WG 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, 04 Apr 2019 10:09:22 -0000 --b3451839ca1444c89fc5d752ad34ffbb Content-Type: text/plain Congrats Jim, welcome to the working group. Cheers, Bron. On Thu, Apr 4, 2019, at 21:02, Alexey Melnikov wrote: > Hi all, > > After discussing candidates with Barry and Bron and I am pleased to > announce that Jim Fenton agreed to co-chair JMAP WG. Please welcome him! > > Best Regards, > > Alexey > > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap > -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --b3451839ca1444c89fc5d752ad34ffbb Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Congrats Jim, welcome to the working group.

Cheers,

Bron.

On = Thu, Apr 4, 2019, at 21:02, Alexey Melnikov wrote:
H= i all,

After discussing candidates with Barry and Bron and= I am pleased to 
announ= ce that Jim Fenton agreed to co-chair JMAP WG. Please welcome him!

Best Regards,

<= /div>
Alexey

___________= ____________________________________
Jmap mailing list
Jma= p@ietf.org
https://www.ietf.o= rg/mailman/listinfo/jmap

=

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


--b3451839ca1444c89fc5d752ad34ffbb-- From nobody Thu Apr 4 04:23:21 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 BB39B1200B1 for ; Thu, 4 Apr 2019 04:23:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001, URIBL_BLOCKED=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 1Kp-rom80bBO for ; Thu, 4 Apr 2019 04:23:17 -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 6B865120092 for ; Thu, 4 Apr 2019 04:23:17 -0700 (PDT) Received: from [IPv6:2601:647:4300:2290:62a4:4cff:fe65:83dd] ([IPv6:2601:647:4300:2290:62a4:4cff:fe65:83dd]) (authenticated bits=0) by v2.bluepopcorn.net (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x34BN8RR010742 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 4 Apr 2019 04:23:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1554376996; bh=736cFzV3jUsVIkwbheB2aSFLHrqMJ9APnfVf3X5rhVE=; h=Subject:To:References:From:Date:In-Reply-To; b=orrspMmjTj3o/IHCLzP0RVYvA68yccboUbpOPOI5kF+KuHM2ZDWUyg6qLjInousmo aC8SkvpJT3WQZrr2yiT6OEgpj4IQ7fCU1aC8fZaLFpf656rNxLPTcU6MLGyGB0hrJk RJs/305uVvz6vMcLEtuM3feTOk1VPDMBMyuYuShU= To: jmap@ietf.org References: <5dea4b29-c62d-3a47-ca83-902b9ac03ce2@isode.com> From: Jim Fenton Message-ID: Date: Thu, 4 Apr 2019 04:23:02 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------F8B7EA25B1E8A871E81E524A" Content-Language: en-US Archived-At: Subject: Re: [Jmap] New co-chair for JMAP WG 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, 04 Apr 2019 11:23:20 -0000 This is a multi-part message in MIME format. --------------F8B7EA25B1E8A871E81E524A Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Thanks, Bron! Looking forward to working with you on this. -Jim On 4/4/19 3:09 AM, Bron Gondwana wrote: > Congrats Jim, welcome to the working group. > > Cheers, > > Bron. > > On Thu, Apr 4, 2019, at 21:02, Alexey Melnikov wrote: >> Hi all, >> >> After discussing candidates with Barry and Bron and I am pleased to >> announce that Jim Fenton agreed to co-chair JMAP WG. Please welcome him! >> >> Best Regards, >> >> Alexey >> >> _______________________________________________ >> Jmap mailing list >> Jmap@ietf.org >> https://www.ietf.org/mailman/listinfo/jmap >> > > -- >   Bron Gondwana, CEO, FastMail Pty Ltd >   brong@fastmailteam.com > > > > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap --------------F8B7EA25B1E8A871E81E524A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
Thanks, Bron! Looking forward to working with you on this.

-Jim

On 4/4/19 3:09 AM, Bron Gondwana wrote:
Congrats Jim, welcome to the working group.

Cheers,

Bron.

On Thu, Apr 4, 2019, at 21:02, Alexey Melnikov wrote:
Hi all,

After discussing candidates with Barry and Bron and I am pleased to 
announce that Jim Fenton agreed to co-chair JMAP WG. Please welcome him!

Best Regards,

Alexey

_______________________________________________
Jmap mailing list


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



_______________________________________________
Jmap mailing list
Jmap@ietf.org
https://www.ietf.org/mailman/listinfo/jmap


--------------F8B7EA25B1E8A871E81E524A-- From nobody Thu Apr 11 00:34:49 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 94698120003; Thu, 11 Apr 2019 00:34:42 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Magnus Westerlund via Datatracker To: "The IESG" Cc: jmap-chairs@ietf.org, jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Magnus Westerlund Message-ID: <155496808253.12726.13042503059452301232.idtracker@ietfa.amsl.com> Date: Thu, 11 Apr 2019 00:34:42 -0700 Archived-At: Subject: [Jmap] Magnus Westerlund's No Objection on charter-ietf-jmap-01-00: (with COMMENT) 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: Thu, 11 Apr 2019 07:34:43 -0000 Magnus Westerlund has entered the following ballot position for charter-ietf-jmap-01-00: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-jmap/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- If the goal is to not diverge from existing formats, is it possible to clarify the relation between object models and data formats. For example are there really a need to define new data formats, as I assume there exists already for the established format? Should there be clearer scoping of why one may consider new data formats for existing object models? From nobody Thu Apr 11 07:35:33 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 7FB8812025E; Thu, 11 Apr 2019 07:35:25 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Benjamin Kaduk via Datatracker To: "The IESG" Cc: jmap-chairs@ietf.org, jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Benjamin Kaduk Message-ID: <155499332551.26219.2615821249971397663.idtracker@ietfa.amsl.com> Date: Thu, 11 Apr 2019 07:35:25 -0700 Archived-At: Subject: [Jmap] Benjamin Kaduk's No Objection on charter-ietf-jmap-01-00: (with COMMENT) 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: Thu, 11 Apr 2019 14:35:26 -0000 Benjamin Kaduk has entered the following ballot position for charter-ietf-jmap-01-00: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-jmap/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- If we're going to be talking about new transports (e.g., websockets, or the more generic "different protocols than HTTPS"), we should say something about ensuring that the appropriate security properties are retained in the new setup(s). From nobody Fri Apr 12 10:15:55 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 81E81120304; Fri, 12 Apr 2019 10:15:47 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Cc: jmap@ietf.org Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Message-ID: <155508934745.16732.1496538328521501441.idtracker@ietfa.amsl.com> Date: Fri, 12 Apr 2019 10:15:47 -0700 Archived-At: Subject: [Jmap] WG Review: JSON Mail Access Protocol (jmap) 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, 12 Apr 2019 17:15:48 -0000 The JSON Mail Access Protocol (jmap) WG in the Applications and Real-Time Area of the IETF is undergoing rechartering. The IESG has not made any determination yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by 2019-04-22. JSON Mail Access Protocol (jmap) ----------------------------------------------------------------------- Current status: Active WG Chairs: Bron Gondwana Jim Fenton Assigned Area Director: Alexey Melnikov Applications and Real-Time Area Directors: Adam Roach Alexey Melnikov Barry Leiba Mailing list: Address: jmap@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/jmap Archive: https://mailarchive.ietf.org/arch/search/?email_list=jmap Group page: https://datatracker.ietf.org/group/jmap/ Charter: https://datatracker.ietf.org/doc/charter-ietf-jmap/ The JMAP protocol defined in draft-ietf-jmap-core is designed to be extensible to multiple datatypes which are useful for personal information management related to email stores. Now that draft-ietf-jmap-mail is completed, the working group will produce specifications for related data types, begining with calendars. The calendar work will be based on draft-ietf-calext-jscalandar as the data format. This working group will consult with the CALEXT working group to ensure that calendar access via JMAP remains compatible with existing calendar standards. 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 different protocols than HTTPS. Work on JMAP extensions will be bound by the following constraints: 1) The work of this group is limited to developing protocols for a client synchronising data with a server. Any server-to-server issues are out of scope for this working group. 2) Object models will use existing IETF work where possible. 3) JMAP Extensions will be built following the core principles: 3.1) The server will not be required to perform work not explicitly requested by the client, and the default should always be the mode which requires the least server work. 3.2) The client can discover limits enforced by the server on resources or request complexity. 3.3) Where side effects generated by the server are optional, the protocol will default to no side effects, and the client must explicitly request that those side effects happen (for example: sending a calendar invitation or reply when updating an event) The working group will deliver documents for the following: - JMAP access to calendars using the JSCalendar format - accessing JMAP over Websockets - handling of S/MIME email messages (e.g. signature verification) over JMAP - Message Disposition Notifications (RFC 8098) via JMAP - other extensions which the working group considers related to email and compatible with the constraints listed above Milestones: Done - Update charter to reflect current and planned work Apr 2019 - Adopt a document for calendar access via JMAP Apr 2019 - Adopt a document for S/MIME interaction via JMAP Sep 2019 - Submit JMAP over websockets document to the IESG Sep 2019 - Submit Message Disposition Notification document to the IESG Dec 2019 - Submit document with guidance for implementation of IMAP servers and proxies (Informational) From nobody Mon Apr 15 22:38:23 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 A0083120118; Mon, 15 Apr 2019 22:38:14 -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=WQdRcCll; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CbAze9bq 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 eIRBwtTeqgFS; Mon, 15 Apr 2019 22:38:12 -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 59EF412025B; Mon, 15 Apr 2019 22:38:12 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 30D0A239D9; Tue, 16 Apr 2019 01:38:11 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Tue, 16 Apr 2019 01:38:11 -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=fm2; bh=BYvR9OcZc8Xte2fhkPnjs+HE6nO3yqtVpSCyWiu KoIc=; b=WQdRcCllL+Nvg90ZIswy97C36yNFzDeK1OJexWs37yeKc6xhyoXImf6 CMkFkQls3DNSWGWEG4OH0O9UM3hMex8M4ElyqrCWClJA1J8b6fmndCVSEmUXv89g dbMqKuiz8Ese1C0rg36Sr/wwUrWxaebF5sr48Tx+8wNyeToEmVTmqcP1XchOmOuv EWriDBW36ojk+iCsBTmQdT8cSW8tAFWdQdOY5kEIBOl+uE/gOkAASLb39TXTZoUA vnmp5PCxMm5fmxfcaHxv59WijhaexkHKaGhH4WsCvUzn4mEmlSLCsOMDLx16zf+r si2np83aSVAfk9XD9jba7EuruXuMDnA== 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=fm2; bh=BYvR9OcZc8Xte2fhkPnjs+HE6nO3y qtVpSCyWiuKoIc=; b=CbAze9bqsp8lNvnbTl728ykGcd+XQFQrt995NWXlU0W0o MlY86Wq14JwYGtzWer12rBu5jSNxQ1vEXghLf6yQIlXoe3Tullv3Cn01+7e6ePRs JG8XHdM+gRsxDA90w1AVad5Oc2fQaK7go9Z6iEzOF8hWD4Vdg82ESr/PnenjF5dW RdSuiiZnoMXF8SHmQ6MCb7TlAAveFKpCkNx3jJTTmpRmxX7Qr6T8KM7WGmdyq+4w IZUh4hAt7AKEja9CpMCMMsrzv6pVjNWMYmmJtWSsL42JVWUHRxOyWSK82VTdBqz4 rePUz/5AaO4HLg9A51z3BRG5+rx1go++wkzQbza4Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrfedtgdeljecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesrgdtreerre ertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghs thhmrghilhhtvggrmhdrtghomheqnecuffhomhgrihhnpehivghtfhdrohhrghenucfrrg hrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm necuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 7326F2069B; Tue, 16 Apr 2019 01:38:10 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-442-g0747b46-fmstable-20190416v2 Mime-Version: 1.0 X-Me-Personality: 56629417 Message-Id: <0d26c814-19a9-4634-991d-911aa8be009e@www.fastmail.com> Date: Tue, 16 Apr 2019 01:38:09 -0400 From: "Bron Gondwana" To: calsify@ietf.org, jmap@ietf.org, caldeveloper-l@lists.calconnect.org Content-Type: multipart/alternative; boundary=7de10601843b4e34831af6e3fefc985c Archived-At: Subject: [Jmap] Looking for a co-author for JMAP Calendars 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, 16 Apr 2019 05:38:15 -0000 --7de10601843b4e34831af6e3fefc985c Content-Type: text/plain Hi All, The JMAP working group at IETF is looking for a co-author to work on a JMAP spec for calendar access. This can be anybody with some calendar experience who's willing to help! An initial draft is here: https://datatracker.ietf.org/doc/draft-jenkins-jmapcalendars/ There is still considerable work to do, particularly around how scheduling will interact, and whether events can be present in multiple calendars simultaneously in the same way that Email objects can be in multiple Mailboxes over in jmap-mail. Obviously we'd love to have somebody from outside FastMail who brings different background and experience to help with the document! Neil is happy to stay on as a co-editor as well. Cheers, Bron. -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --7de10601843b4e34831af6e3fefc985c Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Hi All,

The JMAP working group at IETF is l= ooking for a co-author to work on a JMAP spec for calendar access. = This can be anybody with some calendar experience who's willing to help= !

An initial draft is here:


The= re is still considerable work to do, particularly around how scheduling = will interact, and whether events can be present in multiple calendars s= imultaneously in the same way that Email objects can be in multiple Mail= boxes over in jmap-mail.

=
Obviously we'd love to have some= body from outside FastMail who brings different background and experienc= e to help with the document!  Neil is happy to stay on as a co-edit= or as well.

Cheers,

Bron.

--
  Bron Gondwana, C= EO, FastMail Pty Ltd
  brong@fast= mailteam.com


--7de10601843b4e34831af6e3fefc985c-- From nobody Tue Apr 23 23:46: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 24F1A1201EB for ; Tue, 23 Apr 2019 23:45:58 -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=KhSTm7Ks; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=6n8nVXL1 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 YId0PwsOYlTL for ; Tue, 23 Apr 2019 23:45:55 -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 B04AC1201D7 for ; Tue, 23 Apr 2019 23:45:54 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 44A3A21E92 for ; Wed, 24 Apr 2019 02:45:53 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Wed, 24 Apr 2019 02:45:53 -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=fm2; bh=69HGHwz SYFNsX2X4yEICgqB391pl+bTdHvjsVf2EQ64=; b=KhSTm7KsEs+9mO+9enNYiQD 9UXwIAGEKMzxKLr2kRjEt/dinJLoyijd226hl+sGNK/BodV83N0BDdUtZhy9Xylb ewMNos2FvmJwJ6ekkMgkRuHkC8zOwZu+jSwwyjjSb16pF4JM5Zs3ouU044/yCxIV 6do0wcmphuhaWSFLv5qPN+7eoygqbCXFE57M35BtVa5h8IM83KV3ETn/KFPdXLLX dCYOEWB3bknLR+Imuz6jxDKvOGY7c4aE5qYchclIG84NcuWEpUPZUlC2vLWjQZLR W6otii7b1afFwUqoGXKz4pt2OH8eIyTHhmVnBFJCXHrqvXRIBguQeaX5hG2lXtQ= = 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=fm2; bh=69HGHw zSYFNsX2X4yEICgqB391pl+bTdHvjsVf2EQ64=; b=6n8nVXL1aYiXtqzXfu80nD Xd2oiB3onAPQx1Nth2r000Qcrd/NYQmVl8ajRl4emyMyz35hmNkI9aKeZilUQcI6 Yu2IZO+vJ4ZAPEOxegNFCx+vSIBrFoTvrYohcZwrF1QDmdo66QnBZCZkrSq0vxZS vIC7vyF1zwheuM1Gs/CJEaSOYnICu5Tn84YgZ16wH/xkfFoZkzicDN+3VJGwaFp6 cWKKz3jCwORIgqx5Sbp+XNZjA0tS9TdNTh+tJNivndFLU5UbrHTUWdm2n7cnr9Hg R6wecpvqt0/WgsMxNbzz9nTlL4aseiwbjEzRcuSpdyyw4YZiWVeKLRVhTYEZ715w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrgeelgdduudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucffohhmrghinhepihgvthhfrdhorhhgne curfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdr tghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 90E30205F7; Wed, 24 Apr 2019 02:45:52 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-443-g918f9d3-fmstable-20190416v3 Mime-Version: 1.0 Message-Id: <01217b0c-5a66-4eb0-a351-1d82ad716047@beta.fastmail.com> In-Reply-To: References: Date: Wed, 24 Apr 2019 02:45:52 -0400 From: "Bron Gondwana" To: jmap@ietf.org Content-Type: multipart/alternative; boundary=0973c0ba71864a31b2b42f3785392a06 Archived-At: Subject: Re: [Jmap] Call for adoption of JMAP calendars - reply by April 15 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, 24 Apr 2019 06:45:58 -0000 --0973c0ba71864a31b2b42f3785392a06 Content-Type: text/plain Thanks Neil. There have been no objections, and Mike Douglass has volunteered to co-edit. If you could please upload a new draft-ietf-jmap-calendars-00 with him listed as a co-author I will adopt it formally. Cheers, Bron. On Wed, Mar 27, 2019, at 02:45, Neil Jenkins wrote: > I have posted an IETF-format draft of the initial spec: https://tools.ietf.org/html/draft-jenkins-jmapcalendars-01. > > Work still required includes: > * Deciding if the client should be able to ask the server to expand recurrences (probably yes), and what this looks like. > * Defining scheduling (when to send iMIP messages) in more detail, and probably making this an explicit API method rather than implicit reaction to event changes. > * Deciding whether to allow events to exist in multiple calendars at the same time (like labels vs folders in mail). > * Moving calendar permissions into a `myRights` property to match JMAP Mail. > Neil. > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap > -- Bron Gondwana, CEO, FastMail Pty Ltd brong@fastmailteam.com --0973c0ba71864a31b2b42f3785392a06 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Thanks Neil.  There have been no objections, and= Mike Douglass has volunteered to co-edit.  If you could please upl= oad a new draft-ietf-jmap-calendars-00 with him listed as a co-author I = will adopt it formally.

<= /div>
Cheers,

Bron.
<= br>
On Wed, Mar 27, 2019, at 02:4= 5, Neil Jenkins wrote:
I have posted an IETF-format draft of the initial spec: https://too= ls.ietf.org/html/draft-jenkins-jmapcalendars-01.

<= /div>
Work still required includes:
  • Deciding if the= client should be able to ask the server to expand recurrences (probably= yes), and what this looks like.
  • Defining scheduling (when t= o send iMIP messages) in more detail, and probably making this an explic= it API method rather than implicit reaction to event changes.
    • Deciding whether to allow events to exist in multiple calendars at the= same time (like labels vs folders in mail).
  • Moving calendar= permissions into a myRights property to match = JMAP Mail.
Neil.
_______________________= ________________________
Jmap mailing list
J= map@ietf.org
https://www.ietf.org/mailman/listinfo/jmap

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

--0973c0ba71864a31b2b42f3785392a06-- From nobody Mon Apr 29 06:03:19 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 CB4FD1202D9; Mon, 29 Apr 2019 06:03:17 -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.95.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jmap@ietf.org Message-ID: <155654299775.18610.9326446969406061887@ietfa.amsl.com> Date: Mon, 29 Apr 2019 06:03:17 -0700 Archived-At: Subject: [Jmap] I-D Action: draft-ietf-jmap-calendars-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, 29 Apr 2019 13:03:18 -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-00.txt Pages : 10 Date : 2019-04-29 Abstract: This document specifies a data model for synchronising 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-00 https://datatracker.ietf.org/doc/html/draft-ietf-jmap-calendars-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 Tue Apr 30 14:03:53 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 40FBD120071; Tue, 30 Apr 2019 14:03:44 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= To: "The IESG" Cc: jmap-chairs@ietf.org, jmap@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.95.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= Message-ID: <155665822421.7639.14487978641309584863.idtracker@ietfa.amsl.com> Date: Tue, 30 Apr 2019 14:03:44 -0700 Archived-At: Subject: [Jmap] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_charter-ie?= =?utf-8?q?tf-jmap-01-00=3A_=28with_COMMENT=29?= 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, 30 Apr 2019 21:03:45 -0000 Éric Vyncke has entered the following ballot position for charter-ietf-jmap-01-00: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-jmap/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Having some milestones and roadmap would be a plus.