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

Theodore Tso <tytso@mit.edu> Tue, 08 July 2008 21:35 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 16F3628C331; Tue, 8 Jul 2008 14:35:13 -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 467A428C343; Tue, 8 Jul 2008 14:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 AqBzPpCdy46G; Tue, 8 Jul 2008 14:35:10 -0700 (PDT)
Received: from thunker.thunk.org (www.church-of-our-saviour.org [69.25.196.31]) by core3.amsl.com (Postfix) with ESMTP id 8D52D28C33F; Tue, 8 Jul 2008 14:35:10 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by thunker.thunk.org with local-esmtp (Exim 4.50 #1 (Debian)) id 1KGKpy-0005cK-LK; Tue, 08 Jul 2008 17:35:02 -0400
Received: from tytso by closure.thunk.org with local (Exim 4.69) (envelope-from <tytso@mit.edu>) id 1KGKpy-0002ls-1c; Tue, 08 Jul 2008 17:35:02 -0400
Date: Tue, 08 Jul 2008 17:35:02 -0400
From: Theodore Tso <tytso@mit.edu>
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Call for review of proposed update to ID-Checklist
Message-ID: <20080708213501.GA9957@mit.edu>
References: <20080708184427.5D55F28C0EC@core3.amsl.com> <p06250119c4996f6c1a4a@[75.145.176.242]>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <p06250119c4996f6c1a4a@[75.145.176.242]>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@mit.edu
X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false
Cc: IETF Chair <chair@ietf.org>, 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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Tue, Jul 08, 2008 at 02:27:41PM -0500, Pete Resnick wrote:
> The document says:
>
> "If ABNF is used, you MUST include a normative reference to RFC 4234."
>
> To quote two fine radio personalities here in the states, this one seems 
> "boooooooooogus". Yes, any I-D that uses ABNF must include a normative 
> reference to RFC 4234, but for the IESG to not engage in review until it 
> is in there is silly beyond belief. Make a note to the author that they 
> need the reference and continue consideration.

Stupid question ---- isn't this specific thing something we should
allow the secretariat to fix as part of the RFC publishing process,
and in fact give them instructions to add the reference if they find
it missing?  They do things like fix/update references IIRC, and this
is only a minor step beyond that, and should be well within their
capabilities, I would think.

Sure, we can ask document editors to add the reference to RFC 4234,
and maybe we can even do things like include a reference to RFC 4234
in an RFC template file with a note to remove if the standard ends up
not using ABNF, but there must be a class of things which could be
streamlined to save time on both the document editors, reviewers, and
AD's time.

Regards,

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