Re: [imapext] Proposal for a new IMAP Working Group to revise CONDSTORE & QRESYNC
Cyrus Daboo <cyrus@daboo.name> Wed, 06 March 2013 15:57 UTC
Return-Path: <cyrus@daboo.name>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7479721F8BF6 for <imapext@ietfa.amsl.com>; Wed, 6 Mar 2013 07:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 x1JIuLeTJOjp for <imapext@ietfa.amsl.com>; Wed, 6 Mar 2013 07:57:53 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id CB9EA21F8970 for <imapext@ietf.org>; Wed, 6 Mar 2013 07:57:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 483D03E9BF2A; Wed, 6 Mar 2013 10:57:53 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fo1zgbHY9SfC; Wed, 6 Mar 2013 10:57:51 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 0A1713E9BF1B; Wed, 6 Mar 2013 10:57:50 -0500 (EST)
Date: Wed, 06 Mar 2013 10:57:47 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Alexey Melnikov <alexey.melnikov@isode.com>, imapext@ietf.org
Message-ID: <E50AC0A2E9E5C6195681F82B@caldav.corp.apple.com>
In-Reply-To: <513607D5.4090808@isode.com>
References: <513607D5.4090808@isode.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1197"
Subject: Re: [imapext] Proposal for a new IMAP Working Group to revise CONDSTORE & QRESYNC
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 15:57:54 -0000
Hi Alexey, --On March 5, 2013 at 2:57:25 PM +0000 Alexey Melnikov <alexey.melnikov@isode.com> wrote: > So please comment on whether you think this work is worth doing and on > the proposed charter text. > > I've also posted a new version of RFC 5162bis > (http://tools.ietf.org/html/draft-melnikov-5162bis-01), which addressed > most (but not all) of existing errata on the document. If a new WG is to > be formed, I propose that the document is used as one of the initial > documents. What about also doing an update to RFC4549? I think the big thing client implementors want is a single clear specification of extensions that describe how to accurately do mailbox synchronization. To that end I would even argue that we should be looking at pieces to take out to achieve that goal. For example, how many clients actually make use of the condition store piece of CONDSTORE, as opposed to just the SELECT/SEARCH sync operations? Same goes for QRESYNC - what pieces of it have actually been used by clients? Are there bits that could be removed? So I'd like to see more than a simple rev of the documents to fix errata - or at least lets not rule that out right now. -- Cyrus Daboo
- [imapext] Proposal for a new IMAP Working Group t… Alexey Melnikov
- Re: [imapext] Proposal for a new IMAP Working Gro… Timo Sirainen
- Re: [imapext] Proposal for a new IMAP Working Gro… Alexey Melnikov
- Re: [imapext] Proposal for a new IMAP Working Gro… Dave Cridland
- Re: [imapext] Proposal for a new IMAP Working Gro… Barry Leiba
- Re: [imapext] Proposal for a new IMAP Working Gro… Pete Maclean
- Re: [imapext] Proposal for a new IMAP Working Gro… Barry Leiba
- Re: [imapext] Proposal for a new IMAP Working Gro… Michael M Slusarz
- Re: [imapext] Proposal for a new IMAP Working Gro… Alexey Melnikov
- Re: [imapext] Proposal for a new IMAP Working Gro… Cyrus Daboo
- Re: [imapext] Proposal for a new IMAP Working Gro… Dave Cridland
- Re: [imapext] Proposal for a new IMAP Working Gro… Alexey Melnikov
- Re: [imapext] Proposal for a new IMAP Working Gro… Michael M Slusarz
- Re: [imapext] Proposal for a new IMAP Working Gro… Cyrus Daboo
- Re: [imapext] Proposal for a new IMAP Working Gro… Michael M Slusarz
- Re: [imapext] Proposal for a new IMAP Working Gro… Timo Sirainen
- Re: [imapext] Proposal for a new IMAP Working Gro… Adrien W. de Croy
- [imapext] Re: Proposal for a new IMAP Working Gro… Jan Kundrát
- Re: [imapext] Proposal for a new IMAP Working Gro… Adrien W. de Croy
- [imapext] Re: Proposal for a new IMAP Working Gro… Jan Kundrát
- Re: [imapext] Proposal for a new IMAP Working Gro… Dave Cridland
- Re: [imapext] Proposal for a new IMAP Working Gro… Ashley Clark
- Re: [imapext] Proposal for a new IMAP Working Gro… Barry Leiba