[Jmap] JMAP protocol: transport
Philippe Duke <philippe46@netassist.ua> Sun, 12 February 2017 19:57 UTC
Return-Path: <philippe46@netassist.ua>
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 B3CA0129B05 for <jmap@ietfa.amsl.com>; Sun, 12 Feb 2017 11:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 nJ4MRQz1tCol for <jmap@ietfa.amsl.com>; Sun, 12 Feb 2017 11:57:35 -0800 (PST)
Received: from mail.netassist.ua (mail.netassist.ua [IPv6:2001:67c:1874:5::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B73C129AB6 for <jmap@ietf.org>; Sun, 12 Feb 2017 11:57:35 -0800 (PST)
Received: from [2a01:d0:305:1eaf::46] by mail.netassist.ua with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85 and XAMS 0.0.13) id 1cd0cp-0002rk-8m for jmap@ietf.org; Sun, 12 Feb 2017 22:20:05 +0200
To: jmap@ietf.org
From: Philippe Duke <philippe46@netassist.ua>
Organization: NetAssist LLC
Message-ID: <48ea211a-5022-2fc1-8d66-9bedde8a1953@netassist.ua>
Date: Sun, 12 Feb 2017 21:56:28 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="moPCXEIAiea9laseHxihGEnlLSlo9g1OJ"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/hYCCpHomdYUgeKdJ5aPMR3NfEu0>
Subject: [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: Sun, 12 Feb 2017 19:57:38 -0000
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? 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? 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. 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]? -- Philippe Duke Network software engineer System-level developer NetAssist LLC Ukraine Khreshchatyk Street, 10B, office 8 AS29632 http://netassist.ua Our GitHub Repository: https://github.com/netassist-ua
- [Jmap] JMAP protocol: transport Philippe Duke
- Re: [Jmap] JMAP protocol: transport Yoav Nir