Re: [imapext] AD review of draft-ietf-imapapnd-appendlimit-extension-06

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 17 December 2015 17:57 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 B7C441B3007 for <imapext@ietfa.amsl.com>; Thu, 17 Dec 2015 09:57:00 -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 mrF0d0Mrjft8 for <imapext@ietfa.amsl.com>; Thu, 17 Dec 2015 09:56:59 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 906441B2FF6 for <imapext@ietf.org>; Thu, 17 Dec 2015 09:56:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1450375018; d=isode.com; s=selector; i=@isode.com; bh=paliVnYwhm1KEldYWkb0x8zqgs/nLtq+Wm42Ts+4J9U=; 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=OTsO1rscD+FZe8YQsay77kZcdJ+hV1SaoVQ3MVRtOlg0LGDjKxT7L0356wfvKnqOFxl1Lx WpMYdvvW95UeBGL21pY3fa2aQd5I4sl9m7j0yhracgKm6/A50QsxQHHSXzgEHnKrPPIq31 slGTNuBNsjmN1KKws7fJx8dYLJAyelA=;
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 <VnL3agBBxzKl@statler.isode.com>; Thu, 17 Dec 2015 17:56:58 +0000
To: Barry Leiba <barryleiba@computer.org>, Narendra Bisht <ns.bisht@sea.samsung.com>
References: <emcf7f771e-a84b-4df3-b9ff-06dd5417a655@bodybag> <5A5084CC-6733-45DB-B3D5-4F73285257D0@isode.com> <6679218db47f443794b1ce28452623eb@SEAMBX07.sea.samsung.com> <CAC4RtVDnirH1n1hjtLPpMAEYgBmdYmsQxo3WiXiErEFQYPP8gg@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5672F753.3030709@isode.com>
Date: Thu, 17 Dec 2015 17:56:35 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
In-Reply-To: <CAC4RtVDnirH1n1hjtLPpMAEYgBmdYmsQxo3WiXiErEFQYPP8gg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/uyoJyujj927YjBJvDP3YSoSOegg>
Cc: "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] AD review of draft-ietf-imapapnd-appendlimit-extension-06
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, 17 Dec 2015 17:57:00 -0000

Hi Barry,

On 17/12/2015 17:32, Barry Leiba wrote:
>> The data type for APPENDLIMIT is NUMBER.
> I don't understand that statement: there are no "data types" in IMAP
> commands.  There's ABNF.
ABNF for status responses in RFC 3501 doesn't allow anything other than 
a "number". This inflexibility was fixed in RFC 4466.
>> Will it accommodate a NIL?
> It will if you change the ABNF like this:
>
> OLD
> appendlimit-respcode = "APPENDLIMIT" SP number
>
> NEW
> appendlimit-respcode = "APPENDLIMIT" SP (number / "NIL")
This change is in addition to what I suggested for STATUS.
> END
>
> ...and you'd add text explaining that if there is no limit for a
> particular mailbox, the STATUS APPENDLIMIT response for that mailbox
> is NIL.
+1
> There's no need to allow NIL in appendlimit-cap, because if there's no
> limit you just don't send that item at all.
Agreed.