Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity

Andrew Sullivan <ajs@anvilwalrusden.com> Wed, 08 February 2017 14:23 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54161129B14 for <ietf@ietfa.amsl.com>; Wed, 8 Feb 2017 06:23:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=hn7Rq26z; dkim=pass (1024-bit key) header.d=yitter.info header.b=AfJRKf7m
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 hKCTx1kgtUVh for <ietf@ietfa.amsl.com>; Wed, 8 Feb 2017 06:23:15 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CF54129AE7 for <ietf@ietf.org>; Wed, 8 Feb 2017 06:23:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id BF2ABBD554 for <ietf@ietf.org>; Wed, 8 Feb 2017 14:22:44 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1486563764; bh=qWgMfhExooknikK+82BzMBrr0jxKinq24aItckG9soc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=hn7Rq26z8ci8kszUuC5b+ngIizqZlKT7NA8gNtTIpeln5+YlvjQNVCfvg+FuInPBt gS0fQKixcVpmFEgLbIgryAe7drOh6waTOZ3iFtxBzUyj4s0gSUoUNdK88jj9zO7Tiq ma4UfhkI7ZkMWUMb4zp1XEOI/0pZGXzHegH06mCo=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHbWifGMrcKu for <ietf@ietf.org>; Wed, 8 Feb 2017 14:22:43 +0000 (UTC)
Date: Wed, 08 Feb 2017 09:22:41 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1486563763; bh=qWgMfhExooknikK+82BzMBrr0jxKinq24aItckG9soc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=AfJRKf7mYATgsWpSRl2e1ILBTyUHQfBrDUvBT/ImK00X0fj6KaaSDFuw4xh8/vW3/ lLmgtofZ+o/g1CJkz5pOd78SsbeQ/CNvz/+Uj1YxCkVZHbGd4rZTmK+zkn+m0vOVV7 dr1zNOa9EapxcHRtejxylpm+w1xbarokCclCm3hE=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Message-ID: <20170208142241.GB84460@mx4.yitter.info>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qc7g6iisIC82ZJLiyo_-5OdzUks>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 14:23:16 -0000

On Wed, Feb 08, 2017 at 01:52:00PM +0000, Alexey Melnikov wrote:
> 
> Agreed. JMAP and IMAP are likely to co-exist for long time.
> 

Isn't that exactly the complaint?  Something like, "Long periods of
co-existence need to have lots of benefits or an existential one, or
else they're not a good idea."

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com