Re: [imapext] AD review of draft-ietf-imapapnd-appendlimit-extension-06
Bron Gondwana <brong@fastmail.fm> Wed, 16 December 2015 00:58 UTC
Return-Path: <brong@fastmail.fm>
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 4B70C1A013F for <imapext@ietfa.amsl.com>; Tue, 15 Dec 2015 16:58:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 1YwHSxvE4wdP for <imapext@ietfa.amsl.com>; Tue, 15 Dec 2015 16:58:36 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C79581A010B for <imapext@ietf.org>; Tue, 15 Dec 2015 16:58:36 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 584B920C36 for <imapext@ietf.org>; Tue, 15 Dec 2015 19:58:34 -0500 (EST)
Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Tue, 15 Dec 2015 19:58:34 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=6kZHi4ocvfZtgIXLw+9cP6V1QTs=; b=g7GGX0 JyuNocj0jX9Xd9G15NDcxpkYUOJNNEjiHeFD9v+tYzpT5d1VKuLQIbekKXhlE18b 1v0ADmwUf9KqfWFSQnnfJZaea9x11ewv/jtltbgaQQ33cn3uiEC9vwN5vnC8RsS8 OrasBaKoCKzwqCe4R/4PnhdHZKKlxVPpjy/Wc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=6kZHi4ocvfZtgIX Lw+9cP6V1QTs=; b=aEGm/MVTZcAxs1pouf3UiK2sxoctfAi4JRG+Epevv0TMrnV ZoqXHXQelHlyiUwOm0PcFJZ/pwI3e9mnn2WWYzBT8vhQt3ltlVmWqHzSKfeUtOOO GTG1vfTWC0uyRCVaIzypRPisF3+cZGCZJCNGCR/yFDYm+gXQW3pArOZ8pjuc=
Received: by web2.nyi.internal (Postfix, from userid 99) id 178865400EB; Tue, 15 Dec 2015 19:58:34 -0500 (EST)
Message-Id: <1450227514.484496.468602753.3F5C1248@webmail.messagingengine.com>
X-Sasl-Enc: njdM6WhGKjQ+VdkfEG0qKcl29qb8/6m4yrcAD1/EJEFH 1450227514
From: Bron Gondwana <brong@fastmail.fm>
To: imapext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-5c8c9c89
Date: Wed, 16 Dec 2015 11:58:34 +1100
In-Reply-To: <CALaySJKvgm3meQvF-KC4awR30dMSkWT93-JvS6+JuOj-1jRLjw@mail.gmail.com>
References: <CALaySJLE_6+vbeB-SeMk1VHDAtq2VvS9yKe9dhQ2LTzr4y=oTg@mail.gmail.com> <DEA84B8F15992B4EA87D5CF3D0EC5F98AE4FCFD8@DRTW-EXMB04.telecom.sna.samsung.com> <CALaySJK=5nkmF2K0Vt7mgg2honoX9iYS4yhgu+giDjKyDoR0GQ@mail.gmail.com> <32c2862015984affaa4fc7940e55ae43@SEAMBX01.sea.samsung.com> <002a41b079d94bcc9ef9378bed793858@SEAMBX01.sea.samsung.com> <CALaySJKvgm3meQvF-KC4awR30dMSkWT93-JvS6+JuOj-1jRLjw@mail.gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/FieNVapphTiDuoe9CssC6ToZbsA>
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: Wed, 16 Dec 2015 00:58:38 -0000
On Wed, Dec 16, 2015, at 06:46, Barry Leiba wrote: > > Please find the proposed text for conveying that there no limit for mailboxes. > > > > NEW > > 3. Mailbox specific APPENDLIMIT > > > > IMAP server can have mailbox specific APPENDLIMIT value, which will > > not be advertised as part of CAPABILITY response. The IMAP server can > > publish a huge limit for a mailbox to convey that there is no APPENDLIMIT > > for a mailbox. The following subsections describe the changes to the > > STATUS and LIST commands in support of this situation. > > END > > I am not happy with using "a huge limit", nor any particular number > for this. Sure, the IMAP grammar limits the length of a literal to > "number", which is defined thus in RFC 3501: > > number = 1*DIGIT > ; Unsigned 32-bit integer > ; (0 <= n < 4,294,967,296) > > So, yes, we *could* say (rather than the vague "a huge limit") that > 4294967296 is what you use if you want to say that there's no limit. > But I don't like overloading things that way: this *is* advertising a > limit, rather than saying that there isn't one. > > Why do we think there's anything wrong with using, say, the word > "NONE" (either case-insensitive or case-sensitive; I don't care)? > What's wrong with this?: > > C: t1 STATUS INBOX (APPENDLIMIT) > S: * STATUS INBOX (APPENDLIMIT NONE) > S: t1 OK STATUS completed > If you're going to do that, why not make it (APPENDLIMIT NIL), which already has exactly the meaning that we want? Bron.
- [imapext] AD review of draft-ietf-imapapnd-append… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- [imapext] Referencing RFC 2088 (was: AD review of… S Moonesamy
- Re: [imapext] Referencing RFC 2088 Alexey Melnikov
- Re: [imapext] Referencing RFC 2088 (was: AD revie… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Narendra Bisht
- Re: [imapext] Referencing RFC 2088 S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] Referencing RFC 2088 (was: AD revie… Naren
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Naren
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Naren
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Stu Brandt
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Stu Brandt
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Arnt Gulbrandsen
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Dave Cridland
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Dave Cridland
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Arnt Gulbrandsen
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Bron Gondwana
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Narendra Bisht
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Stu Brandt
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review draft-ietf-imapapnd-appen… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Dave Cridland
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba