Re: [MORG] [apps-discuss] New draft at MORG: POP3 LIST+ Extension

Mykyta Yevstifeyev <evnikita2@gmail.com> Fri, 04 February 2011 14:38 UTC

Return-Path: <evnikita2@gmail.com>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50E103A6930 for <morg@core3.amsl.com>; Fri, 4 Feb 2011 06:38:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.189
X-Spam-Level:
X-Spam-Status: No, score=-3.189 tagged_above=-999 required=5 tests=[AWL=0.410, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 7fRFCpOLWZAZ for <morg@core3.amsl.com>; Fri, 4 Feb 2011 06:38:41 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 3D3863A68E4 for <morg@ietf.org>; Fri, 4 Feb 2011 06:38:41 -0800 (PST)
Received: by fxm9 with SMTP id 9so2622543fxm.31 for <morg@ietf.org>; Fri, 04 Feb 2011 06:42:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=uEa8N465lqQSNBgeBblaAKMSYRAbzZStKyqjw5TT5Lw=; b=q7cR+ZaI5ubggQfmQ/K3FjHTaGcdJPHLePvSeC9U4r7PofUv5Wwir9GpODioYqqou4 pIHQ50xpiBi5EdSxSRdAlIiFm2l7uazkjLwPfg8HvGKCr3Vbb/xsEIkaz+k/28jdlmMN NB8XfVs1rAKucn2Ylt+b4CIsNBAI/XiMKhW68=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=SnuCC6A0iEmdJ00OOO/4sy+BcAoRzWtU5bmML2A8v0XQC96iPDVcgT23VWtqyjLuaF oWvwkB+puty1XgcDyg+Sq11TJxQcvPBQcUu9dGiRZR39YDRslZBKysGfyp8+KQMmLwcD 1M30QQHjpOUrFoavLHc6nN6g6FHt/XYtncmWw=
Received: by 10.223.123.142 with SMTP id p14mr82963far.56.1296830525820; Fri, 04 Feb 2011 06:42:05 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id 21sm252970fav.41.2011.02.04.06.42.03 (version=SSLv3 cipher=RC4-MD5); Fri, 04 Feb 2011 06:42:04 -0800 (PST)
Message-ID: <4D4C1053.3020106@gmail.com>
Date: Fri, 04 Feb 2011 16:42:27 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: morg@ietf.org, Steffen Lehmann <lehmann@strato-rz.de>
References: <4D4ACA2A.3080401@strato-rz.de>
In-Reply-To: <4D4ACA2A.3080401@strato-rz.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 04 Feb 2011 09:51:06 -0800
Subject: Re: [MORG] [apps-discuss] New draft at MORG: POP3 LIST+ Extension
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 14:38:42 -0000

Hello all,

I'm writing to comment Steffen's draft related to POP3 LIST+ extension.

I would firstly ask whether allowing the LIST+ flags with no limited 
number of chars is acceptable?  So I propose to say that (in Section 3) 
'LIST+ flag MAY contain only 16-32 [?? - as you eant] characters' and 
appropriate changes to Appendix B.  Firstly, IANA just won't be able to 
maintain the registry with possibly endless number of values; moreover, 
aspiration to keep flags as short as possible does nt imply such 
unlimited lengths for them.

What is more, I propose to change the security considerations a bit in 
the following way: "Using LIST extended by LIST+ does not introduce any 
new security issues to it' or 'Using LIST extended by LIST+ is not more 
secure that its separate usage'.  It is not right that it does not raise 
any security issues.

I would also like to notice (I've already sent that to the author) that 
IANA considerations are not clear at all.  Therefore I propose (of 
course, formatted in appropriate way):

> 8. IANA Considerations
>
> 8.1. 'LIST+ Flags' Registry
>
> IANA is asked to create and maintain the 'LIST+ Flags' registry 
> following the guidelines below.
>
> The registry consists of two values: LIST+ flag and Reference.  They 
> are described below.
>
>   LIST+ flag - the text string, whose syntax is defined in Section 3.
>
>   Reference - the reference to the document that described the LIST+ flag.
>
> Initial values are given below; new assignments are to be made 
> following the 'IETF Consensus' policies [RFC 5226 - normative ref] (or 
> other policy, as you want)
>   LIST+ flag        Reference
> +-------------------+-------------+
> | +UIDL              | this doc.   |
>          etc.
>
> 8.2. LIST+ Registration in 'POP3 Capabilities' Registry
>
> IANA is asked a new keyword "LIST+" in the "POP3 Capabilities" 
> registry [reference to the reg.] using the template in Section 2 of 
> this document.
Finally, as editorial proposals: the places of Sections 1.1 and 1.2 
should be exchanged; the same as for sections 2 and 3 - this IMO will 
improve the readability of the document.

All the best,
Mykyta Yevstifeyev

03.02.2011 17:30, Steffen Lehmann wrote:
> Hello,
>
> there is a new draft at
> http://datatracker.ietf.org/doc/draft-lehmann-morg-pop3listplus/
> describing the "POP3 LIST+ Extension".
>
> Although it is related to POP3 instead of IMAP, I have put it into MORG,
> because MORG's goals are fitting best.
>
> Comments and suggestions are solicited.
>
> Steffen
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>