Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Gren Elliot <fatkudu@gmail.com> Tue, 07 February 2017 11:26 UTC
Return-Path: <fatkudu@gmail.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 9100D129B50 for <ietf@ietfa.amsl.com>; Tue, 7 Feb 2017 03:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.676
X-Spam-Level:
X-Spam-Status: No, score=-1.676 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, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 8WjUCzD-wBQT for <ietf@ietfa.amsl.com>; Tue, 7 Feb 2017 03:26:48 -0800 (PST)
Received: from mail-yw0-x244.google.com (mail-yw0-x244.google.com [IPv6:2607:f8b0:4002:c05::244]) (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 BA4EB129B4E for <ietf@ietf.org>; Tue, 7 Feb 2017 03:26:47 -0800 (PST)
Received: by mail-yw0-x244.google.com with SMTP id v73so9199584ywg.1 for <ietf@ietf.org>; Tue, 07 Feb 2017 03:26:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:cc; bh=JZ1LcDLMFtYf/pms0OomSQlhu/5hbi8pGZWFzxy/PQo=; b=Cz8+/uXBz25zX4R0Ris0RIylI/2Xi4+p2wWPaWstdxwo6atHnI2nrpC+FdpWtCoItX TXEyyfBVjNpknZwT9H9UPsR3JFwuyfeaYw7DJcRsAnwxX+nFFurxEvScTvOfEzIkf5nE wNZMVXjbSAwRqvDtSeSmRpAiYgvyA4Ir2WNw9imgu/WLn2ZRLimQM/51Oo0h0O29G5FX T/K3hGmaUWPkHu4EasgQU1GCJ/dcfIznmRJTCsg/10w40KgpEKTJxDzrhI+LDiYyQnYC GNK8lU+QPoBh/DX/y+2NVfHne5bJDQyPK2Q0USpwEevqM4ocQycLz50pOQbfJOeBU/XT 49iQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:cc; bh=JZ1LcDLMFtYf/pms0OomSQlhu/5hbi8pGZWFzxy/PQo=; b=qOhN0ybRSs5kgz+kbbMZtcz40R1j4sSTN9I22ibXvOGZdAekN9kVcxb0gN51yDo7t8 d4I4Cn+DBXlQ7Lcz2SF0nWADcOyNNTV+/gaTyX7+jHRdrg8Z+cBvz3eAlqwzftLu/9BD uW9VqIZwOsnfKF4HlM5iCXhQtg0HXqgp0f6z0HeHQ3f6MQjVobmHZLOTST+AiGm0RmKy VN1liD19tsAPtTih5yPTZMpXRboT+HIR/UYGtEv1Fo3He9Et+j7GNwIfukuZa4kD48R4 GXZCjG4uaGpA/31/AIJ5dWNhizZxbfrMvgQ4EhttInI42cH/1B0YW5M0DBi4QWJ1OSO7 mr8w==
X-Gm-Message-State: AMke39m1PLA+XdhqR9Viypyoi+6Vcp2udpy5JEI1nbRKzaE7hLw/cnFelmNK1nOF4nqDs/7D1PVCDszNL7OHcg==
X-Received: by 10.13.193.68 with SMTP id c65mt10909933ywd.88.1486466806915; Tue, 07 Feb 2017 03:26:46 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 7 Feb 2017 03:26:45 -0800
From: Gren Elliot <fatkudu@gmail.com>
In-Reply-To: <1486435969.2314063.872594064.21072F60@webmail.messagingengine.com>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net> <1486435969.2314063.872594064.21072F60@webmail.messagingengine.com>
X-Mailer: Airmail (397)
MIME-Version: 1.0
Date: Tue, 07 Feb 2017 03:26:45 -0800
Message-ID: <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@mail.gmail.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Content-Type: multipart/alternative; boundary="001a114e6c00ff45dc0547ef05c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UgZDOBULwdHAQKHqrG7E40qTHlA>
Cc: jmap@ietf.org, iesg <iesg@ietf.org>, 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: Tue, 07 Feb 2017 11:26:49 -0000
Hi, Just to add my voice to the call for easier configuration where we don’t force users to configure countless different things. Trying to setup a new device for use with open protocols is a complete nightmare - you end up needing to configure 2 things for mail (IMAP and SMTP) plus something for Contacts (CardDAV - perhaps LDAP as well) plus something for Calendar (CalDAV). Many users, myself included are also at the mercy of frequent forced password changes, which necessitate modifying the configuration of each of these on each device. Bizarrely, I suspect across 99% odd of use cases, this separation is completely artificial as the same password is used on the server for all services (and cannot be different because most servers regard them as all relating to the same account). This configuration complexity must waste countless hours across the world and is a major reason why businesses welcome ActiveSync - just to solve this one huge problem with the open protocol landscape. There may be some good esoteric academic reasons why keeping IMAP and message submission protocols separate but I think the real world has clearly showed that the added complexity is too expensive. I believe JMAP is intending to extend from just Mail to encompass Calendar and Contacts too and I truly hope it will (in a way that doesn’t require servers to offer everything) Folks at Calconnect and the IETF have been working on https://tools.ietf.org/html/draft-daboo-aggregated-service-discovery-03 which attempts to ease the configuration burden but that looks like being a long process and needs buy in from device vendors to be really successful. I see most of the need behind this work as a sticky plaster trying to cover up the un-necessary mess we have created :-( It would be nice to see config dialogs where user’s are asked for minimal information (user name, perhaps server name) and then the device discovers what is available there (Mail/Contacts/Calendar/…) and offers the user a way to select them and perhaps a choice of preferred client(s) to handle each service. The way Android handles some things, where a single bit of software is responsible for server access and perhaps local caching and other clients can provide UIs to access this is kind of neat too. Regards, Gren Elliot Zimbra Software Engineer at Synacor
- 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