Re: [imapext] [ietf-smtp] Fwd: Request to form a new WG: JMAP

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 09 November 2016 18:42 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2226129619 for <imapext@ietfa.amsl.com>; Wed, 9 Nov 2016 10:42:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.498
X-Spam-Level:
X-Spam-Status: No, score=-3.498 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=-1.497, 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 mZWwJXJd3smg for <imapext@ietfa.amsl.com>; Wed, 9 Nov 2016 10:42:40 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id BDFFE12960D for <imapext@ietf.org>; Wed, 9 Nov 2016 10:42:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1478716960; d=isode.com; s=june2016; i=@isode.com; bh=XMzhcQmvvkgBpOgLBroyOTp3VpJUURQDCZ2XZewBm54=; 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=YEHxeDZ7NlZjNLrP8rJXY5DRTbqnAUEobGPRDhpKhYm5uQ1mEjBPZBcPWvgdt4mNwO/lBp 9WRDvIjagA/aJhG1vz7B35mdHw7v3tsHdcBFQq3j7O24QFYkYG/cjl8fKFANT2nbx2CQkl Q9HJS1rqWWvKyqBCXIRQYroJPAVJmLA=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <WCNuHwBM5R0p@waldorf.isode.com>; Wed, 9 Nov 2016 18:42:39 +0000
To: imapext@ietf.org
References: <1478539079.1706686.780110457.75B1F9CF@webmail.messagingengine.com> <a786d82d-7134-c7bc-24ef-5dfb56e7bbac@isode.com> <56DA516EAC53C07E3F453BA6@JcK-HP8200> <58220833.4000806@gmail.com> <01Q73SYPHLDI011H9Q@mauve.mrochek.com> <5F4EE3F805C40EF25D1E0E57@JcK-HP8200> <75bbd8ea-9e80-4b9b-93e7-a7d823b03783@gulbrandsen.priv.no>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <a5eb6203-86f7-075b-9530-37306ff01c7a@isode.com>
Date: Wed, 09 Nov 2016 18:42:22 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
In-Reply-To: <75bbd8ea-9e80-4b9b-93e7-a7d823b03783@gulbrandsen.priv.no>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/T-C1KQqZvOeLpulTb37n0adeZPw>
Subject: Re: [imapext] [ietf-smtp] Fwd: Request to form a new WG: JMAP
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2016 18:42:42 -0000

On 09/11/2016 18:22, Arnt Gulbrandsen wrote:

> John C Klensin writes:
>> But, unless we can get rid of IMAP (and some of the
>> functionality, like disconnected mode, that can't obviously be
>> supported over a purely HTTPS/JSON interface) entirely, it seems
>> to me that an HTTPS/JOSN approach is additive, requiring the
>> mail environment to support both it and IMAP for (at least) a
>> very long time.
>
> Not at all. There are many, many clients that serve a very small 
> audience and need only one protocol.
>
> It has been mentioned on this list that a two-digit number of clients 
> account for >99% of people's usage, and at another time that around a 
> thousand different clients used a particular IMAP extension on a 
> particular day at gmail. That's quite a difference, and my guess is 
> that a big part of that is programs that implement someone's business 
> logic and act on at most a handful of mail accounts. Those programs 
> need to be simple to write.
Agreed. I think there are applications which might still be easier to 
write using IMAP. Some applications might find JMAP to be easier.