Document:   draft-ietf-dhc-pxe-options-02.txt
Reviewer: Spencer Dawkins [spencer@mcsr-labs.org]
Review Date:  Saturday 1/14/2006 12:40 AM CST
IESG Telechat Date:  Thursday, 19 January 2006

Summary: Huh?

If I understand the draft and underlying working group mailing list traffic 
correctly, this is being published as an Informational RFC to say that PXE 
(and, for good measure, Etherboot?) are using DHCP options that aren't 
allocated by IANA. Some of the mailing list postings showed previous 
versions of the draft with IANA considerations, but the current version of 
the draft says there are no IANA considerations.

So, the plan is to publish an Informational document that describes this 
practice, but does not tell IANA not to allocate the hijacked option codes 
for some other use? Oh-kay... although 
http://www.iana.org/assignments/bootp-dhcp-parameters shows the option codes 
as already tentatively allocated (one presumes this was based on version 01 
of this draft).

If this is the plan, the document is close to OK for publication, although I 
expect the RFC Editor would expand acronyms, etc. I thought

   As options 128-135 are not officially assigned for PXE use (previous
   to November 2004 they were considered site-specific options, [6]),
   use of these options may conflict with other uses of these options.

was oddly phrased - perhaps the last line should have been something like

   use of these option values for PXE may conflict with other uses of the 
same options on the same networks.