Re: A mailing list protocol

John C Klensin <john-ietf@jck.com> Sun, 09 December 2012 21:17 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 307A921F8CF8 for <ietf@ietfa.amsl.com>; Sun, 9 Dec 2012 13:17:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihAD2iEfLZxt for <ietf@ietfa.amsl.com>; Sun, 9 Dec 2012 13:17:17 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9515A21F8981 for <ietf@ietf.org>; Sun, 9 Dec 2012 13:17:17 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ThoFQ-000BXS-Or; Sun, 09 Dec 2012 16:17:16 -0500
Date: Sun, 09 Dec 2012 16:17:11 -0500
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: A mailing list protocol
Message-ID: <B7B7CE09B650295D27AA1203@JcK-HP8200.jck.com>
In-Reply-To: <50C4F73A.1050707@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <20121206212400.10366.qmail@joyce.lan> <6.2.5.6.2.20121209105838.09574c88@resistor.net> <50C4F73A.1050707@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Dec 2012 21:17:18 -0000

--On Sunday, December 09, 2012 11:40 -0900 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 12/9/12 10:43 AM, S Moonesamy wrote:
>> I would like to ask you to pick the three points from Section
>> 2 (
>> http://tools.ietf.org/html/draft-moonesamy-mail-list-protocol
>> -00 ) which you consider as helpful to facilitate mailing
>> list discussion and send them to me off-list.  I'll post a
>> summary to this mailing list after a week.
> 
> I'm increasingly not a fan of process documents.  It may be
> the case that we need a process document addressing the
> problem of excessive process documents.  I hope that where
> your efforts end up is a wiki page or some such, which I think
> would be helpful, rather than an RFC, which I think would not.

+1 and an observation:  

I think there is a simple test as to when a process document is
actually necessary.  If the nature of the relevant process is
such that one wants a violation to constitute an appeal-able or
recall-able event and believes that the problem created by a
violation is serious appeal or recall should probably succeed,
then getting formal consensus and generating a BCP RFC is
probably justified.  For anything that constitutes general
guidance (as in this case) or is a statement about how some
entity intends to do things until their change their minds
again, "wiki page or some such" should be perfectly adequate and
less likely to waste community time on splitting hairs, picking
nits, and other not-very-productive activities.

Note that the above is consistent with the recent decision(s)
about the Tao: informative document, general guidance, but not
something that contains rule whose violation can be appealed,
hence a web page and some guidance about how it will be
maintained, not a series of RFCs.

    john