Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP

Adrien de Croy <adrien@qbik.com> Thu, 16 February 2012 07:11 UTC

Return-Path: <adrien@qbik.com>
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 AE0DB21F85A0 for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 23:11:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.66
X-Spam-Level:
X-Spam-Status: No, score=-4.66 tagged_above=-999 required=5 tests=[AWL=-2.061, 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 vKNoqYxxhvnV for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 23:10:58 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [210.55.214.35]) by ietfa.amsl.com (Postfix) with ESMTP id EEA6D21F8591 for <imap5@ietf.org>; Wed, 15 Feb 2012 23:10:54 -0800 (PST)
Received: From [192.168.1.10] (unverified [219.89.217.118]) by SMTP Server [210.55.214.35] (WinGate SMTP Receiver v7.1.0 (Build 3381)) with SMTP id <0018865982@smtp.qbik.com>; Thu, 16 Feb 2012 20:10:52 +1300
Message-ID: <4F3CABDB.8080203@qbik.com>
Date: Thu, 16 Feb 2012 20:10:19 +1300
From: Adrien de Croy <adrien@qbik.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120202 Thunderbird/11.0
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
References: <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> <4F3BC7DA.5070803@gulbrandsen.priv.no> <20120215181047.GB13906@launde.brong.net> <alpine.OSX.2.00.1202151020140.38441@hsinghsing.panda.com> <20120215213122.GB16253@launde.brong.net> <4F3C2C1B.6030408@qbik.com> <3077.1329344733.342803@puncture> <4F3CA887.9050509@gulbrandsen.priv.no>
In-Reply-To: <4F3CA887.9050509@gulbrandsen.priv.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: imap5@ietf.org
Subject: Re: [imap5] Feature set? - was Re: 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: Thu, 16 Feb 2012 07:11:04 -0000

On 16/02/2012 7:56 p.m., Arnt Gulbrandsen wrote:
> On 02/15/2012 11:25 PM, Dave Cridland wrote:
>> This mailing list is "Discussion on drastically slimming-down IMAP", and
>> you've listed the properties of ACAP, SIEVE, IMAP, CalDAV, CardDAV *and*
>> Submission, and then thrown in a kitchen sink too.
> As I see it, he's listed features which are in the Exchange protocol and
> in the unnamed protocol spoken by gmail's javascript heap and its
> mothership.
>
> That makes them worthy of discussion.
>
> I know IETF dogma is that protocols shouldn't overlap. But it's a weak
> kind of dogma: IMAP overlaps with POP, POP overlaps with Submission,
> various IMAP extensions with ACAP and what's that about IMSP? I could go on.

actually with a layered approach, this dogma could be maintained, as the 
facilities would be able to be specified separately.

Would be interesting to see wire-line protocol on GMail - I bet they use 
Json

Regards

Adrien


>
> Arnt
> _______________________________________________
> imap5 mailing list
> imap5@ietf.org
> https://www.ietf.org/mailman/listinfo/imap5

-- 
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com