draft-ietf-dhc-unused-optioncodes-04.txt   draft-ietf-dhc-unused-optioncodes-05.txt 
Network Working Group R. Droms IPv6 Group R. Droms
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Expires: December 26, 2003 June 27, 2003 Expires: November 30, 2003 June 2003
Unused DHCP Option Codes Unused DHCP Option Codes
draft-ietf-dhc-unused-optioncodes-04 draft-ietf-dhc-unused-optioncodes-05
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other
other groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-Drafts.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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://
http://www.ietf.org/ietf/1id-abstracts.txt. 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 December 26, 2003. This Internet-Draft will expire on November 30, 2003.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
Prior to the publication of RFC2489 (which was updated by RFC2939), Prior to the publication of RFC2489 (which was updated by RFC2939),
several option codes were assigned to proposed DHCP options that were several option codes were assigned to proposed DHCP options that were
subsequently never used. This document lists those unused option subsequently never used. This document lists those unused option
codes and will be used to confirm that these option codes can be codes and directs IANA to make these option codes available for
reused for other DHCP options in the future. assignment to other DHCP options in the future.
The document also lists several option codes that are not currently
documented in an RFC but should not be made available for
reassignment to future DHCP options.
1. Introduction 1. Introduction
This document lists the unused DHCP option codes from the IANA list Section 2 of this document lists the unused DHCP option codes from
of BOOTP and DHCP option codes [1]. Each option code includes any the IANA list of BOOTP and DHCP option codes [1]. Each option code
known documentation and contact information from the IANA list. includes any known documentation and contact information from the
IANA list. IANA will make these option codes available for
assignment to other DHCP options in the future.
Section 3 lists several DHCP option codes that are not currently
documented in an RFC but should not be made available for
reassignment to future DHCP options.
2. Unused DHCP Option Codes to be Reassigned to Future DHCP Options 2. Unused DHCP Option Codes to be Reassigned to Future DHCP Options
The option codes listed in this section are to be returned to IANA The option codes listed in this section are to be returned to IANA
for reassignment to new options. Responses from associated contact for reassignment to new options. Responses from associated contact
persons are noted where they have been received. persons are noted where they have been received.
2.1 Service Location Protocol Naming Authority 2.1 Service Location Protocol Naming Authority
Code: 80 Code: 80
skipping to change at page 2, line 29 skipping to change at page 2, line 37
Contact: Charlie Perkins Contact: Charlie Perkins
Reason to recover: Never published as standard and not in general use Reason to recover: Never published as standard and not in general use
2.2 Relay Agent Options 2.2 Relay Agent Options
Codes: 83, 84 Codes: 83, 84
Name: Relay Agent Options Name: Relay Agent Options
Defined in: Early draft of RFC3046 [4] Defined in: Early draft of RFC3046 [2]
Contact: (none) Contact: (none)
Reason to recover: Not defined in RFC3046 as published Reason to recover: Not defined in RFC3046 as published
2.3 IEEE 1003.1 POSIX Timezone 2.3 IEEE 1003.1 POSIX Timezone
Code: 88 Code: 88
Name: IEEE 1003.1 POSIX Timezone Name: IEEE 1003.1 POSIX Timezone
skipping to change at page 5, line 25 skipping to change at page 5, line 30
Reason to recover: Never published as Internet-Draft Reason to recover: Never published as Internet-Draft
2.12 IPX Compatibility 2.12 IPX Compatibility
Code: 110 Code: 110
Name: IPX Compatibility Name: IPX Compatibility
Defined in: (none) Defined in: (none)
Contact: Juan Luciani; agress that option code should be Contact: Juan Luciani; agrees that option code should be
reassigned reassigned
Reason to recover: Never published as Internet-Draft Reason to recover: Never published as Internet-Draft
2.13 Netinfo Parameters 2.13 Netinfo Parameters
Codes: 112, 113 Codes: 112, 113
Name: Netinfo Address, Netinfo Tag Name: Netinfo Address, Netinfo Tag
skipping to change at page 6, line 14 skipping to change at page 6, line 23
Contact: Vinod Valloppillil Contact: Vinod Valloppillil
Reason to recover: Never published as Internet-Draft Reason to recover: Never published as Internet-Draft
2.15 Failover 2.15 Failover
Code: 115 Code: 115
Name: Failover Name: Failover
Defined in: Early revisions of "DHCP Failover Protocol" [5] Defined in: Early revisions of "DHCP Failover Protocol" [3]
Contact: Kim Kinnear Contact: Kim Kinnear
Reason to recover: Current version of "DHCP Failover Protocol" does Reason to recover: Current version of "DHCP Failover Protocol" does
not use a DHCP option not use a DHCP option
3. Option codes used in PXE Specification 3. Option codes to be reserved by IANA
The option codes listed in this section are the subject of ongoing
work in the dhc working group. These options codes should remain on
the IANA list of assigned option codes [1] until the dhc working
group has made a final decision about their disposition.
3.1 Option codes used in PXE Specification
The following option codes are used in the "Preboot Execution The following option codes are used in the "Preboot Execution
Environment (PXE) Specification, Version 2.1" [2]. However, although Environment (PXE) Specification, Version 2.1" [4]. However, although
these options are in widespread use by devices that use PXE, none of these options are in widespread use by devices that use PXE, none of
these option codes have been described in a published RFC. these option codes have been described in a published RFC.
The dhc WG will endeavor to have specifications for these options The dhc WG will endeavor to have specifications for these options
published. published.
3.1 Client System 3.1.1 Client System
Code: 93 Code: 93
Name: Client System Name: Client System
Defined in: "Preboot Execution Environment (PXE) Defined in: "Preboot Execution Environment (PXE)
Specification, Version 2.1" [2] Specification, Version 2.1" [4]
Contact: Michael Johnston Contact: Michael Johnston
3.2 Client NDI 3.1.2 Client NDI
Code: 94 Code: 94
Name: Client NDI Name: Client NDI
Defined in: "Preboot Execution Environment (PXE) Defined in: "Preboot Execution Environment (PXE)
Specification, Version 2.1" [2] Specification, Version 2.1" [4]
Contact: Michael Johnston Contact: Michael Johnston
3.3 UUID/GUID Client Identifier 3.1.3 UUID/GUID Client Identifier
Code: 97 Code: 97
Name: UUID/GUID Client Identifier Name: UUID/GUID Client Identifier
Defined in: "Preboot Execution Environment (PXE) Defined in: "Preboot Execution Environment (PXE)
Specification, Version 2.1" [2] (and an expired Internet-Draft) Specification, Version 2.1" [4] (and an expired Internet-Draft)
Contact: Dan Harrington, Michael Johnston Contact: Dan Harrington, Michael Johnston
4. Option Code Extensions 3.2 Option Code Extensions
Note that these option codes are identified in draft-volz-dhc- Note that these option codes are identified in "Extending DHCP
extended-optioncodes-00 [3] as part of a mechanism for extending the Options Codes" [5] as part of a mechanism for extending the set of
set of option codes available to DHCP. If these option codes are not option codes available to DHCP. If these option codes are not used
used for DHCP option code extension, they will be returned to IANA for DHCP option code extension, they will be returned to IANA for
for reassignment to other DHCP options. reassignment to other DHCP options.
Codes: 126, 127 Codes: 126, 127
Name: Option Code Extensions Name: Option Code Extensions
Defined in: (expired Internet-Draft) Defined in: (expired Internet-Draft)
Contact: Ralph Droms Contact: Ralph Droms
Reason to recover: Never published as standard; note that these 4. Already Returned for Reassignment
option codes are mentioned in "Extending DHCP Options Codes" [3].
5. Already Returned for Reassignment
The option codes 99, 102-107, 109 and 111 have already been returned The option codes 99, 102-107, 109 and 111 have already been returned
for reassignment to future DHCP options. for reassignment to future DHCP options.
6. IANA Considerations 5. IANA Considerations
When this document has been published as an Informational RFC, IANA When this document has been published as an Informational RFC, IANA
will be requested to return the unused DHCP option codes to the list will be requested to return the unused DHCP option codes to the list
of available option codes. These option codes may be reassigned to of available option codes. These option codes may be reassigned to
new DHCP options, according to the procedures in RFC 2939 [6]. new DHCP options, according to the procedures in RFC 2939 [6].
Normative References Informative References
[1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", [1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters",
http://www.iana.org/assignments/bootp-dhcp-parameters, http://www.iana.org/assignments/bootp-dhcp-parameters,
February 2003. February 2003.
[2] Intel Corporation, "Preboot Execution Environment (PXE) [2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046,
Specification Version 2.1", January 2001.
http://www.pix.net/software/pxeboot/archive/pxespec.pdf,
September 1999.
[3] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options
Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in
progress), September 2000.
Informative References [3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil,
G., Dooley, M. and A. Kapur, "DHCP Failover Protocol",
draft-ietf-dhc-failover-12.txt (work in progress), November
2002.
[4] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, [4] Intel Corporation, "Preboot Execution Environment (PXE)
January 2001. Specification Version 2.1", http://www.pix.net/software/pxeboot/
archive/pxespec.pdf, September 1999.
[5] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, [5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options
G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", draft- Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in
ietf-dhc-failover-12.txt (work in progress), November 2002. progress), February 2003.
[6] Droms, R., "Procedures and IANA Guidelines for Definition of New [6] Droms, R., "Procedures and IANA Guidelines for Definition of New
DHCP Options and Message Types", BCP 43, RFC 2939, September DHCP Options and Message Types", BCP 43, RFC 2939, September
2000. 2000.
Author's Address Author's Address
Ralph Droms Ralph Droms
Cisco Systems Cisco Systems
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978 936 1674 Phone: +1 978 936 1674
EMail: rdroms@cisco.com EMail: rdroms@cisco.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/