Re: [imapext] I-D Action: draft-ietf-imapapnd-appendlimit-extension-03.txt

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Wed, 07 October 2015 09:57 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
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 262821B2D15 for <imapext@ietfa.amsl.com>; Wed, 7 Oct 2015 02:57:19 -0700 (PDT)
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, RCVD_IN_DNSWL_LOW=-0.7] 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 aenN4E0W1djt for <imapext@ietfa.amsl.com>; Wed, 7 Oct 2015 02:57:17 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 132A81B2D1A for <imapext@ietf.org>; Wed, 7 Oct 2015 02:57:16 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 68D47FA00D1; Wed, 7 Oct 2015 09:57:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1444211834; bh=Bv3Fg7GGartse72Akf2D5MdtNUR3OPSuLAi5RU+Se2U=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TI0e50DUBChxwsX7T3ZbNU+USCQ5Yx5LxQTx3NW3mup8cf8iExV2ItPAJgtipSbtk OrAPleqkrcI4WWXzPXFf+4C02677S61iOTsjwL1XHNP3NU/s11dBAmAnyqYBWeqmDw OE4pgDfAZtDOVM2/IPxu5yMwDhpvqw3W5m9Fj3n4=
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1444211832-3314-3313/11/2; Wed, 7 Oct 2015 09:57:12 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Wed, 07 Oct 2015 10:57:12 +0100
User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Debian GNU/Linux 8.1 (jessie)
Mime-Version: 1.0
Message-Id: <f0e63d2b-ea15-49b7-b323-ae7640769a75@gulbrandsen.priv.no>
In-Reply-To: <6.2.5.6.2.20151007000841.0cc17ed0@resistor.net>
References: <20150911144129.24397.85067.idtracker@ietfa.amsl.com> <89C25BBA-FB25-46A0-9120-5FB65E1F5078@iki.fi> <FEEBF4B6-B27C-4241-B3F7-13A5F553EC34@isode.com> <7a7dd132d5dd4827b4df4d27f13afc37@SEAMBX01.sea.samsung.com> <6.2.5.6.2.20151007000841.0cc17ed0@resistor.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/rOjF_l2NZeqQz9zowwMaNigK8ls>
Subject: Re: [imapext] I-D Action: draft-ietf-imapapnd-appendlimit-extension-03.txt
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, 07 Oct 2015 09:57:19 -0000

S Moonesamy writes:
> Timo sent several comments and also asked a question: "Why 
> implement something that going to be a problem in only some very 
> rare cases?" [1].  It is the sort of question which you could 
> also get during IETF-wide review or during IESG Evaluation.  The 
> draft might or not be the ideal place to have all the answers.  
> It would useful if there is a discussion on the mailing list 
> about the comments (and the question) which Timo sent.

IMO the document should answer this particular question.

Most drafts/RFCs don't; there is a silent assumption that the reader knows 
the problem well before starting to read. That's plausible for the imapext 
subscribers, but less so for random programmers who just follow a link on 
Stack Overflow. And it's particularly bad when an extension helps seldom, 
as in this case.

A document that helps in only a few cases must explain its utility, or else 
it will be pushed down the readers' priority list.

I'm afraid I cannot suggest a good answer to the question, however.

Arnt