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

Mirja Kuehlewind <ietf@kuehlewind.net> Thu, 02 May 2019 14:39 UTC

Return-Path: <ietf@kuehlewind.net>
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 <ietf@kuehlewind.net>
In-Reply-To: <63b454af-e96c-441a-a0fd-e12649a5deab@www.fastmail.com>
Date: Thu, 02 May 2019 16:39:24 +0200
Cc: Benjamin Kaduk <kaduk@mit.edu>, jmap@ietf.org, The IESG <iesg@ietf.org>, 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 <aamelnikov@fastmail.fm>
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: <https://mailarchive.ietf.org/arch/msg/jmap/cw526avt0gtby5zHYToIFdUYGEE>
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 14:39:32 -0000


> On 2. May 2019, at 15:52, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
> 
> 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?
> 
Yes, please!