Re: [dhcwg] AD review of draft-ietf-dhc-unused-optioncodes-03.txt

Thomas Narten <narten@us.ibm.com> Tue, 08 July 2003 18:24 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02969; Tue, 8 Jul 2003 14:24:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zx7E-0002hD-O4; Tue, 08 Jul 2003 14:23:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zx6P-0002gf-Ct for dhcwg@optimus.ietf.org; Tue, 08 Jul 2003 14:22:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02925 for <dhcwg@ietf.org>; Tue, 8 Jul 2003 14:22:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zx6N-0004GY-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 14:22:07 -0400
Received: from e33.co.us.ibm.com ([32.97.110.131]) by ietf-mx with esmtp (Exim 4.12) id 19Zx6L-0004Fx-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 14:22:05 -0400
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e33.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h68ILMkj218806; Tue, 8 Jul 2003 14:21:22 -0400
Received: from rotala.raleigh.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay02.boulder.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h68ILLPw044478; Tue, 8 Jul 2003 12:21:21 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id h68III8k016467; Tue, 8 Jul 2003 14:18:18 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.12.8/8.12.5/Submit) with ESMTP id h68IID0Z016462; Tue, 8 Jul 2003 14:18:18 -0400
Message-Id: <200307081818.h68IID0Z016462@rotala.raleigh.ibm.com>
To: Ralph Droms <rdroms@cisco.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-unused-optioncodes-03.txt
In-Reply-To: Message from rdroms@cisco.com of "Fri, 27 Jun 2003 16:42:42 EDT." <4.3.2.7.2.20030627163720.00ba6290@funnel.cisco.com>
Date: Tue, 08 Jul 2003 14:18:13 -0400
From: Thomas Narten <narten@us.ibm.com>
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

> >A more descriptive title might be better? E.g.:
> >
> >   Reclaiming Unused DHCP Option Codes for Reassignment for Future DHCP
> >   Options.
> >
> >(or something similar)

> OK.

I note that the revised ID stil has the old title. Did you decide to
leave it as is?

> > > Normative References
> >
> >Hmm. Aren't all of the references actually informative? Which ones are
> >critical to *this* document?

To clarify, to me normative means you have to go look at the reference
in order to understand the document being discussed. If the document
is self-contained, it doesn't have to have any normative references.

> I think at least this ref is normative:

>     [1]  Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters",
>          http://www.iana.org/assignments/bootp-dhcp-parameters,
>          February 2003.

I can go either way. One doesn't need to go look at the IANA registry
to understand this document.

> And this ref gives the definition of the PXE options, and should
> be normative:

>     [4]  Intel Corporation, , "Preboot Execution Environment (PXE)
>          Specification Version 2.1",
>          http://www.pix.net/software/pxeboot/archive/pxespec.pdf,
>          September 1999.

But to understand this document, one doesn't have to go read the PXE
document. 

> This ref is arguably normative as it defines a potential use
> for two of the options under review:

>     [5]  Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options
>          Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in
>          progress), September 2000.

Again, I'd argue not critical to understand this document. Another
thing to consider. An ID can't be published as an RFC until all the
normative references are also published. Thus, if the above is
normative, this document needs to wait for the other to be done. I
suspect that is not the intent.

In any case, I've asked that the LC be started.

Thomas

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg