IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Tue, 07 February 2017 14:11 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 6D365129C42; Tue, 7 Feb 2017 06:11:47 -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 g8Qj-hMwumwF; Tue, 7 Feb 2017 06:11:45 -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 D4803129C38; Tue, 7 Feb 2017 06:11:45 -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 1cb6Uh-00007t-HB; Tue, 07 Feb 2017 14:11:43 +0000
Date: Tue, 07 Feb 2017 23:11:41 +0900
Message-ID: <m28tpiytsy.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Gren Elliot <fatkudu@gmail.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
In-Reply-To: <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@mail.gmail.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> <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@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="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nk9_WaasLb2bkG0wIkW6aIj24kA>
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 14:11:47 -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's wrapping fashion is.

randy

v2.23.0 | Report a Bug | By Email