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 16:41 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 B93311A90AA; Thu, 7 Jan 2016 08:41:33 -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 lAGHw33Tygeb; Thu, 7 Jan 2016 08:41:32 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 502DB1A90AC; Thu, 7 Jan 2016 08:41:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1452184891; d=isode.com; s=selector; i=@isode.com; bh=VyUBwcPk1UZQVYRHH/ta7gmRJk34Rnhhrm+yUemHdf8=; 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=DlnQLEQ4g6hZ4EdTd0JJh1+S1oY8hdTPs+yfQmeWDI9/pUaHFX81beKb11Bqqa8R+MXRwl WH2we1bcB3KMKCC7m8dEYiotj9j+s02mPVuYLHs7OYW5YnFSXSngI7DOohPhFuugtIqqOS 7y5ywZ5BcQAVf2icA+xqakjqhp4CODk=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <Vo6VOgBBx0Z3@statler.isode.com>; Thu, 7 Jan 2016 16:41:31 +0000
To: Jayantheesh S B <j.sb@sea.samsung.com>, S Moonesamy <sm+ietf@elandsys.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>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <568E9521.60403@isode.com>
Date: Thu, 07 Jan 2016 16:41:05 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
In-Reply-To: <32e9302978e64b1b84ed10dbe68a68d4@SEAMBX01.sea.samsung.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/w3AklYAeVAyfvz_HH1qi7S9_eas>
Cc: "draft-ietf-imapapnd-appendlimit-extension@ietf.org" <draft-ietf-imapapnd-appendlimit-extension@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, "imapapnd-chairs@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 16:41:33 -0000

On 07/01/2016 16:28, Jayantheesh S B wrote:
> Dear SM,
>
> 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.
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).
> Regards,
> Jay
> -----Original Message-----
> From: S Moonesamy [mailto:sm+ietf@elandsys.com]
> Sent: Thursday, January 07, 2016 11:15 AM
> To: Jayantheesh S B; Narendra Singh Bisht
> 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)
>
> Hi Jay,
> At 08:04 07-01-2016, Jayantheesh S B wrote:
>> Yes, both text refers to the same examples in Section 2.
> Thanks for confirming that.
>
> Why is there a RFC 2119 "SHOULD" in the first sentence of the last paragraph of Section 2?
>
> Regards,
> S. Moonesamy
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext