Re: [imapext] Ben Campbell's No Objection on draft-ietf-imapapnd-appendlimit-extension-08: (with COMMENT)

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 07 January 2016 17:12 UTC

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 08E1D1A90D7; Thu, 7 Jan 2016 09:12:39 -0800 (PST)
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 8R8Z5fbrHPMe; Thu, 7 Jan 2016 09:12:38 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id D9E8D1A90CE; Thu, 7 Jan 2016 09:12:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1452186757; d=isode.com; s=selector; i=@isode.com; bh=lkGwBYapO4GJUODHowrnYcOWulU8sI5r4SZwMGedsE0=; 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=hDFSVw8dDIEy90jJi/n8ygdOlNjpGAWg4KKvCwvIn2en37zAAmEULCntwJx3vVkKKfG17i guvF1x+PBm8mIpiEpY/CoY7BRXcZlkuWPR4GfLB1mpSl7SDSBlXWl12xuCztkn9rVyzmNT j+jTz8G1Uqze0ZxAIUcCwcXjRFTFvx0=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <Vo6chAAbMATm@waldorf.isode.com>; Thu, 7 Jan 2016 17:12:37 +0000
To: S Moonesamy <sm+ietf@elandsys.com>, Jayantheesh S B <j.sb@sea.samsung.com>, Narendra Singh Bisht <narendrasingh.bisht@gmail.com>
References: <20160106231543.12304.75202.idtracker@ietfa.amsl.com> <6.2.5.6.2.20160106152957.0d8df630@elandnews.com> <de1772f169794b96830ad66de9555779@SEAMBX01.sea.samsung.com> <6.2.5.6.2.20160107081246.0dc27430@elandnews.com> <32e9302978e64b1b84ed10dbe68a68d4@SEAMBX01.sea.samsung.com> <6.2.5.6.2.20160107083115.0e98f568@elandnews.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <568E9C6B.8060003@isode.com>
Date: Thu, 07 Jan 2016 17:12:11 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
In-Reply-To: <6.2.5.6.2.20160107083115.0e98f568@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/i9wAUyFVPyAgAM1YjhssK1Xtl5Q>
Cc: draft-ietf-imapapnd-appendlimit-extension@ietf.org, imapext@ietf.org, imapapnd-chairs@ietf.org
Subject: Re: [imapext] Ben Campbell's No Objection on draft-ietf-imapapnd-appendlimit-extension-08: (with COMMENT)
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: Thu, 07 Jan 2016 17:12:39 -0000

Hi SM,

On 07/01/2016 17:09, S Moonesamy wrote:
> Hi Jay, Alexey,
>
> At 08:41 07-01-2016, Alexey Melnikov wrote:
>> SHOULD implies that it is possible for the client not to parse one of 
>> the variants in some circumstances. I think not using normative 
>> language is better here (or switch to MUST).
>
> Yes.  I don't think that using normative language is appropriate in 
> that sentence.
>
> At 08:28 07-01-2016, Jayantheesh S B wrote:
>> IMAP client implementing this extension, should be capable to parse 
>> both Mailbox-specific and Global APPENDLIMIT response.
>>
>> IMAP client ignoring one format may result in non-compliance to this 
>> extension. To stress that point we have added RFC 2119 "SHOULD" in 
>> that sentence.
>
> I'll suggest the following text:
>
>   An IMAP client implementing this extension should be able to parse both
>   mailbox-specific and global APPENDLIMIT responses.
+1.