Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Ted Hardie <ted.ietf@gmail.com> Wed, 08 February 2017 18:33 UTC
Return-Path: <ted.ietf@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 363DA129D36 for <ietf@ietfa.amsl.com>; Wed, 8 Feb 2017 10:33:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 31UnLNkAu735 for <ietf@ietfa.amsl.com>; Wed, 8 Feb 2017 10:33:53 -0800 (PST)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 B2124129D34 for <ietf@ietf.org>; Wed, 8 Feb 2017 10:33:53 -0800 (PST)
Received: by mail-qt0-x22c.google.com with SMTP id k15so174168655qtg.3 for <ietf@ietf.org>; Wed, 08 Feb 2017 10:33:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GKERFyD2Ezkzhffz+UMFTu0flDMXpJAfruenUEFZ69Y=; b=tnpj9ymoORVwGDXST9LvCDddrlLCUj/eHdVvVkpHRwYYVNvjfEqTtT2U4sa0FuFRU4 ZPF5A12Kv4HZfBL541R/89aRalEKHkcD3rBdBfvMp4l/2SAZSCX7Scd+O9MsU336cyQD dqHh4UjHKZs09k7uL+dm7ir8LrUtjqY42lwVGaM0EYCOdb2S9XEs3PTj7t6ODxUKHBns 7PBUKvMCSMs/lndhgC6L4e0oDQ7zV5EM6VtoiI8X0dFGX2uRMW/zFlguL569Amfsqy1K VlHhcFVGCTR7p0lWKpc2Ckt4ZlJlmzRAvLZwfeBLeoC+FZNfWtZU9Rhv/E/HGNz7MUHO N7uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GKERFyD2Ezkzhffz+UMFTu0flDMXpJAfruenUEFZ69Y=; b=NIaDou5fTRtE7Aq2v3c70DoZea3lwla1Rj1lE5N3dtNRxjcafulJxIKAhPvWrkjMC7 2mypcCcA9zeeYmLopZsrESndABRiKUfkGzUGmr0G/rq54PGQoXBbe7weCdQcyCXhIBqL 5QfbOEQiY3V61nyZLa8nDilK7kQAS9/gjCmnfnseXR1XXaMyBHvwP0ej8eGHVB7hZ/67 pbNeZvCTgT74CdCDiCxDEgW665DTXF63Go5Amd0L//tvRGspYUpK9R9ilMDWEwLHAtGa cGa9uX0q1c9wDizmn/ju9yLIyUBu/LiWVdHmrQDFZMbafRdPf0paiWfelmxjH/xzpces z9tw==
X-Gm-Message-State: AMke39kfpsKbURiy/retAEmdRgLmUa0jmq2eDggW/igAnt4Fj71AaXP7CPJawDi1DUMOOADkOHH5o93Bu2tfjQ==
X-Received: by 10.200.53.50 with SMTP id y47mr20711888qtb.114.1486578832477; Wed, 08 Feb 2017 10:33:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.174.226 with HTTP; Wed, 8 Feb 2017 10:33:22 -0800 (PST)
In-Reply-To: <32D2801528D191A01AD4D3B2@PSB>
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>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 08 Feb 2017 10:33:22 -0800
Message-ID: <CA+9kkMCCQLhJ+dD7Ga2L4axQ51VjXKAsh+OyinW2M1zefKF7OQ@mail.gmail.com>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary="001a11397f763dd6480548091be3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QaAAgg2Zpc3gOHs6rmAeo0wcHWs>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, IETF <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: Wed, 08 Feb 2017 18:33:55 -0000
On Wed, Feb 8, 2017 at 7:03 AM, John C Klensin <john-ietf@jck.com> wrote: > > > Except for the small minority of users who switch MUAs back and forth (see > below), I > would expect any given user to use either an IMAP approach, a > JSON or JSON-like one, or neither. I am confused by this claim. There are substantial numbers of users who access their mail from mobile and from laptop/desktop systems. Those, generally speaking, are different MUAs. > No long transition as far > as they are concerned. However, from the perspective of > someone trying to maintain servers or a mailstore, the fact that > there will be both types of users (for a long time if not > forever), it implies the need to maintain (and configure, > support, etc.) both IMAP/SMTP and JMAP facilities in parallel > and to support, also for a long time, the ability to convert > between the two formats. Also, if that conversion is not > absolutely lossless, there will be a large collection of ongoing > problems, for an equally long time. > > Those _are_ reasons to not let JMAP progress because it could > easily make the mail system work worse. I think you and the proponents fundamentally disagree about what the current mail system is. They see a welter of proprietary systems based on JSON and HTTP, and they want to clean it up by standardizing on one approach. You see a standardized system of IMAP/SMTP and want to avoid standardizing another system. From the proponents perspective Andrew's question of "long periods of coexistence" has to be seen in the context of "long periods of coexistence" _of proprietary systems_ . If you don't agree on what the mail system is, it's not particularly surprising that you don't agree on the method for optimizing it. Not, as Andrew (and > several others) have suggested, not a risk we should encourage > unless the benefits and improvements are significant. > > The proponents seem to have demonstrated that there are proprietary systems in place. So I believe the calculus of benefits and improvements must be done over a different set of data points. regards, Ted > best, > john > > > >
- 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