Re: [Jmap] JMAP-over-Websocket text tweak

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 18 August 2020 12:29 UTC

Return-Path: <alexey.melnikov@isode.com>
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 5BA853A09A0 for <jmap@ietfa.amsl.com>; Tue, 18 Aug 2020 05:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.047
X-Spam-Level:
X-Spam-Status: No, score=-3.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.949, SPF_HELO_NONE=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=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 3cu6Pd1ihP8l for <jmap@ietfa.amsl.com>; Tue, 18 Aug 2020 05:29:46 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 369633A099F for <jmap@ietf.org>; Tue, 18 Aug 2020 05:29:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1597753785; d=isode.com; s=june2016; i=@isode.com; bh=PQtvM20T9m9QqB08bSyUeVgLeVmvOhGVFlpyZJhFquQ=; 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=xJ2z5D7DOJ/t+rli92I8OWnXjjRhNMWxG/jlfXtGcoBGx3+z0jkqcwnM+AXd0Tk3S9OBFX lABcQ/qlXKUQpWClWPGgl0yerU5IzWL8OS5MvcEZzNwCZSDw8W49cSM+NHZQXQeViXJHcU u2APRW6Yh7ed2scyIm4Fa074nDAe19Y=;
Received: from [172.27.253.188] (connect.isode.net [172.20.0.72]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <XzvJuQBUoAcn@statler.isode.com>; Tue, 18 Aug 2020 13:29:45 +0100
To: Ken Murchison <murch@fastmail.com>, jmap@ietf.org
References: <59640963-b6f9-0206-c7f0-4c664a6ac4f2@fastmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <a65c9573-4436-af06-a815-0d485c3f0182@isode.com>
Date: Tue, 18 Aug 2020 13:29:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
In-Reply-To: <59640963-b6f9-0206-c7f0-4c664a6ac4f2@fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------6160B4CD95BA07A414F48EF6"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/pLXqzd1JJE8PWoFMzv8npjk06nk>
Subject: Re: [Jmap] JMAP-over-Websocket text tweak
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: Tue, 18 Aug 2020 12:29:47 -0000

Hi Ken,

On 18/08/2020 13:22, Ken Murchison wrote:
>
> All,
>
> The JMAP-over-Websocket draft is in AUTH48 and as I'm reviewing the 
> text one last time, I'd like to make one, hopefully non-controversial, 
> change in light of the fact the Bron make soon be writing up a spec 
> for Blob/[get|set].  The soon-to-be RFC 8887 current says this:
>
> Binary data is handled per Section 6 of [RFC8620] via a separate HTTP connection or stream.
>
> I'd like to change it to this:
>
> Binary data is handled per Section 6 of [RFC8620] (via a separate connection or stream) or per a future extension to JMAP or this specification.
>
>
> Any objections or suggested wordsmithing?
>
This looks reasonable to me.

Best Regards,

Alexey