Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
John C Klensin <john-ietf@jck.com> Mon, 13 February 2017 19:04 UTC
Return-Path: <john-ietf@jck.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 BC9891297CE for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:04:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=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 vrmGAukRXXTo for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:04:46 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC4F31296EE for <ietf@ietf.org>; Mon, 13 Feb 2017 11:04:45 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cdLvQ-000ERf-C0; Mon, 13 Feb 2017 14:04:36 -0500
Date: Mon, 13 Feb 2017 14:04:29 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, Dave Cridland <dave@cridland.net>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Message-ID: <3974108D855D9B53126DFEA7@PSB>
In-Reply-To: <23132594-9f68-d7dc-fe92-6487182d4e59@dcrocker.net>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com> <23132594-9f68-d7dc-fe92-6487182d4e59@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pMvWAi8fshKG6p0Welr63f02AWo>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
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: Mon, 13 Feb 2017 19:04:48 -0000
(Top Post) Exactly. Could not have said it better myself. There is one additional issue here. JMAP (or some hypothetical xMAP) can either aspire to be a cleaner, more modern, less LISP-like interface to (more or less, see below) the same functionality as IMAP _or_ it can aspire to be a better idea, with a different underlying architecture and/or reference model, functionality, etc. Can't have it both ways, at least without moving from discussions about proxies and overlays and into discussions about translators that are a lot more like gateways, gateways that, like most of their predecessors, mostly work and mostly preserve functionality and semantics. My confusion about this effort -- and it has been considerable-- is that I've heard different statements claiming goals in both categories. That isn't acceptable, if one because a WG proposal for one approach should be evaluated differently from one proposing the there one. The choice really must be made now and, whatever it is, should be absolutely crystal-clear in the charter... in addition to the things Dave describes below, which should also be spelled out. john --On Monday, February 13, 2017 09:30 -0800 Dave Crocker <dhc@dcrocker.net> wrote: > On 2/13/2017 9:17 AM, Dave Cridland wrote: >> I don't think this is true. > ... >> JMAP, on the other hand, can cope with both gmail style >> labels and IMAP-style mailboxes, by stated design. > > > The constraints/flexibility of an effort depend on the goals > it asserts and the support for those goals. I think it's > dandy to target an access protocol that is substantially > different from the features/style/whatever of IMAP. The > requirements are to be very clear about the > features/style/whatever of the new effort, very clear about > the expected benefits, and very clear about the support for > that. > > Given the long history of IMAP, the proposed JMAP effort > should offer clear assertions of the relative differences and > benefits of the new effort, to aid in assessing likely appeal > of the effort. > > So, for example, the above comment about JMAP's handling of > different reference models is substantive and appealing. > However the various notes that have been posted about JMAP > leave me thinking that there is less clarity about the effort > than one would like, among JMAP's supporters. > > The embodiment of the clarity needs to be the charter text and > I don't think it's made its case well enough. For example, I > don't see a reference to the ability to support different > referencing models. > > d/
- Re: WG Review: JSON Mail Access Protocol (jmap) Dave Crocker
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Alexey Melnikov
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Adrien de Croy
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Dave Crocker
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Phillip Hallam-Baker
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Neil Jenkins
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Gren Elliot
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Randy Bush
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Dave Crocker
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Ted Lemon
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Gren Elliot
- Fwd: Re: [Jmap] WG Review: JSON Mail Access Proto… Gren Elliot
- Re: [Jmap] service discovery, was WG Review: JSON… John Levine
- Re: Fwd: Re: [Jmap] WG Review: JSON Mail Access P… Dave Crocker
- Re: Fwd: Re: [Jmap] WG Review: JSON Mail Access P… Randy Bush
- Re: Fwd: Re: [Jmap] WG Review: JSON Mail Access P… John C Klensin
- Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access P… Adrien de Croy
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Neil Jhaveri
- Re: Fwd: Re: [Jmap] WG Review: JSON Mail Access P… Gren Elliot
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Joe Hildebrand
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Ted Lemon
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Dave Crocker
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Neil Jenkins
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Yoav Nir
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Dave Cridland
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Alexey Melnikov
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Alexey Melnikov
- Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Acc… Alexey Melnikov
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Andrew Sullivan
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Alexey Melnikov
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Spencer Dawkins at IETF
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… John C Klensin
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Dave Crocker
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Ted Lemon
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Alexey Melnikov
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Ted Hardie
- Re: WG Review: JSON Mail Access Protocol (jmap) -… John Levine
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Alexey Melnikov
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Pete Resnick
- Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access P… Ted Lemon
- Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access P… Dave Crocker
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… ned+ietf
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… John Levine
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Phillip Hallam-Baker
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… John C Klensin
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Dave Cridland
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Dave Crocker
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Ted Lemon
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… John C Klensin
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… John C Klensin
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Ted Lemon
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Dave Cridland
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Dave Cridland
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Ted Lemon
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… Alexey Melnikov
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… ned+ietf
- Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail… John C Klensin