Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
Alexey Melnikov <alexey.melnikov@isode.com> Wed, 08 February 2017 13:35 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 E61B0129A38; Wed, 8 Feb 2017 05:35:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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=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 o7RnXlMSy-UY; Wed, 8 Feb 2017 05:35:14 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 811D0129A21; Wed, 8 Feb 2017 05:35:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1486560913; d=isode.com; s=june2016; i=@isode.com; bh=vO6lDZmEov1k+sdWXvpEYmOBvYU6jdAVFLd+udMlg5I=; 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=drMEImk78QlDE4RSNCWkhM8UwrZcw+jkHVlZHtkGaPGJtbnWj0RsoOZa0vq6z+lZCg84n2 SRruXNGx0Os8rDE2IllzrvBxofXwXI4hGRNsvK7JZ8qKgRMcmrUemLRe+RaBQt0gZDRZYd J7NjnqGx8wRF2ReilbzPd7lIL8Xq1FA=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <WJsekAAY1zyf@statler.isode.com>; Wed, 8 Feb 2017 13:35:13 +0000
To: dcrocker@bbiw.net
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <125d54fa-eb60-cf14-db93-0c5602be58ad@isode.com>
Date: Wed, 08 Feb 2017 13:34:55 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/HZ8A6_wIqfnAEl1Ydw0OctINFas>
Cc: jmap@ietf.org, ietf@ietf.org, iesg <iesg@ietf.org>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 08 Feb 2017 13:35:16 -0000
Hi Dave, On 06/02/2017 20:11, Dave Crocker wrote: > Alexey, thanks for the quick followup. > > inline... > > On 2/6/2017 11:41 AM, Alexey Melnikov wrote: > >> There also needs to be clarity about the relationship between the JSON > >> encodings and the encodings in 'native' Internet Mail. >> See drafts (and above). > > Drafts? What drafts? Perhaps you mean: > > https://tools.ietf.org/html/draft-jenkins-jmap > > Except that no draft is cited in the charter. I realized that I accidentally deleted an important sentence from the Charter while doing editing. One of the paragraphs should have read: The work of this group is limited to developing a protocol for a client synchronising data with a server. The work will be based on draft-jenkins-jmap and draft-jenkins-jmapmail. Any server-to-server issues are out of scope for this working group. New end-to-end encryption mechanisms are out of scope, but the work should consider how to integrate with existing standards such as S/MIME and OpenPGP. Best Regards, Alexey
- [Jmap] WG Review: JSON Mail Access Protocol (jmap) The IESG
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Randy Bush
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Arnt Gulbrandsen
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Alexey Melnikov
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Alexey Melnikov
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Phillip Hallam-Baker