Re: Call for review of proposed update to ID-Checklist

Henrik Levkowetz <henrik@levkowetz.com> Mon, 11 August 2008 16:54 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 648CF3A6B58; Mon, 11 Aug 2008 09:54:33 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AA373A6957; Mon, 11 Aug 2008 09:54:32 -0700 (PDT)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ytfTk0stpKdD; Mon, 11 Aug 2008 09:54:31 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 471AF3A6359; Mon, 11 Aug 2008 09:54:28 -0700 (PDT)
Received: from localhost ([127.0.0.1]:52003 helo=chardonnay.local) by merlot.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <henrik@levkowetz.com>) id 1KSaf2-00065J-7d; Mon, 11 Aug 2008 18:54:25 +0200
Message-ID: <48A06EBE.9030505@levkowetz.com>
Date: Mon, 11 Aug 2008 18:54:22 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Call for review of proposed update to ID-Checklist
References: <D78EAB64AF674E24B2199B2C1DBDA1FE@BertLaptop> <489F13F2.3060707@dcrocker.net> <72963A021589CE51C5AFB967@[192.168.1.110]> <489F71B1.80100@levkowetz.com> <9B6E255474F2CDD02B76D19B@[192.168.1.110]> <489FF6A3.5000501@levkowetz.com> <48A04E24.4090306@dcrocker.net>
In-Reply-To: <48A04E24.4090306@dcrocker.net>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: dcrocker@bbiw.net, ietf@ietf.org, iesg@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi Dave,

On 2008-08-11 16:35 Dave Crocker said the following:
> 
> Henrik Levkowetz wrote:
>   > My personal viewpoint is that it would be inappropriate to strictly
>> enforce a limit of 5 authors.  The use of 'should' in section 2.2,
>> item 2 of the current document ('There should not be more than 5
>> authors/editors') seems appropriate given the current RFC Editor
>> policy, and tools-wise this would then be implemented as a note or
>> warning at the most, but should never cause a refusal to accept a draft
>> submission.
> 
> 
> 1. "enforce a limit"  moves a should to a must.

Yes, but nobody is arguing that this should be done...

> 2. The RFC Editor's policy document does not use language that is as strong as a 
> should.
> 
> Hence, the ID Checklist is making a normative statement stronger than the RFC 
> Editor and the proposal for the checker to 'enforce' is even stronger than that.

Repeating myself in a new context:  Umm??

I didn't propose that the checker enforce such a limit, and I'm not aware of
anyone else proposing it, thus I don't understand why you seem to argue against
a proposal nobody seems to have made.  Have I misunderstood what you seem to
be saying immediately above, or have you misunderstood my position?

> By contrast, last sentence suggesting simply printing a notice that there are 
> more authors than preferred captures the RFC Editor policy's statement.

I think you are saying that this makes sense?  If so, I think we're in agreement.


	Henrik
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf