IETF Logo Mail Archive

Re: [Jmap] JMAP protocol: transport

Yoav Nir <ynir.ietf@gmail.com> Mon, 13 February 2017 06:44 UTC

Return-Path: <ynir.ietf@gmail.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 6B81B1294D8 for <jmap@ietfa.amsl.com>; Sun, 12 Feb 2017 22:44:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=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=gmail.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 kQLU1EvfkJA7 for <jmap@ietfa.amsl.com>; Sun, 12 Feb 2017 22:44:57 -0800 (PST)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 42692126FDC for <jmap@ietf.org>; Sun, 12 Feb 2017 22:44:56 -0800 (PST)
Received: by mail-wm0-x22d.google.com with SMTP id v186so150375811wmd.0 for <jmap@ietf.org>; Sun, 12 Feb 2017 22:44:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=TuSHMS+w8XGzZsE4EiPOswnAqor1ZpdkHODtxZNNJAY=; b=DfqJMCwOu1i7E/I3rrjjvsw971n17LfFJrJn5gWHX2VJ7jwsafrWBZUUmWBT1nRis3 owYIKVvVSxZZ/pRKzPmseRxVAXHy76/knSpMVNQnzXWNagJHhH7xcTuKE3K3Uub84BfR WjY4uDqbdWq4ZeupGFF1QIoT0abccOX+4oYFzK2TQhSE6nzBdx2RorFByDRFEjVsR5XT Ktx/0q9eJfD5YTI7Ed1KGY5CLsQQgZAfrfKeNGwRa74rx0OOF/CDV/R7M6ve4vEW3XXs l6fnhd8mlpT54OCkAAA/0SfHpnV1AbFXHHNRBizxMM+8hYQlDVgNPXgtBEr9KmYgIy8O +4Gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=TuSHMS+w8XGzZsE4EiPOswnAqor1ZpdkHODtxZNNJAY=; b=QC/63keuyFLke4zZSD3RtSGIUUOQHSIwtOzG0mOd8cNLSnAtRSm2iBPHWPV/KADLkU jyUtjHHTFjnI3eycLSDrcbr7jMzfMn4/hCrR11kXF3SHtbyZZ292GAlClMveRduR+drg Zna/4ckvZn3OOWZ9EUGvepgIB/vfGp3IuV46Sy+z3WI5aBLWyldV4ttNUsrkq2nQZiUr Le+2aNJA5CIJSnwEBCK0eT5tlyPlls9KZYB5jrS2VFK3a0rR17QP6qj2ARui3xOTqtWM vluoY3A8EiKxXBdXpVopLiNtvyMnwOabgHwTsRdXFjJhNP8SpVx1t/lAdqsmmPkmfuSe q8MA==
X-Gm-Message-State: AMke39mdg4s4uXih2aHnn4jlZBg1+DcQs60wgP+KPGTvlG2S//uOd/vCuM1HpT8FarFGbQ==
X-Received: by 10.28.0.2 with SMTP id 2mr17438558wma.141.1486968295209; Sun, 12 Feb 2017 22:44:55 -0800 (PST)
Received: from [192.168.137.219] ([109.253.200.31]) by smtp.gmail.com with ESMTPSA id z90sm12563594wrc.24.2017.02.12.22.44.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Feb 2017 22:44:53 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <55B4EC7F-74B0-4C96-8EC4-47F677C26067@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_20762686-38B6-4534-9F9C-F27C2C306CBE"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Mon, 13 Feb 2017 08:44:48 +0200
In-Reply-To: <48ea211a-5022-2fc1-8d66-9bedde8a1953@netassist.ua>
To: Philippe Duke <philippe46@netassist.ua>
References: <48ea211a-5022-2fc1-8d66-9bedde8a1953@netassist.ua>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/XhFHbOUceCPpum3IxI8aucf9ZAo>
Cc: jmap@ietf.org
Subject: Re: [Jmap] JMAP protocol: transport
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: Mon, 13 Feb 2017 06:44:59 -0000

Hi, Philippe

On 12 Feb 2017, at 21:56, Philippe Duke <philippe46@netassist.ua> wrote:

> Hello members of JMAP WG,
> 
> I would like to join your discussion to help create a new email fetch
> protocol. I would like to ask is what is the current state of design?

The current state is that there is a mailing list and a proposed charter for a working group.

There are also two drafts that have the current design by Neil Jenkins from FastMail:
https://tools.ietf.org/html/draft-jenkins-jmap-00 <https://tools.ietf.org/html/draft-jenkins-jmap-00>
https://tools.ietf.org/html/draft-jenkins-jmapmail-00 <https://tools.ietf.org/html/draft-jenkins-jmapmail-00>

Of course, if and when a working group is formed, all change control goes to the group, and if the group decides to replace the JSON with DER and OOB attachments with in-band RFC3252-encoded attachments, then that what is going to be (although that would be regrettable)

> How do you plan to implement notifications? What would transport SHOULD
> be used? Will the protocol be TCP-independent and work only on top of
> HTTP like RFC6455?

Current design is a web service on top of HTTPS.

>  What is your view on special  mailboxes (like Inbox, Drafts, Trash,
> Spam and so on) already done by [RFC6154]? So many clients have a mess
> with IMAP LIST special folders.

There is some info on that in section 2 of https://tools.ietf.org/html/draft-jenkins-jmapmail-00 <https://tools.ietf.org/html/draft-jenkins-jmapmail-00>

> As far as I realize, the base approach of the JMAP is to make mail
> access available from browser applications without need to interop on
> IMAP. What is your approach for WebSocket [RFC6455]?

When you use email from a browser application, you’re really downloading the application from the mail provider. You don’t really need standardization to have a gmail client provided by Google talk to the gmail servers. The protocol’s aim (see this: https://www.ietf.org/mail-archive/web/imapext/current/msg05820.html <https://www.ietf.org/mail-archive/web/imapext/current/msg05820.html> ) is to allow you to “write a good MUA”, so not necessarily a browser. Perhaps not even primarily a browser.

HTH

Yoav

v2.23.0 | Report a Bug | By Email