Re: [Jmap] Mirja Kühlewind's Block on charter-ietf-jmap-01-01: (with BLOCK)

"Alexey Melnikov" <aamelnikov@fastmail.fm> Thu, 02 May 2019 13:53 UTC

Return-Path: <aamelnikov@fastmail.fm>
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: <xms:TPbKXEoZA_xa2nDA_mV8bNH5BkXPSD2Kg9pJBQYPn-XmGVCsW2XR7Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrieelgdejvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdetlhgv gigvhicuofgvlhhnihhkohhvfdcuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrd hfmheqnecuffhomhgrihhnpehivghtfhdrohhrghdphhhtthhpshdrihhnnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmhenuc evlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:TPbKXN5IwMbPBoEzVtOXBJ_xElOl6jYEfGgwZ-rtvuExhURG8Gg61w> <xmx:TPbKXCr-yPq7h6EiwVSOtPsB-3bWG6MTirgP6R3icbQE17pf56BgQw> <xmx:TPbKXHhvB4Eua_7366vVocyd1G_VMZgm9HQtyCJW05QlKbPBhK4FGQ> <xmx:TfbKXNp32GskMH4yIIP-MeYyRt_dvmGkpK1d0e4RMikEtCJElyjZAw>
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 <aamelnikov@fastmail.fm>
To: Mirja Kuehlewind <ietf@kuehlewind.net>, Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, jmap@ietf.org, jmap-chairs@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/H3Rtip2jPYTmCq5RY4Lo0ab60Sc>
Subject: Re: [Jmap] Mirja Kühlewind's Block on charter-ietf-jmap-01-01: (with BLOCK)
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2019 13:53:21 -0000

On Thu, May 2, 2019, at 2:43 PM, Mirja Kühlewind via Datatracker wrote:
> 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!

Honestly, we only care about WSS (Websocket over TLS) transport. So maybe the charter should just say that?