Re: [dhcwg] PXELinux.
"David W. Hankins" <David_Hankins@isc.org> Thu, 06 July 2006 17:19 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyXVq-0003MZ-NA; Thu, 06 Jul 2006 13:19:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyXVp-0003MU-2b for dhcwg@ietf.org; Thu, 06 Jul 2006 13:19:37 -0400
Received: from kaboom.isc.org ([2001:4f8:3:bb:250:8dff:fef7:d58c]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyXVo-0006EF-Qr for dhcwg@ietf.org; Thu, 06 Jul 2006 13:19:37 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200) id 59EC84C900; Thu, 6 Jul 2006 10:19:36 -0700 (PDT)
Date: Thu, 06 Jul 2006 10:19:36 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [dhcwg] PXELinux.
Message-ID: <20060706171936.GG4572@isc.org>
References: <20060525190516.GG4047@isc.org> <20060705231427.GG8862@isc.org> <44AC9790.7020300@zytor.com>
Mime-Version: 1.0
In-Reply-To: <44AC9790.7020300@zytor.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: dhcwg@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============2143637773=="
Errors-To: dhcwg-bounces@ietf.org
On Wed, Jul 05, 2006 at 09:54:40PM -0700, H. Peter Anvin wrote: > I just re-read this item, and have a few notes: > > 1. The standard spelling is PXELINUX, all caps. This is for historical > reasons, but has stuck around. I know 'PXE' and I know 'Linux', so I just glued those together. The document name has to be all lowercase, but I've updated my use of the name within the document for consistency. I also found one use of 'PXElinux'. > 2. With regards to option 210: if this is adopted, it needs to be noted > for any new option if it is subject to having option 210 prepended or > not. Option 209 *is* subject to 210. > > 3. There is an additional justification for option 210. It does provide > a method to allow the administrator to let PXELINUX use the standard > discovery algorithm for the configuration file, but in a specific area > of the TFTP server. It's thus, in addition to other things, a "softer" > form of the configuration file search option. Good catch, thanks Peter. I've revved the draft and provided clear language on server and client behaviour expectations, incorporating (I think) these two points. I've also fixed some typos and cleaned up the language about the parameter request list. Once the new rev is up on the i-d database, I'll ask again for that rev to be taken on as a WG item. -- David W. Hankins "If you don't do it right the first time, Software Engineer you'll just have to do it again." Internet Systems Consortium, Inc. -- Jack T. Hankins
_______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] PXELinux. David W. Hankins
- Re: [dhcwg] PXELinux. David W. Hankins
- Re: [dhcwg] PXELinux. H. Peter Anvin
- Re: [dhcwg] PXELinux. David W. Hankins