[dhcwg] AD review of draft-ietf-dhc-unused-optioncodes-03.txt
Thomas Narten <narten@us.ibm.com> Tue, 24 June 2003 16:06 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21770 for <dhcwg-archive@odin.ietf.org>; Tue, 24 Jun 2003 12:06:07 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5OG5e701821 for dhcwg-archive@odin.ietf.org; Tue, 24 Jun 2003 12:05:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UqIe-0000TI-2O for dhcwg-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 12:05:40 -0400
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 MAA21707 for <dhcwg-web-archive@ietf.org>; Tue, 24 Jun 2003 12:05:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UqI1-0000OH-Qi; Tue, 24 Jun 2003 12:05:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UqHX-0000Mr-Rv for dhcwg@optimus.ietf.org; Tue, 24 Jun 2003 12:04:31 -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 MAA21597 for <dhcwg@ietf.org>; Tue, 24 Jun 2003 12:02:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UqFN-0003ui-00 for dhcwg@ietf.org; Tue, 24 Jun 2003 12:02:17 -0400
Received: from e35.co.us.ibm.com ([32.97.110.133]) by ietf-mx with esmtp (Exim 4.12) id 19UqEx-0003u2-00 for dhcwg@ietf.org; Tue, 24 Jun 2003 12:01:54 -0400
Received: from westrelay01.boulder.ibm.com (westrelay01.boulder.ibm.com [9.17.195.10]) by e35.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h5OG0Uxe269360 for <dhcwg@ietf.org>; Tue, 24 Jun 2003 12:00:30 -0400
Received: from cichlid.adsl.duke.edu (sig-9-65-226-238.mts.ibm.com [9.65.226.238]) by westrelay01.boulder.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h5OG0SGA121540 for <dhcwg@ietf.org>; Tue, 24 Jun 2003 10:00:29 -0600
Received: from cichlid.adsl.duke.edu (narten@localhost) by cichlid.adsl.duke.edu (8.11.6/8.9.3) with ESMTP id h5OFxVK02817 for <dhcwg@ietf.org>; Tue, 24 Jun 2003 11:59:31 -0400
Message-Id: <200306241559.h5OFxVK02817@cichlid.adsl.duke.edu>
To: dhcwg@ietf.org
Date: Tue, 24 Jun 2003 11:59:30 -0400
From: Thomas Narten <narten@us.ibm.com>
Subject: [dhcwg] AD review of draft-ietf-dhc-unused-optioncodes-03.txt
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>
The WG has asked that this document be advanced as an informational RFC. Seems like an IETF Last Call on this document would be appropriate, since the point is (in some sense) to verify that it is OK to reuse the listed options for something else. Right? My comments (all nits, I think). > Unused DHCP Option Codes A more descriptive title might be better? E.g.: Reclaiming Unused DHCP Option Codes for Reassignment for Future DHCP Options. (or something similar) > The following option codes are used in the "Preboot Execution > Environment (PXE) Specification, Version 2.1" [4]. However, although > these options are in widespread use by devices that use PXE, none of > these option codes have been specified as a Standards-track RFC. remove mention of standards track (since this is not required?) I.e., just getting them published as RFCs would be good.. > 3.1 Client System > > Code: 93 > > Name: Client System > > Defined in: (none) Shouldn't you reference the PXE documents here? (ditto for remaining PXE ones). Also, including the contact information in the option description struck me a bit odd. As I was reading this, my first thought was "has this person been contacted, and what did they say?" The document could include an indication of this. > Normative References Hmm. Aren't all of the references actually informative? Which ones are critical to *this* document? Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] AD review of draft-ietf-dhc-unused-option… Thomas Narten
- Re: [dhcwg] AD review of draft-ietf-dhc-unused-op… Ralph Droms
- Re: [dhcwg] AD review of draft-ietf-dhc-unused-op… Ralph Droms
- Re: [dhcwg] AD review of draft-ietf-dhc-unused-op… Thomas Narten
- Re: [dhcwg] AD review of draft-ietf-dhc-unused-op… Ralph Droms
- Re: [dhcwg] AD review of draft-ietf-dhc-unused-op… Thomas Narten
- Re: [dhcwg] AD review of draft-ietf-dhc-unused-op… Robert Elz