IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Tue, 07 February 2017 20:03 UTC

Return-Path: <randy@psg.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 25DE7129E80; Tue, 7 Feb 2017 12:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 mxeOFI-kjpWt; Tue, 7 Feb 2017 12:03:47 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 1866A129E7B; Tue, 7 Feb 2017 12:03:47 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cbBzN-0001oH-GX; Tue, 07 Feb 2017 20:03:45 +0000
Date: Wed, 08 Feb 2017 05:03:42 +0900
Message-ID: <m2poitydi9.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Gren Elliot <fatkudu@gmail.com>
Subject: Re: Fwd: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
In-Reply-To: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="ISO-8859-7"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y1yF5Rpht061gIiqNye_9c8K7QU>
Cc: jmap@ietf.org, 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 20:03:48 -0000

>> 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)
> 
> and now, because we will have to be backward compatible, it will be
> three. so that third had best be a really massive win. and i am not
> seeing it. what i am seeing is second system syndrome in a wrapper of
> whatever today <http://airmail.calendar/2017-02-07%2012:00:00%20GMT>'s
> wrapping fashion is.
> 
> randy
> 
> Why?  You will either be using IMAP/SMTP to access your mail/submit
> your messages or you will be using JMAP.  If you have the option of
> the latter, you’ve just halved the number of things that need
> configuring.

how does the server forward the submitted mail to the global internet?

how does the server migrate 200 or 2,000 imap users at human speed,
i.e. over months?

yet another protocol that requires a flag day.  that has worked out
so well for ipv6.

randy

v2.23.0 | Report a Bug | By Email