Re: [lemonade] ToDo list for Lemonade Profile Bis

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 12 March 2008 13:05 UTC

Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: ietfarch-lemonade-archive@core3.amsl.com
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB1B728C7DC; Wed, 12 Mar 2008 06:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.781
X-Spam-Level:
X-Spam-Status: No, score=-100.781 tagged_above=-999 required=5 tests=[AWL=-0.344, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RkP3KBd6KM8J; Wed, 12 Mar 2008 06:05:30 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4421F28C7D8; Wed, 12 Mar 2008 06:04:45 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37DF128C78C for <lemonade@core3.amsl.com>; Wed, 12 Mar 2008 06:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AyzDgdns5+V9 for <lemonade@core3.amsl.com>; Wed, 12 Mar 2008 06:04:39 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id E197628C7D6 for <lemonade@ietf.org>; Wed, 12 Mar 2008 06:02:52 -0700 (PDT)
Received: from [130.129.21.224] (dhcp-15e0.ietf71.ietf.org [130.129.21.224]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <R9fT8AAMZiwt@rufus.isode.com>; Wed, 12 Mar 2008 13:00:33 +0000
Message-ID: <47D7C3DF.4010701@isode.com>
Date: Wed, 12 Mar 2008 11:51:59 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Lemonade WG <lemonade@ietf.org>
References: <47BD9C87.50203@isode.com>
In-Reply-To: <47BD9C87.50203@isode.com>
MIME-Version: 1.0
Subject: Re: [lemonade] ToDo list for Lemonade Profile Bis
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Glenn asked me to summarize the conference call discussion we had a 
couple of weeks ago. As all WG related decisions needs to be reviewed on 
the mailing list, if you disagree with any particular suggestion from 
the conference call, please comment on the mailing list.

Alexey Melnikov wrote:

>In preparation for the conference call later today, I am posting my 
>current list of open issues/todos for the Profile Bis document (listed 
>in no particular order of items). I am not going to state my opinion on 
>any of the listed items below, so that people don't get distracted.
>
>1). Decide if Future Release SMTP (RFC 4865) extension should be included.

Don't add to profile bis (*)

>2). Decide if IMAP Sieve (draft-ietf-lemonade-imap-sieve) should be 
>included.

Don't add to profile bis (*).
Issue WGLC soon and publish on Standard Track.

>3). Decide if METADATA-SERVER should be included.
>4). Decide if draft-melnikov-imapext-filters should be included.


3) is only useful with 4). People were split on this issue, so
suggestion to add it to the "maybe" list of features.
Some feedback from OMA and discussion in Philadelphia is needed.

>5). Describe what should happen if a CONVERT URL (which now returns 
>binary data) is used in CATENATE. Does this require a new IMAP 
>capability? Should this be a required extension?

Don't add to profile bis (*).

>6). Decide if URLFETCH=BINARY should be included (CONVERT URLs will 
>depend on it).

Don't add to profile bis (*), as CONVERT URL extension that depends on
URLFETCH=BINARY is not included either.

>7). Define a new IMAP capability for declaring that URLAUTH and CATENATE 
>support PARTIAL IMAP URLs (see RFC 5092)?

"This is such a minor feature that we might as well add it to Profile
Bis." Suggestion to add this to the "maybe" list.

>8). Add a new IMAP Keyword for "this message is pending submission" and 
>[possibly] another one for "this message got submitted".

Consensus to add some text on this to Profile Bis.
Peter Coates has proposed some text on the mailing list.

>9). New IMAP keyword for "has attachment"?

We spent lots of time discussing usability and precise semantics of
this. The group felt that this was not worth doing, especially after
Arnt's discovery that COMPRESS=DEFLATE works really well for FETCH
BODYSTRUCTURE, which contain this information.

>10). Add ability to discover "special" mailboxes like Trash/Junk/Sent 
>Mail/Drafts ?

Some discussion that 8 and 10 are alternative proposals to deal with the
same problem. I don't remember what exactly we've decided on this one.

>11). Should Profile Bis require Sieve AnnotateMore (to read data from 
>per-server annotations, e.g. notification address)?
>12). If Sieve and extensions remain in Lemonade Profile Bis, we need a 
>way to manage Sieve scripts. How should this be done?

We didn't have time to discuss 11 or 12.

>13). Should the document define a way to find number of attachments? 
>Should this be another extension or just an informative text?

Consensus not to do this, due to the decision not to do 9 above.

>14). Should support for IPv6 be mandated for servers?

We didn't have time to discuss this either.

We've also discussed SORT in details. One person objected about its
implementation complexity on the server, but I think rough consensus in
favor of keeping it in Profile Bis was unchanged.

-------------
(*) While many people thought it is useful, the group didn't feel it was
a Lemonade feature. So suggestion not to add it to the Profile Bis.


_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade