IETF Logo Mail Archive

Re: [imapext] qresync WG kick-off

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 09 May 2013 19:35 UTC

Return-Path: <alexey.melnikov@isode.com>
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 606D221F8F6E for <imapext@ietfa.amsl.com>; Thu, 9 May 2013 12:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.953
X-Spam-Level:
X-Spam-Status: No, score=-100.953 tagged_above=-999 required=5 tests=[AWL=-0.654, BAYES_00=-2.599, MANGLED_TOOL=2.3, 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 aHPjZvFosXZ7 for <imapext@ietfa.amsl.com>; Thu, 9 May 2013 12:35:34 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 0567821F8F4D for <imapext@ietf.org>; Thu, 9 May 2013 12:35:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1368128132; d=isode.com; s=selector; i=@isode.com; bh=ELKRUffC938KBU34/aVX5Nd7wpOP45/4p2tt0MxSLNY=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=m7ttZMKFZ9pQL1v6aYJRtSfOQ9cbwvfZH5mkE2g8UU3WvneEhRs+wQVIRGuqhh5dKvgVhs adbs8QxiNKpvtvaY7uHDzRLcyIno9NDYJ+DZyhQjL6V0OK8WUtmxA9/UojBihNc4E1SMhV fxsU/OzYkA1NYVNKk99e6eJPSffEn6s=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by statler.isode.com (submission channel) via TCP with ESMTPA id <UYv6ggA6F7lP@statler.isode.com>; Thu, 9 May 2013 20:35:32 +0100
Message-ID: <518BFA87.8080209@isode.com>
Date: Thu, 09 May 2013 20:35:35 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: Dave Cridland <dave@cridland.net>
References: <XJHMsUTna4pbNfs0JEye9Ky1-nscMKjWdyW2k27WfNjwGm13A@smtp.gmail.com>
In-Reply-To: <XJHMsUTna4pbNfs0JEye9Ky1-nscMKjWdyW2k27WfNjwGm13A@smtp.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] qresync WG kick-off
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: Thu, 09 May 2013 19:35:38 -0000

On 08/05/2013 16:29, Dave Cridland wrote:
>
> As chairman.
>
> Just so everyone's on the same page, the plan for the working group is 
> essentially as follows:
>
> - Alexey's putting together starting drafts, which we'll be looking to 
> adopt.
>

Actually no, I think the WG should look at adopting 
http://datatracker.ietf.org/doc/draft-melnikov-5162bis/

List of changes for the current version (-01) is:

Appendix A.  Changes since RFC 5162

    Addressed erratum #1365:
    http://www.rfc-editor.org/errata_search.php?eid=1365

    Addressed erratum #1807:
    http://www.rfc-editor.org/errata_search.php?eid=1807

    Addressed erratum #1808:
    http://www.rfc-editor.org/errata_search.php?eid=1808

    Addressed erratum #1809:
    http://www.rfc-editor.org/errata_search.php?eid=1809

    Addressed erratum #3322:
    http://www.rfc-editor.org/errata_search.php?eid=3322

    Fixed some examples to report data that match requirements specified

Obviously the WG (once the draft is adopted by the WG) can decide to 
address these issues differently, but for now I assume that they are 
adequately addressed.

I don't have any pending changes to -01. I do have a list of pending 
issues though, which I can post here.

> - Once those drafts are out, we'll need reviewers on them to gauge 
> what milestones we should have - we currently just have a publication 
> request milestone of December; Eliot and I suspect this could be moved 
> much sooner if we feel that the issues are well-known.
>
> - We're not intending meeting. This includes online meetings - all 
> discussion will therefore be solely on this list.
>
> Just to refresh your memories, all discussion on this list 
> (working-group related or not) is covered by the Note Well; if you're 
> unclear what your responsibilities are under this, please ask.
>

v2.23.0 | Report a Bug | By Email