
From nobody Tue Jun  2 11:22:30 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 246A61B3491 for <imapext@ietfa.amsl.com>; Tue,  2 Jun 2015 11:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RwgkaVpIvKzo for <imapext@ietfa.amsl.com>; Tue,  2 Jun 2015 11:22:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A97C1B3496 for <imapext@ietf.org>; Tue,  2 Jun 2015 11:22:20 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: <imapext@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150602182220.13912.79468.idtracker@ietfa.amsl.com>
Date: Tue, 02 Jun 2015 11:22:20 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/ppvRx4ouRgoq393Et_--AfYiSAQ>
Subject: [imapext] State changed: charter-ietf-imapapnd-00-00
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 02 Jun 2015 18:22:27 -0000

State changed to Internal review.

URL: https://datatracker.ietf.org/doc/charter-ietf-imapapnd/


From nobody Tue Jun  2 11:22:33 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED731B30A9; Tue,  2 Jun 2015 11:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWLJiLWhc5g1; Tue,  2 Jun 2015 11:22:27 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8A41B2FCA; Tue,  2 Jun 2015 11:22:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <iesg-secretary@ietf.org>, <iesg@ietf.org>, <imapext@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150602182227.13920.77958.idtracker@ietfa.amsl.com>
Date: Tue, 02 Jun 2015 11:22:27 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/HSkGjvYidh6HO2QZNR6t7POY3cQ>
Subject: [imapext] Telechat update notice: <charter-ietf-imapapnd-00-00.txt>
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 02 Jun 2015 18:22:28 -0000

Placed on agenda for telechat - 2015-06-11
ID Tracker URL: https://datatracker.ietf.org/doc/charter-ietf-imapapnd/


From nobody Tue Jun  2 11:28:53 2015
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE591B34B6 for <imapext@ietfa.amsl.com>; Tue,  2 Jun 2015 11:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.122
X-Spam-Level: 
X-Spam-Status: No, score=0.122 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyEJRs6SYAub for <imapext@ietfa.amsl.com>; Tue,  2 Jun 2015 11:28:45 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CF501B34B2 for <imapext@ietf.org>; Tue,  2 Jun 2015 11:28:45 -0700 (PDT)
Received: by igbyr2 with SMTP id yr2so93879721igb.0 for <imapext@ietf.org>; Tue, 02 Jun 2015 11:28:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=ISr2bzY3EBpLxEPYUuwFbQbgFLSyl/juLNV4qYYv624=; b=VtD7WBGqjvn3M/SBG24vFQeKyNfEgHU3GjcaPE6OX5/gwGElPy7RpM8k9AZNl7Gj+8 8M6Aw/Ntpd0FYoyHnGUGBKMxd77aq+xqP+VLDsOx0/DTXiQxuICdezpCtWlnIZN+93S1 s6WgcFaP6kXOQvIn0ZkgvpLJImDWYFENUFmHjQwiV+3oK4OCw4mryFVGrlT99O9NUxdD bDQ5URuO1xdBOdKHYERutuBkff19REaOk0xcV5qbSlszaDbvhT23MAqFXZAgCIKx/Ica MesETkQMcQU7+7Ig3ARdkjvyad/U1/pBJW3hjQ+j3Xi9mIgMAGysGZrZeS0aIQWMr+Ze 7P4w==
MIME-Version: 1.0
X-Received: by 10.50.225.35 with SMTP id rh3mr21706973igc.29.1433269724888; Tue, 02 Jun 2015 11:28:44 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.136.216 with HTTP; Tue, 2 Jun 2015 11:28:44 -0700 (PDT)
In-Reply-To: <02454F842DD7B449B96715A2AD90C0365EBD6658@exMB5.telecom.sna.samsung.com>
References: <551A0193.5030104@isode.com> <552C457A.50700@aol.com> <02454F842DD7B449B96715A2AD90C0365EBD6658@exMB5.telecom.sna.samsung.com>
Date: Tue, 2 Jun 2015 14:28:44 -0400
X-Google-Sender-Auth: H7erq2jlbVLwrrXhSsOyCR9b-wc
Message-ID: <CAC4RtVDdqgFX=4y1Pd_s42hKRrCci_uGBap=yrEu4wYgcCQ5iw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "imapext@ietf.org" <imapext@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/COoSzl4ZizaAcQ5K_1p0kGAc3yg>
Subject: Re: [imapext] Charter Proposal for a new IMAP related Working Group
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 02 Jun 2015 18:28:46 -0000

I have initiated the chartering process for the "IMAP APPEND
Extensions" working group (imapapnd):
https://datatracker.ietf.org/wg/imapapnd/charter/

Note that it only includes the specs for append limit and literal-.
That's because I don't think it's a good idea for the same community
to try to put through four (or more) documents at once, and because
the charter process isn't really so onerous.  So let's get these done,
and as we complete those we can write up another charter to handle
replace and/or snippet.

Does that make sense to folks?

Timing: I've put the initial IESG/IAB review on the telechat agenda
for next week, 11 June.  It will then do out for External Review for
two weeks, and have the final approval ballot on 25 June.

Barry, ART DIrector


From nobody Fri Jun 12 09:07:39 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2173E1A1B5A for <imapext@ietfa.amsl.com>; Fri, 12 Jun 2015 09:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TlKnHX2eQygl for <imapext@ietfa.amsl.com>; Fri, 12 Jun 2015 09:07:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C92A31A6F13 for <imapext@ietf.org>; Fri, 12 Jun 2015 09:07:24 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: <imapext@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150612160724.16891.7387.idtracker@ietfa.amsl.com>
Date: Fri, 12 Jun 2015 09:07:24 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/NA8u2xM0EAOhRCgxGaCkH0Q53Gk>
Subject: [imapext] State changed: charter-ietf-imapapnd-00-00
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 12 Jun 2015 16:07:38 -0000

State changed to External review.

URL: https://datatracker.ietf.org/doc/charter-ietf-imapapnd/


From nobody Fri Jun 12 09:07:45 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F9FA1A6EE4; Fri, 12 Jun 2015 09:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0_HxYqDpSjgq; Fri, 12 Jun 2015 09:07:42 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A6C881A1BAC; Fri, 12 Jun 2015 09:07:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <iesg-secretary@ietf.org>, <iesg@ietf.org>, <imapext@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150612160731.14426.56005.idtracker@ietfa.amsl.com>
Date: Fri, 12 Jun 2015 09:07:31 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/32prLIH9OMtLVVpFKruKS06UT1Y>
Subject: [imapext] Telechat update notice: <charter-ietf-imapapnd-00-00.txt>
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 12 Jun 2015 16:07:43 -0000

Telechat date has been changed to 2015-06-25 from 2015-06-11
ID Tracker URL: https://datatracker.ietf.org/doc/charter-ietf-imapapnd/


From nobody Fri Jun 12 09:17:55 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB02A1A8954; Fri, 12 Jun 2015 09:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZwRWiWvrAwK; Fri, 12 Jun 2015 09:17:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 876F81A1C04; Fri, 12 Jun 2015 09:17:10 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150612161710.25579.65994.idtracker@ietfa.amsl.com>
Date: Fri, 12 Jun 2015 09:17:10 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/5yF2DJQXjOeVTpIVNGFuqSv9vRM>
Cc: imapapnd WG <imapext@ietf.org>
Subject: [imapext] WG Review: IMAP APPEND Extensions (imapapnd)
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 12 Jun 2015 16:17:42 -0000

A new IETF working group has been proposed in the Applications and
Real-Time Area. The IESG has not made any determination yet. The
following draft charter was submitted, and is provided for informational
purposes only. Please send your comments to the IESG mailing list (iesg
at ietf.org) by 2015-06-22.

IMAP APPEND Extensions (imapapnd)
------------------------------------------------
Current Status: Proposed WG

Assigned Area Director:
  Barry Leiba <barryleiba@computer.org>

Mailing list
  Address: imapext@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/imapext
  Archive: https://www.ietf.org/mail-archive/web/imapext/

Charter:

The Internet Message Access Protocol (IMAP), defined in RFC 3501,
specifies a protocol for transferring email messages between a server
that implements a message store, and a client. It also includes commands
for manipulating the message store -- creating, deleting, and renaming
mailboxes, adding a message to a mailbox, and copying messages from one
mailbox to another.

IMAP (RFC 3501) contains the "literal" syntactic construct for
transferring blocks of data. Sending an IMAP literal string entails
first sending the length of the string, waiting for a response that
accepts a string of that length, then sending the string itself.
This complicates client implementations and resulted in definition
of the "LITERAL+" IMAP extension (RFC 2088), which specifies an
alternative
type of literal string that does not require an extra network round trip
(the length and data are sent together). While this extension is quite
commonly supported by servers, some implementations have it disabled
because there is no good way for clients to know whether a server can
accept big messages.

The IMAP APPEND Extensions (imapapnd) working group will produce two
related Standards Track specifications, which are targeted at improving
the current situation:

* The first is based on draft-jayantheesh-imap-appendlimit-extension,
and defines a way for servers to announce an APPEND limit for a
particular
server or a particular mailbox.

* The second is based on draft-melnikov-rfc2088bis, and describes
implementation choices for servers supporting the LITERAL+ extension,
as well as defining a new "LITERAL-" extension that has similar
properties but provides a mechanism allowing servers to avoid
denials of service by malicious or naive IMAP clients.

As part of the protocol development, implementation experience on both
the client and server side is highly desirable, so that the actual
operational value of this extension can be assessed. The working group
will document the results of this experience on the working group wiki.

No other IMAP extension work is in scope for this working group.

Milestones:



From nobody Sun Jun 21 08:27:44 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 690141A8791 for <imapext@ietfa.amsl.com>; Sun, 21 Jun 2015 08:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8eCO05dMydFT for <imapext@ietfa.amsl.com>; Sun, 21 Jun 2015 08:27:42 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B994D1A878E for <imapext@ietf.org>; Sun, 21 Jun 2015 08:27:42 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: <imapext@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150621152742.26265.52578.idtracker@ietfa.amsl.com>
Date: Sun, 21 Jun 2015 08:27:42 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/_QVg3pk2pqRm5NOF_wi8-LyXCLA>
Subject: [imapext] State changed: charter-ietf-imapapnd-00-00
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 21 Jun 2015 15:27:43 -0000

State changed to IESG review.

URL: https://datatracker.ietf.org/doc/charter-ietf-imapapnd/


From nobody Wed Jun 24 07:33:04 2015
Return-Path: <ben@nostrum.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E93FE1B2AC2; Tue, 23 Jun 2015 17:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDulqiLQ0g05; Tue, 23 Jun 2015 17:23:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 131C81B30E2; Tue, 23 Jun 2015 17:23:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Ben Campbell" <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150624002301.16159.6606.idtracker@ietfa.amsl.com>
Date: Tue, 23 Jun 2015 17:23:01 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/gCm2itbPsWeQmrlvVuZojRnwFWM>
X-Mailman-Approved-At: Wed, 24 Jun 2015 07:33:02 -0700
Cc: imapext@ietf.org
Subject: [imapext] Ben Campbell's Yes on charter-ietf-imapapnd-00-00: (with COMMENT)
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Jun 2015 00:23:08 -0000

Ben Campbell has entered the following ballot position for
charter-ietf-imapapnd-00-00: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-imapapnd/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Some milestones would be good.



From nobody Fri Jun 26 13:42:12 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF7AF1A701E; Fri, 26 Jun 2015 13:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hqG7amLDRpTE; Fri, 26 Jun 2015 13:42:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C05941AC413; Fri, 26 Jun 2015 13:42:08 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150626204208.21887.25710.idtracker@ietfa.amsl.com>
Date: Fri, 26 Jun 2015 13:42:08 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/EJvaztOLAepqhooqLRCyAA6AT7w>
Cc: imapapnd WG <imapext@ietf.org>
Subject: [imapext] WG Action: Formed IMAP APPEND Extensions (imapapnd)
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 26 Jun 2015 20:42:11 -0000

A new IETF working group has been formed in the Applications and
Real-Time Area. For additional information please contact the Area
Directors or the WG Chair.

IMAP APPEND Extensions (imapapnd)
------------------------------------------------
Current Status: Proposed WG

Chairs:
  S Moonesamy <sm+ietf@elandsys.com>

Assigned Area Director:
  Barry Leiba <barryleiba@computer.org>

Mailing list
  Address: imapext@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/imapext
  Archive: https://mailarchive.ietf.org/arch/browse/imapext/

Charter:

The Internet Message Access Protocol (IMAP), defined in RFC 3501,
specifies a protocol for transferring email messages between a server
that implements a message store, and a client. It also includes commands
for manipulating the message store -- creating, deleting, and renaming
mailboxes, adding a message to a mailbox, and copying messages from one
mailbox to another.

IMAP (RFC 3501) contains the "literal" syntactic construct for
transferring blocks of data. Sending an IMAP literal string entails
first sending the length of the string, waiting for a response that
accepts a string of that length, then sending the string itself.
This complicates client implementations and resulted in definition
of the "LITERAL+" IMAP extension (RFC 2088), which specifies an 
alternative type of literal string that does not require an extra 
network round trip (the length and data are sent together). While this 
extension is quite commonly supported by servers, some implementations 
have it disabled because there is no good way for clients to know 
whether a server can accept big messages.

The IMAP APPEND Extensions (imapapnd) working group will produce two
related Standards Track specifications, which are targeted at improving
the current situation:

* The first is based on draft-jayantheesh-imap-appendlimit-extension,
and defines a way for servers to announce an APPEND limit for a 
particular server or a particular mailbox.

* The second is based on draft-melnikov-rfc2088bis, and describes
implementation choices for servers supporting the LITERAL+ extension,
as well as defining a new "LITERAL-" extension that has similar
properties but provides a mechanism allowing servers to avoid
denials of service by malicious or naive IMAP clients.

As part of the protocol development, implementation experience on both
the client and server side is highly desirable, so that the actual
operational value of this extension can be assessed. The working group
will document the results of this experience on the working group wiki.

No other IMAP extension work is in scope for this working group.


From nobody Fri Jun 26 14:12:35 2015
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E71A1A8722 for <imapext@ietfa.amsl.com>; Fri, 26 Jun 2015 14:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eJ0AFsqrx8WU for <imapext@ietfa.amsl.com>; Fri, 26 Jun 2015 14:12:32 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE9A71A1C02 for <imapext@ietf.org>; Fri, 26 Jun 2015 14:12:31 -0700 (PDT)
Received: by igblr2 with SMTP id lr2so21304083igb.0 for <imapext@ietf.org>; Fri, 26 Jun 2015 14:12:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=ZdmAewaaD0iY2Dzo04SPPCoNY41DnXwz0H828DaNNGk=; b=xsSaFiiNaJYcBYUhzuI9yq+qwx4E2IlrBWMihLThFRdOG1RvzJYTKpdri/LtVDF5Vi QAC0OEBnaNMraBuLnL02sWGCwEQ7ihgoSnjxQdZMe4hf8gDdJBpbVRBz8YolP1qCNF6O 0EZQAO8Qplx1e5ZHRKryWCTq6vidvP0bWf2PRS+9IvceK7q5n6W8MaMPcW2RNkBgeFmH f8Vfm2eo+siJr3SDW8jieMJNFkqVYGs1jos6T23YSu8/KQWFL10qJhPzmaOm5O4xAuWJ 6/Kw8jZrxy3La6vkq/LYtYpydEVI6drbitmiT1IOODoHad1Pyx8i4v2wu9vfmYUkg7RV TGlw==
MIME-Version: 1.0
X-Received: by 10.42.81.201 with SMTP id a9mr5882989icl.9.1435353151191; Fri, 26 Jun 2015 14:12:31 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.178.11 with HTTP; Fri, 26 Jun 2015 14:12:31 -0700 (PDT)
In-Reply-To: <20150626204208.21887.25710.idtracker@ietfa.amsl.com>
References: <20150626204208.21887.25710.idtracker@ietfa.amsl.com>
Date: Fri, 26 Jun 2015 18:12:31 -0300
X-Google-Sender-Auth: xYQyTsZVjZUx1Xrvmm1_kT33PgA
Message-ID: <CAC4RtVBMXjOZw4KHJj28Q=qANj55WYk=TqmayhyB+0S7Mcvcow@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: imapapnd WG <imapext@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/5U_X6MQ2-5Ypyk5NUg-itV1n9og>
Subject: Re: [imapext] WG Action: Formed IMAP APPEND Extensions (imapapnd)
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 26 Jun 2015 21:12:33 -0000

Congratulations, all y'all: you have a working group.  And you have a
chair, in the very capable "SM" (Subramanian Moonesamy, but let's
stick with "SM" to save bandwidth).  I've decided to ask SM to run
this show solo, as this working group isn't going to meet (it'll do
everything on the mailing list), SM has no chance of having any
conflicts of interest, and we should be done with this stuff fairly
quickly.

The working group's first task is to create milestones, and SM should
be getting that process started tout de suite.

Let's roll...

Barry

On Fri, Jun 26, 2015 at 5:42 PM, The IESG <iesg-secretary@ietf.org> wrote:
> A new IETF working group has been formed in the Applications and
> Real-Time Area. For additional information please contact the Area
> Directors or the WG Chair.
>
> IMAP APPEND Extensions (imapapnd)
> ------------------------------------------------
> Current Status: Proposed WG
>
> Chairs:
>   S Moonesamy <sm+ietf@elandsys.com>
>
> Assigned Area Director:
>   Barry Leiba <barryleiba@computer.org>
>
> Mailing list
>   Address: imapext@ietf.org
>   To Subscribe: https://www.ietf.org/mailman/listinfo/imapext
>   Archive: https://mailarchive.ietf.org/arch/browse/imapext/
>
> Charter:
>
> The Internet Message Access Protocol (IMAP), defined in RFC 3501,
> specifies a protocol for transferring email messages between a server
> that implements a message store, and a client. It also includes commands
> for manipulating the message store -- creating, deleting, and renaming
> mailboxes, adding a message to a mailbox, and copying messages from one
> mailbox to another.
>
> IMAP (RFC 3501) contains the "literal" syntactic construct for
> transferring blocks of data. Sending an IMAP literal string entails
> first sending the length of the string, waiting for a response that
> accepts a string of that length, then sending the string itself.
> This complicates client implementations and resulted in definition
> of the "LITERAL+" IMAP extension (RFC 2088), which specifies an
> alternative type of literal string that does not require an extra
> network round trip (the length and data are sent together). While this
> extension is quite commonly supported by servers, some implementations
> have it disabled because there is no good way for clients to know
> whether a server can accept big messages.
>
> The IMAP APPEND Extensions (imapapnd) working group will produce two
> related Standards Track specifications, which are targeted at improving
> the current situation:
>
> * The first is based on draft-jayantheesh-imap-appendlimit-extension,
> and defines a way for servers to announce an APPEND limit for a
> particular server or a particular mailbox.
>
> * The second is based on draft-melnikov-rfc2088bis, and describes
> implementation choices for servers supporting the LITERAL+ extension,
> as well as defining a new "LITERAL-" extension that has similar
> properties but provides a mechanism allowing servers to avoid
> denials of service by malicious or naive IMAP clients.
>
> As part of the protocol development, implementation experience on both
> the client and server side is highly desirable, so that the actual
> operational value of this extension can be assessed. The working group
> will document the results of this experience on the working group wiki.
>
> No other IMAP extension work is in scope for this working group.
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext


From nobody Fri Jun 26 15:21:12 2015
Return-Path: <sm@elandsys.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F4C1ACE36 for <imapext@ietfa.amsl.com>; Fri, 26 Jun 2015 15:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kaSskYwL5foP for <imapext@ietfa.amsl.com>; Fri, 26 Jun 2015 15:21:10 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 822761ACE35 for <imapext@ietf.org>; Fri, 26 Jun 2015 15:21:10 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.214.63]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id t5QMKwjr006681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <imapext@ietf.org>; Fri, 26 Jun 2015 15:21:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1435357269; x=1435443669; bh=XcTg9DCot082rT/P8A5hlBYkeBiRINtE9SConDc/7e4=; h=Date:To:From:Subject; b=uJyuWEYcYhv/tTVSeXT+XB9bt9h202Ox4JXyG4+mOCa1pp02YmhQ3j8mofRzVWAkJ k81sRYwkUrJ1rerOimhwov+Wx611jUvFDSL0mmZhGvWGGo/7fcId8nvM/AikGBSC7R T3bxgebhRdfDKP4BNQ2b8UxvTZENEhZyKi2vvKzo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1435357269; x=1435443669; i=@elandsys.com; bh=XcTg9DCot082rT/P8A5hlBYkeBiRINtE9SConDc/7e4=; h=Date:To:From:Subject; b=AZ3egaHT0fTlehP7f1xedEJV3RvAEVUpqFcpDxgLPtlnI0BVgoheSngh3lv++bPQc KmMpKoNSWUERBhJYgEzslVoE7Y+m0+yWm/pez9n7ktxu0PBw1e6ZwF+N6fQxSWgDhj 5VCZ+lgTqemlompPYSPRRkZ5Mp+JihGB0tJczT8Y=
Message-Id: <6.2.5.6.2.20150626144931.0f2aed80@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 26 Jun 2015 15:20:09 -0700
To: imapext@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/HMH5ieLEkLyFRUqePOL4yp05pBo>
Subject: [imapext] imapapdb milestones
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 26 Jun 2015 22:21:11 -0000

Hello,

The Working Group Charter for IMAP APPEND Extensions (imapapnd) is at 
https://datatracker.ietf.org/wg/imapapnd/charter/  The working group 
has to deliver two Standards Track specifications to the IESG.  The 
first step is set the milestones for the 
draft-jayantheesh-imap-appendlimit-extension and 
draft-melnikov-rfc2088bis.  Could the working group participants 
please suggest a date for each of the two drafts?  I would like to 
have the milestones settled by 30 June so that the working group can 
proceed with the technical discussions about the two drafts.

If you have any questions about the work of the working group please 
feel free to raise them on the mailing list [1].  You can also email 
me if you find that easier.

Regards,
S. Moonesamy (as imapapdb WG Chair)

1. https://www.ietf.org/mailman/listinfo/imapext


From nobody Sat Jun 27 15:52:36 2015
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A477F1A92EB for <imapext@ietfa.amsl.com>; Sat, 27 Jun 2015 15:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bR_GFfrLOvRg for <imapext@ietfa.amsl.com>; Sat, 27 Jun 2015 15:52:34 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [217.34.220.150]) by ietfa.amsl.com (Postfix) with ESMTP id 5E80F1A92EA for <imapext@ietf.org>; Sat, 27 Jun 2015 15:52:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1435445553; d=isode.com; s=selector; i=@isode.com; bh=IF3FZZubbHm6NFwdtnAOWXqu0b/9Bi/MO5J6dAkQzZc=; 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=OaxasLNe1HcX9sF621Ck7imSH3SHWJX5wcx9rci+lS9KSfa/rcewhQ1JcV75hJ8UUvLbcL lml3j0mBhOJE+9ZUZFMex1YZ59DWvMTi5hwok0f+/l41lmfuXMC34COhM4VSuKXqaUGExQ yLKNHrHOI/Q7cVs+w1Nk2hJ8TnhEP+U=;
Received: from [192.168.0.6] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <VY8pMAA3=0bQ@waldorf.isode.com>; Sat, 27 Jun 2015 23:52:32 +0100
X-SMTP-Protocol-Errors: PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (12F69)
In-Reply-To: <6.2.5.6.2.20150626144931.0f2aed80@elandnews.com>
Date: Sat, 27 Jun 2015 23:54:33 +0100
Message-Id: <F0F59580-61F5-4F5D-B00F-5B27B6A4BAA6@isode.com>
References: <6.2.5.6.2.20150626144931.0f2aed80@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/G8t9Dr7q41Ysd51I_dDe6htPHTM>
Cc: "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] imapapdb milestones
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 27 Jun 2015 22:52:35 -0000

Hi SM,
May I suggest:

> On 26 Jun 2015, at 23:20, S Moonesamy <sm+ietf@elandsys.com> wrote:
>=20
> Hello,
>=20
> The Working Group Charter for IMAP APPEND Extensions (imapapnd) is at http=
s://datatracker.ietf.org/wg/imapapnd/charter/  The working group has to deli=
ver two Standards Track specifications to the IESG.  The first step is set t=
he milestones for the draft-jayantheesh-imap-appendlimit-extension

I think August 2015 should be reasonable, as the document is pretty much rea=
dy for WGLC already.

> and draft-melnikov-rfc2088bis.

September 2015, unless people think it is too aggressive. i would really lik=
e to take this off my plate ASAP.

> Could the working group participants please suggest a date for each of the=
 two drafts?  I would like to have the milestones settled by 30 June so that=
 the working group can proceed with the technical discussions about the two d=
rafts.
>=20
> If you have any questions about the work of the working group please feel f=
ree to raise them on the mailing list [1].  You can also email me if you fin=
d that easier.
>=20
> Regards,
> S. Moonesamy (as imapapdb WG Chair)
>=20
> 1. https://www.ietf.org/mailman/listinfo/imapext

