IETF Logo Mail Archive

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

Barry Leiba <barryleiba@computer.org> Thu, 17 December 2015 17:32 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 DD7B31B2FE6 for <imapext@ietfa.amsl.com>; Thu, 17 Dec 2015 09:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 wyEdey-SqR7L for <imapext@ietfa.amsl.com>; Thu, 17 Dec 2015 09:32:58 -0800 (PST)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1F511A21A5 for <imapext@ietf.org>; Thu, 17 Dec 2015 09:32:58 -0800 (PST)
Received: by mail-ig0-x230.google.com with SMTP id to18so16521713igc.0 for <imapext@ietf.org>; Thu, 17 Dec 2015 09:32:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=UKa39BVwF9/198lKsCExRfX3TRxfdnANOPHNsUajRgc=; b=uHP17zp6suqUjZUJgjO6RkmZwh7wePZNUzB+MZldqPA5JOX5CqCElm7sVdvu26QHef j6YebepvzDZh63nRepnmnqM7pzGZll7n9eaGBDfaMdP4FkhI1aR426bGkhidEYgbFjbG gcga9KfLH4P021GIyt4ifKDxkO4cTLR5oNYjoraqZqd0GyFpO8vgqgKU3s1yZqB/09z3 FbAWBjQ6DLZnb/tTxCeQw1IYNNlbuL59YTO21oQxFzO41TFGlNbrtxIF/qS0G9y1Wag1 WxajEjiFsCo7jtiYzhSyYWZxqsfHiculYs3dyTBKUyTjzwGKC50CHT8kpZ8kE8DY8DUn e+Hw==
MIME-Version: 1.0
X-Received: by 10.50.138.1 with SMTP id qm1mr5032851igb.90.1450373578210; Thu, 17 Dec 2015 09:32:58 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.181.78 with HTTP; Thu, 17 Dec 2015 09:32:58 -0800 (PST)
In-Reply-To: <6679218db47f443794b1ce28452623eb@SEAMBX07.sea.samsung.com>
References: <emcf7f771e-a84b-4df3-b9ff-06dd5417a655@bodybag> <5A5084CC-6733-45DB-B3D5-4F73285257D0@isode.com> <6679218db47f443794b1ce28452623eb@SEAMBX07.sea.samsung.com>
Date: Thu, 17 Dec 2015 12:32:58 -0500
X-Google-Sender-Auth: XC8NUOyl217vCBi4n0jSACfcnxw
Message-ID: <CAC4RtVDnirH1n1hjtLPpMAEYgBmdYmsQxo3WiXiErEFQYPP8gg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Narendra Bisht <ns.bisht@sea.samsung.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/f2bUGnJkkSY8azNFOqkBzzG0q9k>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, "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:33:00 -0000

> The data type for APPENDLIMIT is NUMBER.

I don't understand that statement: there are no "data types" in IMAP
commands.  There's ABNF.

> 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")

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.

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.

Barry

v2.23.0 | Report a Bug | By Email