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

Michel Sébastien <Sebastien.Michel@atos.net> Wed, 15 February 2012 21:00 UTC

Return-Path: <sebastien.michel@atos.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 D7D3521E8043 for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 13:00:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.699
X-Spam-Level:
X-Spam-Status: No, score=-3.699 tagged_above=-999 required=5 tests=[BAYES_50=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 D2LO+289ca7w for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 13:00:01 -0800 (PST)
Received: from smtp1.mail.atosorigin.com (smtp1.mail.atosorigin.com [160.92.103.80]) by ietfa.amsl.com (Postfix) with ESMTP id 2E10921F864D for <imap5@ietf.org>; Wed, 15 Feb 2012 13:00:01 -0800 (PST)
Received: from filter.atosorigin.com (localhost [127.0.0.1]) by mxfed001 (Postfix) with ESMTP id E96DB26396F7; Wed, 15 Feb 2012 21:59:57 +0100 (CET)
Received: from mail.awl.fr.atosorigin.com (serv-smtp-wse01.fr.atosworldline.com [160.92.103.180]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "mail.awl.fr.atosorigin.com", Issuer "VeriSign Class 3 Secure Server CA - G2" (verified OK)) by mxfed001 (Postfix) with ESMTP id E2DB526396F0; Wed, 15 Feb 2012 21:59:57 +0100 (CET)
Received: from frspx302.fr01.awl.atosorigin.net (10.24.253.187) by frspx401.priv.atos.fr (10.24.220.7) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 15 Feb 2012 21:59:57 +0100
Received: from FRSPX100.fr01.awl.atosorigin.net ([10.24.253.184]) by frspx302.fr01.awl.atosorigin.net ([10.24.253.187]) with mapi; Wed, 15 Feb 2012 21:59:57 +0100
From: Michel Sébastien <Sebastien.Michel@atos.net>
To: Bron Gondwana <brong@fastmail.fm>, Alexey Melnikov <alexey.melnikov@isode.com>, Tony Finch <dot@dotat.at>
Date: Wed, 15 Feb 2012 21:59:56 +0100
Thread-Topic: [imap5] Designing a new replacement protocol for IMAP
Thread-Index: Aczr8CkSWFTKkA7BTBek7e3hr6szzwAMZNZw
Message-ID: <66F68487BF0EED4BA7D767E2410F30B3EFF259456A@FRSPX100.fr01.awl.atosorigin.net>
References: <1328732126.32086.140661033971485@webmail.messagingengine.com> <201202090820.28260.thomas@koch.ro> <4F337E61.5040702@qbik.com> <201202101544.51364.thomas@koch.ro> <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>
In-Reply-To: <1329316981.8310.140661036883625@webmail.messagingengine.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Discussion on drastically slimming-down IMAP." <imap5@ietf.org>
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 21:00:06 -0000

>> On 15/02/2012 14:19, Bron Gondwana wrote:
>> > On Wed, Feb 15, 2012, at 02:11 PM, Tony Finch wrote:
>> >> Is there any reason to keep subscriptions in IMAP 5 ?
>> > I envisage "subscription" as either an annotation or a "Special Use"
>> > on a folder rather than yet another axis of data.
>> +1.
Does it works with shared folders ?

> I was chatting to one of the other guys on our team yesterday about data modelling in this context.
>
> Mail is a structured data store, with some small set of types of data stored in the IMAP "model".  The IMAP protocol is very much about the
> communications, and trying to optimise specific use cases.
>
> But at the core, it's about querying and modifying data in a particular model, with some constraints on the valid modifications - both for integrity and for ACL permissions reasons.
>
> Along with a side dose of syncronising up offline modifications to that same data model.
>
> This is not a problem that's unique to email.  There's nothing really special about email here unless you make it special.  Sure there's a bunch of indexed and optimised ways of viewing that data - sort by trimmed subject, encodings, etc.  All of which could be expressed as generic queries against the data model with a query optimiser on the far end rather than needing a custom syntax for everything...
>

Some others seems to think that webdav could be a candidate : http://www.webdav.org/other/faq.html#Q26
A new layer on top of webdav, with some keywords registered at IANA. But I just don't like the trend to use HTTP for everything... despite its interest here.



Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité d'Atos ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.