draft-ietf-dhc-pxelinux-00.txt   draft-ietf-dhc-pxelinux-01.txt 
Dynamic Host Configuration Working D. Hankins Dynamic Host Configuration Working D. Hankins
Group ISC Group ISC
Expires: November 2, 2006 Intended status: Informational
Expires: October 20, 2007
PXELINUX Use of 'Site Local' Option Space PXELINUX Use of 'Site Local' Option Space
draft-ietf-dhc-pxelinux-00 draft-ietf-dhc-pxelinux-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 2, 2006. This Internet-Draft will expire on October 20, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document is in response to RFC3942 [1], and describes the use by This document is in response to RFC3942 [4], and describes the use by
PXELINUX of some DHCP Option Codes [2] numbering from 208-211. These PXELINUX of some DHCP Option Codes [1] numbering from 208-211. These
codes were designated 'Site Local' [3] prior to this action, and are codes were designated 'Site Local' [2] prior to this action, and are
redefined by RFC3942 as available for allocation as standard DHCP redefined by RFC3942 as available for allocation as standard DHCP
Options. Options.
Table of Contents Table of Contents
1. PXELINUX in a Nutshell . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. MAGIC Option . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. MAGIC Option . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Description . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Description . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 4
3.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 3.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 5
3.4. Response to RFC3942 . . . . . . . . . . . . . . . . . . . 5 3.4. Response to RFC3942 . . . . . . . . . . . . . . . . . . . 5
4. Configuration File Option . . . . . . . . . . . . . . . . . . 5 4. Configuration File Option . . . . . . . . . . . . . . . . . . 5
4.1. Description . . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Description . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 5
4.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 5 4.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 6
4.4. Response to RFC3942 . . . . . . . . . . . . . . . . . . . 6 4.4. Response to RFC3942 . . . . . . . . . . . . . . . . . . . 6
4.5. Client and Server Behaviour . . . . . . . . . . . . . . . 6 4.5. Client and Server Behaviour . . . . . . . . . . . . . . . 6
5. Path Prefix Option . . . . . . . . . . . . . . . . . . . . . . 6 5. Path Prefix Option . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Description . . . . . . . . . . . . . . . . . . . . . . . 6 5.1. Description . . . . . . . . . . . . . . . . . . . . . . . 6
5.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 7
5.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 7 5.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 7
5.4. Response to RFC3942 . . . . . . . . . . . . . . . . . . . 7 5.4. Response to RFC3942 . . . . . . . . . . . . . . . . . . . 8
5.5. Client and Server Behaviour . . . . . . . . . . . . . . . 8 5.5. Client and Server Behaviour . . . . . . . . . . . . . . . 8
6. Option 211 - Reboot Time . . . . . . . . . . . . . . . . . . . 8 6. Option 211 - Reboot Time . . . . . . . . . . . . . . . . . . . 8
6.1. Description . . . . . . . . . . . . . . . . . . . . . . . 8 6.1. Description . . . . . . . . . . . . . . . . . . . . . . . 8
6.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 9 6.2. Packet Format . . . . . . . . . . . . . . . . . . . . . . 9
6.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 9 6.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 9
6.4. Response to RFC3942 . . . . . . . . . . . . . . . . . . . 9 6.4. Response to RFC3942 . . . . . . . . . . . . . . . . . . . 9
6.5. Client and Server Behaviour . . . . . . . . . . . . . . . 9 6.5. Client and Server Behaviour . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Normative References . . . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . . . . . 13 Intellectual Property and Copyright Statements . . . . . . . . . . 13
1. PXELINUX in a Nutshell 1. Introduction
PXE, the Preboot eXecution Environment, is a first-stage network PXE, the Preboot eXecution Environment, is a first-stage network
bootstrap agent. PXE is loaded out of firmware on the client host, bootstrap agent. PXE is loaded out of firmware on the client host,
and performs DHCP queries to obtain an IP Address. and performs DHCP queries to obtain an IP Address.
Once on the network, it loads a second-stage bootstrap agent as Once on the network, it loads a second-stage bootstrap agent as
configured by DHCP header and option contents. configured by DHCP header and option contents.
PXELINUX is one such second-stage bootstrap agent. Once PXE has PXELINUX is one such second-stage bootstrap agent. Once PXE has
passed execution to it, PXELINUX seeks its configuration from a cache passed execution to it, PXELINUX seeks its configuration from a cache
of DHCP Options supplied to the PXE first-stage agent, and then takes of DHCP Options supplied to the PXE first-stage agent, and then takes
action based upon those options. action based upon those options.
Most frequently, this implies loading via TFTP [4] one or more images Most frequently, this implies loading via TFTP [5] one or more images
which are decompressed into memory and executed to pass execution to which are decompressed into memory and executed to pass execution to
the final Host Operating System. the final Host Operating System.
PXELINUX uses DHCP Options 208-211 to govern parts of this bootstrap PXELINUX uses DHCP Options 208-211 to govern parts of this bootstrap
process, but these options are not requested by the PXE DHCP Client process, but these options are not requested by the PXE DHCP Client
at the time it acquires its lease...at that time, the PXE bootloader at the time it acquires its lease...at that time, the PXE bootloader
has no knowledge that PXELINUX is going to be in use, and even so has no knowledge that PXELINUX is going to be in use, and even so
would have no way to know what option(s) PXELINUX might digest. would have no way to know what option(s) PXELINUX might digest.
Local installations that serve this PXELINUX image to its clients Local installations that serve this PXELINUX image to its clients
must also configure their DHCP Servers to provide these options even must also configure their DHCP Servers to provide these options even
skipping to change at page 4, line 20 skipping to change at page 4, line 23
o "second-stage bootloader" - This describes a program loaded by the o "second-stage bootloader" - This describes a program loaded by the
first-stage bootloader at the behest of the DHCP Server. first-stage bootloader at the behest of the DHCP Server.
o "bootloader" and "network bootstrap agent" - These are synonyms, o "bootloader" and "network bootstrap agent" - These are synonyms,
excepting that "bootloader" is intentionally vague in that its excepting that "bootloader" is intentionally vague in that its
next form of bootstrapping may not in fact involve network next form of bootstrapping may not in fact involve network
resources. resources.
The key words "MAY", "MUST", "MUST NOT", "SHOULD", and "SHOULD NOT" The key words "MAY", "MUST", "MUST NOT", "SHOULD", and "SHOULD NOT"
in this document are to be interpreted as described in RFC2119 [5]. in this document are to be interpreted as described in RFC2119 [3].
3. MAGIC Option 3. MAGIC Option
3.1. Description 3.1. Description
If this option is provided to the PXE bootloader, then the value is If this option is provided to the PXE bootloader, then the value is
checked by PXELINUX to match the octet string f1:00:74:7e. If this checked by PXELINUX to match the octet string f1:00:74:7e. If this
matches, then PXELINUX bootloaders will also consume options 209-211, matches, then PXELINUX bootloaders will also consume options 209-211,
as described below. Otherwise, they are ignored. as described below. Otherwise, they are ignored.
skipping to change at page 11, line 34 skipping to change at page 11, line 38
9. Acknowledgements 9. Acknowledgements
These options were designed and implemented for the PXELINUX project These options were designed and implemented for the PXELINUX project
by H. Peter Anvin, and he was instrumental in producing this by H. Peter Anvin, and he was instrumental in producing this
document. Shane Kerr has also provided feedback which has improved document. Shane Kerr has also provided feedback which has improved
this document. this document.
10. References 10. References
[1] Volz, B., "Reclassifying Dynamic Host Configuration Protocol 10.1. Normative References
version 4 (DHCPv4) Options", RFC 3942, November 2004.
[2] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, [1] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
March 1997. March 1997.
[3] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor [2] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC 2132, March 1997. Extensions", RFC 2132, March 1997.
[4] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
July 1992.
[5] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
10.2. Informative References
[4] Volz, B., "Reclassifying Dynamic Host Configuration Protocol
version 4 (DHCPv4) Options", RFC 3942, November 2004.
[5] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350,
July 1992.
Author's Address Author's Address
David W. Hankins David W. Hankins
Internet Systems Consortium, Inc. Internet Systems Consortium, Inc.
950 Charter Street 950 Charter Street
Redwood City, CA 94063 Redwood City, CA 94063
US US
Phone: +1 650 423 1307 Phone: +1 650 423 1307
Email: David_Hankins@isc.org Email: David_Hankins@isc.org
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 13, line 29 skipping to change at page 13, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 21 change blocks. 
40 lines changed or deleted 47 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/