Re: [imap5] Designing a new replacement protocol for IMAP

Dave Cridland <dave@cridland.net> Wed, 15 February 2012 22:42 UTC

Return-Path: <dave@cridland.net>
X-Original-To: imap5@ietfa.amsl.com
Delivered-To: imap5@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB7C21F84A0 for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 14:42:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DvGjaDiqfktf for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 14:42:21 -0800 (PST)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [IPv6:2001:470:1f09:882:2e0:81ff:fe29:d16a]) by ietfa.amsl.com (Postfix) with ESMTP id 3AAD221E8084 for <imap5@ietf.org>; Wed, 15 Feb 2012 14:42:19 -0800 (PST)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 69BFA1168087; Wed, 15 Feb 2012 22:42:18 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uazC3QqBtqKp; Wed, 15 Feb 2012 22:42:11 +0000 (GMT)
Received: from puncture (puncture.dave.cridland.net [IPv6:2001:470:1f09:882:221:85ff:fe3f:1696]) by peirce.dave.cridland.net (Postfix) with ESMTPA id AC1C01168067; Wed, 15 Feb 2012 22:42:10 +0000 (GMT)
References: <833EE8EEE88E4ADE5CDDDADB@caldav.corp.apple.com> <4F3835A1.7060804@qbik.com> <B764BD8C8B6047E659EABBE2@caldav.corp.apple.com> <4F397212.1030107@qbik.com> <20120213210805.GB13029@launde.brong.net> <alpine.LSU.2.00.1202151405550.30682@hermes-2.csi.cam.ac.uk> <1329315552.1444.140661036879893@webmail.messagingengine.com> <4F3BBFA4.8010107@isode.com> <1329316981.8310.140661036883625@webmail.messagingengine.com> <66F68487BF0EED4BA7D767E2410F30B3EFF259456A@FRSPX100.fr01.awlatosorigin.net> <20120215211301.GA16253@launde.brong.net> <4F3C2362.2060007@qbik.com> <4F3C3356.6030100@panozzo.it>
In-Reply-To: <4F3C3356.6030100@panozzo.it>
MIME-Version: 1.0
Message-Id: <3077.1329345730.658893@puncture>
Date: Wed, 15 Feb 2012 22:42:10 +0000
From: Dave Cridland <dave@cridland.net>
To: Giovanni Panozzo <giovanni@panozzo.it>, "Discussion on drastically slimming-down IMAP." <imap5@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
Subject: Re: [imap5] Designing a new replacement protocol for IMAP
X-BeenThere: imap5@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion on drastically slimming-down IMAP." <imap5.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imap5>, <mailto:imap5-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imap5>
List-Post: <mailto:imap5@ietf.org>
List-Help: <mailto:imap5-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imap5>, <mailto:imap5-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2012 22:42:26 -0000

On Wed Feb 15 22:36:06 2012, Giovanni Panozzo wrote:
> Il 15/02/2012 22:28, Adrien de Croy ha scritto:
>> 
>> having dealt with support issues relating primarily to HTTP for  
>> the last
>> 17 years, I'd STRONGLY recommend against using anything HTTP  
>> based. The
>> number of proxies that break WebDAV makes it problematic alone.
>> 
>> If some clients need HTTP-based access to some IMAP function, they  
>> can
>> use a gateway.
> 
> Such a gateway should be a mandatory part of the protocol, or we  
> will end up on having a lot of servers with the http gateway and  
> many other servers without it, really bad user experience.
> 
> Could we think a "skype-like" solution, where the client makes two  
> attempts:
> 
> 1) Direct socket connection on a single TCP port
>  and then, in case of failure
> 2) https tunnel of the same protocol (thru optional client side  
> proxy).
>    https is more likely to survive across proxyes than http.

BOSH.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade