RE: [dhcwg] dhc wg last call on draft-ietf-dhc-pxelinux-01

"Bernie Volz \(volz\)" <volz@cisco.com> Fri, 29 June 2007 21:20 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4NtC-0004Mt-QH; Fri, 29 Jun 2007 17:20:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4NtB-0004Ml-Vk for dhcwg@ietf.org; Fri, 29 Jun 2007 17:20:25 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4NsJ-0001k7-Rx for dhcwg@ietf.org; Fri, 29 Jun 2007 17:20:25 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 29 Jun 2007 17:19:31 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOYThUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,476,1175486400"; d="scan'208"; a="124925662:sNHT40478976"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5TLJVSL004203; Fri, 29 Jun 2007 17:19:31 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TLJT6a016790; Fri, 29 Jun 2007 21:19:29 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jun 2007 17:19:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] dhc wg last call on draft-ietf-dhc-pxelinux-01
Date: Fri, 29 Jun 2007 17:19:28 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104619BF1@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <46823079.5050405@uninett.no>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] dhc wg last call on draft-ietf-dhc-pxelinux-01
Thread-Index: Ace4nzo7p38aIPS3SSaRrGqqpr2ArgB8n2hw
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Stig Venaas <stig.venaas@uninett.no>, dhcwg <dhcwg@ietf.org>, "David W. Hankins" <David_Hankins@isc.org>
X-OriginalArrivalTime: 29 Jun 2007 21:19:28.0939 (UTC) FILETIME=[2D7BB7B0:01C7BA93]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2973; t=1183151971; x=1184015971; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20dhc=20wg=20last=20call=20on=20=20draft-ietf -dhc-pxelinux-01 |Sender:=20 |To:=20=22Stig=20Venaas=22=20<stig.venaas@uninett.no>, =20=22dhcwg=22=20<d hcwg@ietf.org>, =0A=20=20=20=20=20=20=20=20=22David=20W.=20Hankins=22=20<Da vid_Hankins@isc.org>; bh=5QNWTNnfXYZ101hgx/R9RNXxEtQBw1rmVy5/HgjRPPk=; b=ZscICPrawCpSJ21Z3Nn+qtL7fFiEYh/FjwMHB6Vdxn9R7gqrFm2zCO2Mtl7pcdDSqh6tp9Np XSz2wgRFcxcFTRHqQSYoGMvz8BUx4Bbp1aqnwxevu4UuAEQcY+Zn/+HW;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s ig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc:
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: dhcwg-bounces@ietf.org

I fully support this document moving forward.

I suggest that perhaps:

   1.  Move DHCPv4 Option code 208 from 'Tentatively Assigned' to
       'Unassigned, Last Resort'.  It is hoped that Unassigned DHCP
       Option Codes (that had never been Tentatively Assigned) SHOULD be
       allocated prior to assigning this option code, but otherwise
       SHOULD be allocated before any option code that has been
       Tentatively Assigned, or Assigned.

Also might recommend that this option code (even as a last resort) not
be used for a future purpose that could result in the magic value
appearing in the option? Though we'll probably long have forgotten this!

Therefore, I think it makes more sense to just allocate 208 to PXELINUX,
but call it a deprecated option. Then if 10 years from now we're out of
option codes, we could reclaim it. But, if we never need it, no harm
done. I also think this is easier than tagging it as "last resort".

This of course also impacts section 3.4, which would have to be
reworded.

A couple of nits:

1. Rename section 6 to "Reboot Time Option".

   3.  MAGIC Option . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Configuration File Option  . . . . . . . . . . . . . . . . . .  5
   5.  Path Prefix Option . . . . . . . . . . . . . . . . . . . . . .  6
   6.  Option 211 - Reboot Time . . . . . . . . . . . . . . . . . . .  8

2. Perhaps the title should just be "PXELINUX Options"? As 'Site Local'
are now redefined (per RFC 3942) and as this just documents the PXELINUX
usage.

I don't think there would be need to respind this document for any of
these (if adopted) - they can be handled as notes to the RFC-Editor?

- Bernie

-----Original Message-----
From: Stig Venaas [mailto:stig.venaas@uninett.no] 
Sent: Wednesday, June 27, 2007 5:40 AM
To: dhcwg
Subject: [dhcwg] dhc wg last call on draft-ietf-dhc-pxelinux-01

This message announces a dhc wg last call on "PXELINUX Use of 'Site
Local' Option Space" <draft-ietf-dhc-pxelinux-01.txt>.  The last call
will conclude at 1700EDT on Mon, 2007-07-09.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.  Lack of discussion does not
represent positive support.  If there is no expression of support for
acceptance during the WG last call, the document will not be advanced
to the IESG.

draft-ietf-dhc-pxelinux-01 is in response to the process of
reclassifying site-specific options, RFC 3942, and describes the use
by PXELINUX of some DHCP Option Codes numbering from 208-211.  These
codes were designated 'Site Local' prior to this action, and are
redefined by RFC 3942 as available for allocation as standard DHCP
Options.

Stig

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

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