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

Ralph Droms <rdroms@cisco.com> Tue, 08 July 2003 18:38 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 OAA03524; Tue, 8 Jul 2003 14:38:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZxLl-00046t-Bu; Tue, 08 Jul 2003 14:38:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZxLZ-00044F-0B for dhcwg@optimus.ietf.org; Tue, 08 Jul 2003 14:37:49 -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 OAA03500 for <dhcwg@ietf.org>; Tue, 8 Jul 2003 14:37:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZxLW-0004SU-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 14:37:46 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19ZxLV-0004SA-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 14:37:45 -0400
Received: from cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 08 Jul 2003 11:39:54 -0700
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h68Ib97F007537; Tue, 8 Jul 2003 11:37:09 -0700 (PDT)
Received: from rdroms-w2k.cisco.com (sjc-vpn4-834.cisco.com [10.21.83.65]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR) with ESMTP id AAM37513; Tue, 8 Jul 2003 14:37:07 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030708143215.0494eb90@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 08 Jul 2003 14:37:05 -0400
To: Thomas Narten <narten@us.ibm.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-unused-optioncodes-03.txt
Cc: dhcwg@ietf.org
In-Reply-To: <200307081818.h68IID0Z016462@rotala.raleigh.ibm.com>
References: <Message from rdroms@cisco.com of "Fri, 27 Jun 2003 16:42:42 EDT." <4.3.2.7.2.20030627163720.00ba6290@funnel.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>

At 02:18 PM 7/8/2003 -0400, Thomas Narten wrote:
> > >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?

Nope; I seem to have overlooked changing the title...


> > > > 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.

Well, perhaps I've written this doc to be sufficiently self-contained
to avoid normative references.  Guess I was trying to err in the direction
of assuming minimal background in DHCP on the part of the reader...

> > 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.

"normative references are also published" as an RFC?

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

Thanks...

- Ralph



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