From nobody Wed May 1 17:08:37 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 A34741200EA; Wed, 1 May 2019 17:08:35 -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.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Benjamin Kaduk Message-ID: <155675571560.2931.9840518132194126377.idtracker@ietfa.amsl.com> Date: Wed, 01 May 2019 17:08:35 -0700 Archived-At: Subject: [Jmap] Benjamin Kaduk's Block on charter-ietf-jmap-01-00: (with BLOCK) 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, 02 May 2019 00:08:36 -0000 Benjamin Kaduk has entered the following ballot position for charter-ietf-jmap-01-00: Block 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/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- 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 Thu May 2 03:27:30 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 7E884120333; Thu, 2 May 2019 03:27:24 -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, FREEMAIL_FROM=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=fastmail.fm header.b=nU7R7POS; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=UnReBI5g 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 GGHrsdgLMxmx; Thu, 2 May 2019 03:27:23 -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 132EA12031D; Thu, 2 May 2019 03:27:23 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 35A3C25645; Thu, 2 May 2019 06:27:22 -0400 (EDT) Received: from imap1 ([10.202.2.51]) by compute7.internal (MEProxy); Thu, 02 May 2019 06:27:22 -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=fm3; bh=jiJeDoI7x7qn/aFzY8mEK/na9Omiuty +YknunfJNPxk=; b=nU7R7POSVJXHNt4Inyp7UDEsa6ybsyDJutgbP2D5aojT4Dc SxQy3aaQLozJ5s+KcFgvhx9gsmfvKoQKxvzg0yW1dEO01M0fvdvqvDF5EON9DbpS khEGMEX1dkbmbm1giDUB/Dd62LBoSW/Rw/cUbbjsWyKxQdypRSEKLwnUZaAU4rHz IXT4zZwIdPwv1/Hjy6cTzDNOFwm352Y7QsusoJgdjUyepPs9hx5eMrOYzujYCMc+ GhRQIPSr+xoxEXRC13dzyAeoXTdYCOYBphzwrtl71keDjPLOSf+M4Thc5BjJvqXm 6ZlKeuq4btWIKLQWaDFPWwgPbLwwY3DJFcHz5vA== 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=fm2; bh=jiJeDo I7x7qn/aFzY8mEK/na9Omiuty+YknunfJNPxk=; b=UnReBI5g+cxOTdq4EgUsDT zqlvYlmqsJvSHoP/yUwImTk3G5bjr2a1lnk3MP+KvCObnXWqg7DjR8J0gsFYmAxe mziOuehoCHOeXSejtvAwvhAs74O8DkhmGr50ng4Ql+ToOIKqEHAHP/Lfb24iKPKl xkRJUpYmv6FlXq7B19xxaZDy3w7BosjVLBjwvyYK7VEPKAJCl5eOHwXkVqAUpnvw MstDImBREwXdlRVHBhNzxtMn1wGwZhL4KrkuqWfXgBBLbQiLg0VNdh2zjZg9jfDj YJoFJQ12pXgdUUFItDz0K7B+kAlpKQ6vhJKbaHaQgNID9l074SJBjm+GCiCWCsHg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrieelgdeftdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedftehlvgig vgihucfovghlnhhikhhovhdfuceorggrmhgvlhhnihhkohhvsehfrghsthhmrghilhdrfh hmqeenucffohhmrghinhephhhtthhpshdrihhnnecurfgrrhgrmhepmhgrihhlfhhrohhm pegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmhenucevlhhushhtvghrufhiii gvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 746BFD4931; Thu, 2 May 2019 06:27:21 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-449-gfb3fc5a-fmstable-20190430v1 Mime-Version: 1.0 Message-Id: <20ebf56f-4d8b-4840-b854-58d7eedc1390@www.fastmail.com> In-Reply-To: <155675571560.2931.9840518132194126377.idtracker@ietfa.amsl.com> References: <155675571560.2931.9840518132194126377.idtracker@ietfa.amsl.com> Date: Thu, 02 May 2019 06:26:57 -0400 From: "Alexey Melnikov" To: "Benjamin Kaduk" , "The IESG" Cc: jmap@ietf.org, jmap-chairs@ietf.org Content-Type: text/plain Archived-At: Subject: Re: [Jmap] Benjamin Kaduk's Block on charter-ietf-jmap-01-00: (with BLOCK) 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, 02 May 2019 10:27:24 -0000 Hi Benjamin, On Thu, May 2, 2019, at 1:08 AM, Benjamin Kaduk via Datatracker wrote: > ---------------------------------------------------------------------- > BLOCK: > ---------------------------------------------------------------------- > > 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). I've added the following to the Charter: 4) New transports for transporting JMAP will have security properties comparable to HTTPS. In particular they have to require TLS. The only proposal on the table is based on WSS, so this is no brainer. Best Regards, Alexey From nobody Thu May 2 06:43:26 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 2F89C120135; Thu, 2 May 2019 06:43:24 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?Mirja_K=C3=BChlewind_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?Mirja_K=C3=BChlewind?= Message-ID: <155680460418.24967.7747659650977041535.idtracker@ietfa.amsl.com> Date: Thu, 02 May 2019 06:43:24 -0700 Archived-At: Subject: [Jmap] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Block_on_charter-ietf-?= =?utf-8?q?jmap-01-01=3A_=28with_BLOCK=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: Thu, 02 May 2019 13:43:24 -0000 Mirja Kühlewind has entered the following ballot position for charter-ietf-jmap-01-01: Block 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/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- I actually have a question about this how new transport part: "New transports for transporting JMAP will have security properties comparable to HTTPS. In particular they have to require TLS." Is the intention actually to have a "transport other https" or rather something on top of https? I really would like to see further explanation here what this is heading to! From nobody Thu May 2 06:53:29 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 89BFA120103; Thu, 2 May 2019 06:53:20 -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, FREEMAIL_FROM=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=mrzFXT83; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=e9pedSXf 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 qXE9fRoTckIF; Thu, 2 May 2019 06:53:18 -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 769EE120372; Thu, 2 May 2019 06:53:18 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 7AF0C25C0D; Thu, 2 May 2019 09:53:17 -0400 (EDT) Received: from imap1 ([10.202.2.51]) by compute7.internal (MEProxy); Thu, 02 May 2019 09:53:17 -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:content-transfer-encoding; s=fm3; bh=EE2oQ YDZVI8YrFWnUrJ2n5RA72I7eAsgAxjYU82j0v4=; b=mrzFXT83WcZ0EiCZbmFMi /4pp8P/uSlpejLcy0H2RCda6n6Wa3UTToTHlcRdHtbSIGOn8Dc1z88IdH22JDETr rRrZnwC78I///graPv5hXuAkxlgH/37B+1VSXKyVR86+55PfO04qPMhq5igL/N8K LurA5n0dlNl2b0tyDIvDDV1XZMya4IbthXsSdakHMyOqsyDJ8Bx3v4XDKslAeFmJ X3hbx/a9kYAQQ9hVPMVQoWjS4yiQKwM+CRyMXCS6QyzpDBbq+0YGWYpuP0yT4x2R QA6Sx5odbRqRdfDbo+lPPxlU5xFvWFnFcS0nFarBy5U63ffQenlLPdOG/3atX6Zi w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=EE2oQYDZVI8YrFWnUrJ2n5RA72I7eAsgAxjYU82j0 v4=; b=e9pedSXfYMljLfIAq8tvh7sSbSOE7/Digqan2rDewdLJ1i1Y6Oop5l145 ioZGGD1HeCcbVgjm49hZJpbMaYvY1+6YuX6v9myVTYaGHknowhLtbWEvtue+LYcO Oaqw2RLwo2YalyTXfLDScUlw9sVYhYx0NF1XGrk893VhKdjdqZYgF1g4O7K5Xfvr WaoI5DoP6+yS5MDSvI41XUD5BCa1mELURCEgmoBMUKibodNHqhChvLM+Xf1bpdZS 2Sg9SRTZIHOHxkpvohAo6YPzb1hRQZityuTltmZiRjPK7sQBDW8QbYLPjjrfyl0f UiQLuOoETI8qBT9nv6Pr4/svC0SgA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrieelgdejvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdetlhgv gigvhicuofgvlhhnihhkohhvfdcuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrd hfmheqnecuffhomhgrihhnpehivghtfhdrohhrghdphhhtthhpshdrihhnnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmhenuc evlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id C2E26D4931; Thu, 2 May 2019 09:53:16 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-449-gfb3fc5a-fmstable-20190430v1 Mime-Version: 1.0 Message-Id: <63b454af-e96c-441a-a0fd-e12649a5deab@www.fastmail.com> In-Reply-To: <155680460418.24967.7747659650977041535.idtracker@ietfa.amsl.com> References: <155680460418.24967.7747659650977041535.idtracker@ietfa.amsl.com> Date: Thu, 02 May 2019 09:52:53 -0400 From: "Alexey Melnikov" To: "Mirja Kuehlewind" , "Benjamin Kaduk" Cc: "The IESG" , jmap@ietf.org, jmap-chairs@ietf.org Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Jmap] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Block_on_charter-ietf-?= =?utf-8?q?jmap-01-01=3A_=28with_BLOCK=29?= 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, 02 May 2019 13:53:21 -0000 On Thu, May 2, 2019, at 2:43 PM, Mirja K=C3=BChlewind via Datatracker wr= ote: > Mirja K=C3=BChlewind has entered the following ballot position for > charter-ietf-jmap-01-01: Block >=20 > 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 thi= s > introductory paragraph, however.) >=20 >=20 >=20 > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/charter-ietf-jmap/ >=20 > ----------------------------------------------------------------------= > BLOCK: > ----------------------------------------------------------------------= >=20 > I actually have a question about this how new transport part: > "New transports for transporting JMAP will have security properties > comparable to HTTPS. In particular they have to require TLS." > Is the intention actually to have a "transport other https" or rather = something > on top of https? I really would like to see further explanation here w= hat this > is heading to! Honestly, we only care about WSS (Websocket over TLS) transport. So mayb= e the charter should just say that? From nobody Thu May 2 07:39:34 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 E96BC12013E; Thu, 2 May 2019 07:39:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 u7VnOkUWIhc2; Thu, 2 May 2019 07:39:29 -0700 (PDT) Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA251120103; Thu, 2 May 2019 07:39:28 -0700 (PDT) Received: from 200116b82c28d900586a8455fab5fdc1.dip.versatel-1u1.de ([2001:16b8:2c28:d900:586a:8455:fab5:fdc1]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1hMCrt-0004j5-CR; Thu, 02 May 2019 16:39:25 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) From: Mirja Kuehlewind In-Reply-To: <63b454af-e96c-441a-a0fd-e12649a5deab@www.fastmail.com> Date: Thu, 2 May 2019 16:39:24 +0200 Cc: Benjamin Kaduk , jmap@ietf.org, The IESG , jmap-chairs@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <4DF6CE27-7FF1-4F32-8CD6-3882C730FD93@kuehlewind.net> References: <155680460418.24967.7747659650977041535.idtracker@ietfa.amsl.com> <63b454af-e96c-441a-a0fd-e12649a5deab@www.fastmail.com> To: Alexey Melnikov X-Mailer: Apple Mail (2.3445.104.8) X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1556807968;292fd1b9; X-HE-SMSGID: 1hMCrt-0004j5-CR Archived-At: Subject: Re: [Jmap] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Block_on_charter-ietf-?= =?utf-8?q?jmap-01-01=3A_=28with_BLOCK=29?= 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, 02 May 2019 14:39:32 -0000 > On 2. May 2019, at 15:52, Alexey Melnikov = wrote: >=20 > On Thu, May 2, 2019, at 2:43 PM, Mirja K=C3=BChlewind via Datatracker = wrote: >> Mirja K=C3=BChlewind has entered the following ballot position for >> charter-ietf-jmap-01-01: Block >>=20 >> 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.) >>=20 >>=20 >>=20 >> The document, along with other ballot positions, can be found here: >> https://datatracker.ietf.org/doc/charter-ietf-jmap/ >>=20 >> = ---------------------------------------------------------------------- >> BLOCK: >> = ---------------------------------------------------------------------- >>=20 >> I actually have a question about this how new transport part: >> "New transports for transporting JMAP will have security properties >> comparable to HTTPS. In particular they have to require TLS." >> Is the intention actually to have a "transport other https" or rather = something >> on top of https? I really would like to see further explanation here = what this >> is heading to! >=20 > Honestly, we only care about WSS (Websocket over TLS) transport. So = maybe the charter should just say that? >=20 Yes, please! From nobody Thu May 2 07:53:38 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 5E31412013E; Thu, 2 May 2019 07:53:36 -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, FREEMAIL_FROM=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=apTINCAI; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=zYdqVi9Q 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 pSdg3AsFWE9q; Thu, 2 May 2019 07:53:34 -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 3AF4212016B; Thu, 2 May 2019 07:53:33 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 69AC0255D6; Thu, 2 May 2019 10:53:32 -0400 (EDT) Received: from imap1 ([10.202.2.51]) by compute7.internal (MEProxy); Thu, 02 May 2019 10:53:32 -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:content-transfer-encoding; s=fm3; bh=spsUa jBIc8KFco8RRtCMkpXihM9cHvytTWQDWMuJdkg=; b=apTINCAIKxKsMiJvHSGIz F4+LsJZf60ObDCAGC9XMctRzw7qDZqQQBOvQTvOE0IiyZjB7Ggf0fzZYeceBRKzu wxzw5Ej74mZW0PpvMGjG7BUXswKFQGdKoDFt3ZUftHs+frZVPwzYx4g8a/lJ6nFp KLMu7EhFyyVwomIa+y65BvT2Pl1JoPuODFUUUITf34SZk/3Ga2FGrBPDgI3Ghmt4 NxUHKjNWaBAJdE6pz4UsJkO+F5Te1I/ur/NEAzYi0ZqFYvTTxSnhdcXv/EoYdJ0e eqOw31/+YUsEnbuLkzo1k9LJx//uhmE/x0iPOJamj1Z7++4ZhKvtPf8KdLeLs4n+ Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=spsUajBIc8KFco8RRtCMkpXihM9cHvytTWQDWMuJd kg=; b=zYdqVi9QERD929dE7dbgF6sFiv6lIkC6GluwvdMa6271ny+4vJnjEFc0I qt5KfXYBXgQO8UqrTEiNloysDgulYdhdYV1tL2npId5LQtq8TysUdX3Mu0L2whKB ozBTxM41FnPJXKNijaz/WDy37gmjNhWcAu6Au/8pedHYEsZZ0Dg4aQ3bZiocA2eK HqmEb1ZVIAxBbGxnLtqZd0UpL7CnrGf3OZOypCD5cQqgXSOHc2F5toZhA5q+MY3j DOSXSvKUm0iQEot73+UX08JBu4qsdU75G53zoogRI+5JBIVoaNMQUH08E/UkSR3H hM3BmY3o6GZcGjjnYi9YlYSEIpCtw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrieelgdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdetlhgv gigvhicuofgvlhhnihhkohhvfdcuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrd hfmheqnecuffhomhgrihhnpehivghtfhdrohhrghdphhhtthhpshdrihhnnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmhenuc evlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id C6A3AD4931; Thu, 2 May 2019 10:53:31 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-449-gfb3fc5a-fmstable-20190430v1 Mime-Version: 1.0 Message-Id: In-Reply-To: <4DF6CE27-7FF1-4F32-8CD6-3882C730FD93@kuehlewind.net> References: <155680460418.24967.7747659650977041535.idtracker@ietfa.amsl.com> <63b454af-e96c-441a-a0fd-e12649a5deab@www.fastmail.com> <4DF6CE27-7FF1-4F32-8CD6-3882C730FD93@kuehlewind.net> Date: Thu, 02 May 2019 10:53:08 -0400 From: "Alexey Melnikov" To: "Mirja Kuehlewind" Cc: "Benjamin Kaduk" , jmap@ietf.org, "The IESG" , jmap-chairs@ietf.org Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Jmap] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Block_on_charter-ietf-?= =?utf-8?q?jmap-01-01=3A_=28with_BLOCK=29?= 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, 02 May 2019 14:53:37 -0000 On Thu, May 2, 2019, at 3:39 PM, Mirja Kuehlewind wrote:=20 >=20 > > On 2. May 2019, at 15:52, Alexey Melnikov w= rote: > >=20 > > On Thu, May 2, 2019, at 2:43 PM, Mirja K=C3=BChlewind via Datatracke= r wrote: > >> Mirja K=C3=BChlewind has entered the following ballot position for > >> charter-ietf-jmap-01-01: Block > >>=20 > >> When responding, please keep the subject line intact and reply to a= ll > >> email addresses included in the To and CC lines. (Feel free to cut = this > >> introductory paragraph, however.) > >>=20 > >>=20 > >>=20 > >> The document, along with other ballot positions, can be found here:= > >> https://datatracker.ietf.org/doc/charter-ietf-jmap/ > >>=20 > >> -------------------------------------------------------------------= --- > >> BLOCK: > >> -------------------------------------------------------------------= --- > >>=20 > >> I actually have a question about this how new transport part: > >> "New transports for transporting JMAP will have security properties= > >> comparable to HTTPS. In particular they have to require TLS." > >> Is the intention actually to have a "transport other https" or rath= er something > >> on top of https? I really would like to see further explanation her= e what this > >> is heading to! > >=20 > > Honestly, we only care about WSS (Websocket over TLS) transport. So = maybe the charter should just say that? > >=20 > Yes, please! Check the latest text, I just updated the Charter to read: 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). and I removed 4). From nobody Thu May 2 08:07: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 30BB41203AB; Thu, 2 May 2019 08:07:47 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?Mirja_K=C3=BChlewind_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?Mirja_K=C3=BChlewind?= Message-ID: <155680966713.24689.9600774504466055832.idtracker@ietfa.amsl.com> Date: Thu, 02 May 2019 08:07:47 -0700 Archived-At: Subject: [Jmap] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_charte?= =?utf-8?q?r-ietf-jmap-01-02=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: Thu, 02 May 2019 15:07:47 -0000 Mirja Kühlewind has entered the following ballot position for charter-ietf-jmap-01-02: 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: ---------------------------------------------------------------------- Thanks for addressing my block! From nobody Thu May 2 08:08:30 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 A7DD912014A; Thu, 2 May 2019 08:08:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 ERcLngQgrVjZ; Thu, 2 May 2019 08:08:20 -0700 (PDT) Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81B4B1203C2; Thu, 2 May 2019 08:08:20 -0700 (PDT) Received: from 200116b82c28d900586a8455fab5fdc1.dip.versatel-1u1.de ([2001:16b8:2c28:d900:586a:8455:fab5:fdc1]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1hMDJq-0006KP-AT; Thu, 02 May 2019 17:08:18 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) From: Mirja Kuehlewind In-Reply-To: Date: Thu, 2 May 2019 17:08:17 +0200 Cc: jmap-chairs@ietf.org, jmap@ietf.org, Benjamin Kaduk , The IESG Content-Transfer-Encoding: quoted-printable Message-Id: <38D1C258-6141-4CA8-93D8-F1A752AB8795@kuehlewind.net> References: <155680460418.24967.7747659650977041535.idtracker@ietfa.amsl.com> <63b454af-e96c-441a-a0fd-e12649a5deab@www.fastmail.com> <4DF6CE27-7FF1-4F32-8CD6-3882C730FD93@kuehlewind.net> To: Alexey Melnikov X-Mailer: Apple Mail (2.3445.104.8) X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1556809700;70b3d2ac; X-HE-SMSGID: 1hMDJq-0006KP-AT Archived-At: Subject: Re: [Jmap] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Block_on_charter-ietf-?= =?utf-8?q?jmap-01-01=3A_=28with_BLOCK=29?= 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, 02 May 2019 15:08:23 -0000 Okay, released my block. Thanks! :-) > On 2. May 2019, at 16:53, Alexey Melnikov = wrote: >=20 > On Thu, May 2, 2019, at 3:39 PM, Mirja Kuehlewind wrote:=20 >>=20 >>> On 2. May 2019, at 15:52, Alexey Melnikov = wrote: >>>=20 >>> On Thu, May 2, 2019, at 2:43 PM, Mirja K=C3=BChlewind via = Datatracker wrote: >>>> Mirja K=C3=BChlewind has entered the following ballot position for >>>> charter-ietf-jmap-01-01: Block >>>>=20 >>>> 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.) >>>>=20 >>>>=20 >>>>=20 >>>> The document, along with other ballot positions, can be found here: >>>> https://datatracker.ietf.org/doc/charter-ietf-jmap/ >>>>=20 >>>> = ---------------------------------------------------------------------- >>>> BLOCK: >>>> = ---------------------------------------------------------------------- >>>>=20 >>>> I actually have a question about this how new transport part: >>>> "New transports for transporting JMAP will have security properties >>>> comparable to HTTPS. In particular they have to require TLS." >>>> Is the intention actually to have a "transport other https" or = rather something >>>> on top of https? I really would like to see further explanation = here what this >>>> is heading to! >>>=20 >>> Honestly, we only care about WSS (Websocket over TLS) transport. So = maybe the charter should just say that? >>>=20 >> Yes, please! >=20 > Check the latest text, I just updated the Charter to read: >=20 > 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). >=20 > and I removed 4). >=20 >=20 From nobody Fri May 3 09:40:44 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 07D2512028A; Fri, 3 May 2019 09:40:42 -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.1 Auto-Submitted: auto-generated Precedence: bulk Cc: jmap@ietf.org, jmap-chairs@ietf.org, The IESG Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Message-ID: <155690164202.7253.8030861630232117788.idtracker@ietfa.amsl.com> Date: Fri, 03 May 2019 09:40:42 -0700 Archived-At: Subject: [Jmap] WG Action: Rechartered 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, 03 May 2019 16:40:42 -0000 The JSON Mail Access Protocol (jmap) WG in the Applications and Real-Time Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the WG Chairs. 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 WSS (WebSocket over TLS, RFC 6455). 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 May 27 09:31:39 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 CFFFC12015D for ; Mon, 27 May 2019 09:31:37 -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_20=-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 m5q2HhUu123z for ; Mon, 27 May 2019 09:31:36 -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 B158A12001B for ; Mon, 27 May 2019 09:31:36 -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 x4RGVYnr030757 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 27 May 2019 09:31:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1558974696; bh=jiYxGq1FzFFXKx+k8RUSv0owo1L4+6IeyFWWXABPhJo=; h=To:From:Subject:Date; b=rajpU/XIJxS8FTKXDxNue4IhMh9AW4ILS8RifFZUU/mCwdTsYObzMG/4b6VB0pTh2 6wFDKBvOzRsa+8O97a2yHHXnl8GZBfgoFA9YoIEvyc1FhHZiGyD9C3ujbpdfUwDc6y hync6MstiFFijAwqmeVG4NK8VUo3BXQsa4Z35O0k= To: jmap@ietf.org From: Jim Fenton Message-ID: <839adaf2-fb72-44a3-eb90-b6abd851e71f@bluepopcorn.net> Date: Mon, 27 May 2019 09:31:29 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: [Jmap] Call for agenda topics: IETF 105/Montreal 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, 27 May 2019 16:31:38 -0000 IETF 105 in Montreal is fast approaching, and it's time to submit a meeting request and agenda. Please respond to the list with items you would like to present, and about how much time you think you will need. I'd like to receive these by 1 June so we can get a meeting request submitted on time. -Jim (as co-chair) From nobody Fri May 31 04:57:40 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 6605912009C for ; Fri, 31 May 2019 04:57:38 -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=H/EPucdc; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=kYb2sBtV 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 Vn4golFmXSIo for ; Fri, 31 May 2019 04:57:36 -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 6E596120044 for ; Fri, 31 May 2019 04:57:36 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 7E07A2203C; Fri, 31 May 2019 07:57:35 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Fri, 31 May 2019 07:57:35 -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=vcCC4SU ZEje29ei5b/Vvd1994MS9j+62EylOP+Z3c9o=; b=H/EPucdcOc9lMY5KI/iHTTj AstZLHGOeFvJom6ZRqnFRzh/G07yqBur9xeH1lsGn6l92qA+A/6enyfrMXgvi/8r QSLLvyckGGi/jVznu/xYCYibeXKWNnlnM/DNTclkq/XMrQI4CgYphNN0mEqnoHsr adyaw6BHNge0ecs96f8cgxvkxMevRA7sZaScN2jhQLlcnxKtpYMulNsiwR8BzGWO F0AyULgePvqorVM9HACgCLoozg5K+LbbjQ6pxya3a2f5c+ujwqbjp/wBRiUYKwmX vluokQphv144AveIv0MtYH8NeAOrSx69tXd9q5hxsA9Knlqoj97NWRz56s5BJyg= = 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=vcCC4S UZEje29ei5b/Vvd1994MS9j+62EylOP+Z3c9o=; b=kYb2sBtVbfwGIWirZm9vGv iiQaBUP/QViKvYkvO6ynLp422dsSngP9icOo7m38SLaubydfbZO9u5A0GYIrny2D VDBhdUA0sF2Kau3DHlXqO53+eu0XqpwTtOSx2qsO+7wl4M9NX5SAUd1IACuZbWiu IxNHePrGKMkv6HlaxQ0fEncy5L95v3t5kBuc8op0QDQJynbZbrXL5yL2idGe64jK zvZgEwsB4LzOM0kUXREeLy8xvKzbslQ2fblNeKF8lKftc7rIJbmsmCzmEl6+IS/4 Phxz88bNQ9aRtxA5Z9A+DHBe6F0GQb5nTxZ3uTHV+C7IVRKXedjwUX0GAqFhzmLw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudefuddggeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfpvghi lhculfgvnhhkihhnshdfuceonhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucfrrghrrghmpehmrghilhhfrhhomhepnhgvihhljhesfhgrshhtmhgrihhlthgvrghm rdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 26BB1180091; Fri, 31 May 2019 07:57:35 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-555-g49357e1-fmstable-20190528v2 Mime-Version: 1.0 Message-Id: In-Reply-To: <839adaf2-fb72-44a3-eb90-b6abd851e71f@bluepopcorn.net> References: <839adaf2-fb72-44a3-eb90-b6abd851e71f@bluepopcorn.net> Date: Fri, 31 May 2019 21:57:34 +1000 From: "Neil Jenkins" To: "Jim Fenton" , "IETF JMAP Mailing List" Content-Type: multipart/alternative; boundary=4a21c3b200d444ce956324d64db0e23e Archived-At: Subject: Re: [Jmap] Call for agenda topics: IETF 105/Montreal 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, 31 May 2019 11:57:38 -0000 --4a21c3b200d444ce956324d64db0e23e Content-Type: text/plain I would like to present the current status and work required for JMAP Calendars. I'm not sure exactly how much time should be allocated as I haven't yet compiled a list of all the discussion points to be addressed at this meeting, but I'd hazard somewhere in the region of 20-30 minutes would be about right. Cheers, Neil. --4a21c3b200d444ce956324d64db0e23e Content-Type: text/html
I would like to present the current status and work required for JMAP Calendars. I'm not sure exactly how much time should be allocated as I haven't yet compiled a list of all the discussion points to be addressed at this meeting, but I'd hazard somewhere in the region of 20-30 minutes would be about right.

Cheers,
Neil.
--4a21c3b200d444ce956324d64db0e23e--