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

S Moonesamy <sm+ietf@elandsys.com> Thu, 07 January 2016 17:10 UTC

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 2136E1A90EE; Thu, 7 Jan 2016 09:10:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] 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 s1b6l8fHp3-t; Thu, 7 Jan 2016 09:10:37 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 306C01A90ED; Thu, 7 Jan 2016 09:10:37 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.208.165]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u07HAIXq025650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Jan 2016 09:10:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1452186632; x=1452273032; bh=Ef4amfKp5pRh4EXmPGR7N+DicUx0BVDKovS/EPJEr3g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=26pHlxCzy5A/qjCwDDf/Nv8NZCKHnyi+Xz2DLwVn0fGusrJ5UVG1hDGpDxYEr8uC9 BechRk+YR7hPnZyzo0WmF9hhGmvTkqLUESTrIkQBhy/aRsn13lLHP6KNhiWAPjQ7O9 YMd+EtMJee+7RaMmt8eqX3N6OT4VnOqSgubfp9p4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1452186632; x=1452273032; i=@elandsys.com; bh=Ef4amfKp5pRh4EXmPGR7N+DicUx0BVDKovS/EPJEr3g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=d6S2tSmAjqmthPmJF7j/8K+3wd5VcsNzBQAjLyeM60I2XmzdQUVM3cMDni1f9k4Nd jujsgdZs1CDdhBNMX6E6QpcXC5OojiRuc4hPOsu4LUTSnpEkkIks09N9EKx0uYrY/k D8uVi41Y+YYLFcbKmzSrHbCdvuFHmS4Lk1wAYJo4=
Message-Id: <6.2.5.6.2.20160107083115.0e98f568@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 07 Jan 2016 09:09:06 -0800
To: Jayantheesh S B <j.sb@sea.samsung.com>, Narendra Singh Bisht <narendrasingh.bisht@gmail.com>, Alexey Melnikov <alexey.melnikov@isode.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <32e9302978e64b1b84ed10dbe68a68d4@SEAMBX01.sea.samsung.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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/RvpexYLrun5xEMaDmuWR1D21x14>
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:10:38 -0000

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.


Regards,
S. Moonesamy (as document shepherd)