draft-ietf-dhc-unused-optioncodes-07.txt		rfc3679.txt
	IPv6 Group R. Droms		Network Working Group R. Droms
	Internet-Draft Cisco Systems		Request for Comments: 3679 Cisco Systems
	Expires: April 2, 2004 October 3, 2003		Category: Informational January 2004
	Unused DHCP Option Codes		Unused Dynamic Host Configuration Protocol (DHCP) Option Codes
	draft-ietf-dhc-unused-optioncodes-07
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This memo provides information for the Internet community. It does
	all provisions of Section 10 of RFC2026.		not specify an Internet standard of any kind. Distribution of this
			memo is unlimited.
	Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that other
	groups may also distribute working documents as Internet-Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at http://
	www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on April 2, 2004.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2003). All Rights Reserved.		Copyright (C) The Internet Society (2004). 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 Dynamic Host
	subsequently never used. This document lists those unused option		Configuration Protocol (DHCP) options that were subsequently never
	codes and directs IANA to make these option codes available for		used. This document lists those unused option codes and directs IANA
	assignment to other DHCP options in the future.		to make these option codes available for assignment to other DHCP
			options in the future.
	The document also lists several option codes that are not currently		The document also lists several option codes that are not currently
	documented in an RFC but should not be made available for		documented in an RFC but should not be made available for
	reassignment to future DHCP options.		reassignment to future DHCP options.
	1. Introduction		1. Introduction
	Section 2 of this document lists the unused DHCP option codes from		Section 2 of this document lists the unused DHCP option codes from
	the IANA list of BOOTP and DHCP option codes [1]. Each option code		the IANA list of BOOTP and DHCP option codes [1]. Each option code
	includes any known documentation and contact information from the		includes any known documentation and contact information from the
	skipping to change at page 2, line 19		skipping to change at page 2, line 5
	Section 3 lists several DHCP option codes that are not currently		Section 3 lists several DHCP option codes that are not currently
	documented in an RFC but should not be made available for		documented in an RFC but should not be made available for
	reassignment to future DHCP options.		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
	Name: Service Location Protocol Naming Authority		Name: Service Location Protocol Naming Authority
	Defined in: (expired Internet-Draft)		Defined in: (expired Internet-Draft)
	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 [2]		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
	Defined in: (expired Internet-Draft)		Defined in: (expired Internet-Draft)
	Contact: Mike Carney		Contact: Mike Carney
	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.4 FQDNs in DHCP Options		2.4. FQDNs in DHCP Options
	Code: 89		Code: 89
	Name: FQDNs in DHCP Options		Name: FQDNs in DHCP Options
	Defined in: (expired Internet-Draft)		Defined in: (expired Internet-Draft)
	Contact: Ralph Droms; agrees that option code should be		Contact: Ralph Droms; agrees that option code should be
	reassigned		reassigned
	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.5 VINES TCP/IP Server		2.5. VINES TCP/IP Server
	Code: 91		Code: 91
	Name: VINES TCP/IP Server		Name: VINES TCP/IP Server
	Defined in: (none)		Defined in: (none)
	Contact: (none)		Contact: (none)
	Reason to recover: Never published as Internet-Draft		Reason to recover: Never published as Internet-Draft
	2.6 Server Selection		2.6. Server Selection
	Code: 92		Code: 92
	Name: Server Selection		Name: Server Selection
	Defined in: (none)		Defined in: (none)
	Contact: (none)		Contact: (none)
	Reason to recover: Never published as Internet-Draft		Reason to recover: Never published as Internet-Draft
	2.7 IPv6 Transition		2.7 IPv6 Transition
	Code: 96		Code: 96
	Name: IPv6 Transition		Name: IPv6 Transition
	Defined in: (expired Internet-Draft)		Defined in: (expired Internet-Draft)
	Contact: Dan Harrington; agrees that option code should be		Contact: Dan Harrington; agrees that option code should be
	reassigned		reassigned
	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.8 Printer Name		2.8. Printer Name
	Code: 100		Code: 100
	Name: Printer Name		Name: Printer Name
	Defined in: (none)		Defined in: (none)
	Contact: (none)		Contact: (none)
	Reason to recover: Never published as Internet-Draft		Reason to recover: Never published as Internet-Draft
	2.9 Multicast Assignment through DHCP		2.9. Multicast Assignment through DHCP
	Code: 101		Code: 101
	Name: Multicast Assignment through DHCP		Name: Multicast Assignment through DHCP
	Defined in: (expired Internet-Draft)		Defined in: (expired Internet-Draft)
	Contact: Baiju Patel, Munil Shah		Contact: Baiju Patel, Munil Shah
	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.10 Swap Path		2.10. Swap Path
	Code: 108		Code: 108
	Name: Swap Path		Name: Swap Path
	Defined in: (none)		Defined in: (none)
	Contact: (none)		Contact: (none)
	Reason to recover: Never published as Internet-Draft		Reason to recover: Never published as Internet-Draft
	2.11 IPX Compatibility		2.11. IPX Compatibility
	Code: 110		Code: 110
	Name: IPX Compatibility		Name: IPX Compatibility
	Defined in: (none)		Defined in: (none)
	Contact: Juan Luciani; agrees 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.12 Failover		2.12. Failover
	Code: 115		Code: 115
	Name: Failover		Name: Failover
	Defined in: Early revisions of "DHCP Failover Protocol" [3]		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 to be reserved by IANA		3. Option codes to be reserved by IANA
	The option codes listed in this section are the subject of ongoing		The option codes listed in this section are the subject of ongoing
	work in the dhc working group. These options codes should remain on		work in the DHC Working Group (WG). These option codes should remain
	the IANA list of assigned option codes [1] until the dhc working		on the IANA list of assigned option codes [1] until the DHC WG has
	group has made a final decision about their disposition.		made a final decision about their disposition.
	3.1 Option codes used in PXE Specification		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" [4]. 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.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" [4]		Specification, Version 2.1" [4]
	Contact: Michael Johnston		Contact: Michael Johnston
	(frenchy@quiet-like-a-panther.org)		(frenchy@quiet-like-a-panther.org)
	3.1.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" [4]		Specification, Version 2.1" [4]
	Contact: Michael Johnston		Contact: Michael Johnston
	(frenchy@quiet-like-a-panther.org)		(frenchy@quiet-like-a-panther.org)
	3.1.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" [4] (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
	(frenchy@quiet-like-a-panther.org)		(frenchy@quiet-like-a-panther.org)
	3.2 In Use by Apple		3.2. In Use by Apple
	The following option codes are used by devices from Apple Computer.		The following option codes are used by devices from Apple Computer.
	However, none of these option codes have been described in a		However, none of these option codes have been described in a
	published RFC.		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.2.1 LDAP Servers		3.2.1. LDAP Servers
	Code: 95		Code: 95
	Name: LDAP Servers		Name: LDAP Servers
	Defined in: (none)		Defined in: (none)
	Contact: Dieter Siegmund, dieter@apple.com		Contact: Dieter Siegmund, dieter@apple.com
	Reason to recover: Never published in an RFC		Reason to recover: Never published in an RFC
	3.2.2 Netinfo Parameters		3.2.2. Netinfo Parameters
	Codes: 112, 113		Codes: 112, 113
	Name: Netinfo Address, Netinfo Tag		Name: Netinfo Address, Netinfo Tag
	Defined in: (none)		Defined in: (none)
	Contact: Dieter Siegmund, dieter@apple.com		Contact: Dieter Siegmund, dieter@apple.com
	Reason to recover: Never published in an RFC		Reason to recover: Never published in an RFC
	3.2.3 URL		3.2.3. URL
	Code: 114		Code: 114
	Name: URL		Name: URL
	Defined in: (none)		Defined in: (none)
	Contact: Dieter Siegmund, dieter@apple.com		Contact: Dieter Siegmund, dieter@apple.com
	Reason to recover: Never published in an RFC		Reason to recover: Never published in an RFC
	3.3 Option Code Extensions		3.3. Option Code Extensions
	Note that these option codes are identified in "Extending DHCP		Note that these option codes are identified in "Extending DHCP
	Options Codes" [5] as part of a mechanism for extending the set of		Options Codes" [5] as part of a mechanism for extending the set of
	option codes available to DHCP. If these option codes are not used		option codes available to DHCP. If these option codes are not used
	for DHCP option code extension, they will be returned to IANA for		for DHCP option code extension, they will be returned to IANA 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
	4. Already Returned for Reassignment		4. 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.
	5. Security Considerations		5. Security Considerations
	This document has no known security implications, as none of the		This document has no known security implications, as none of the
	skipping to change at page 8, line 36		skipping to change at page 6, line 40
	IANA has returned the DHCP option codes listed in Section 2 to the		IANA has returned the DHCP option codes listed in Section 2 to the
	list of available option codes. These option codes may be reassigned		list of available option codes. These option codes may be reassigned
	to new DHCP options, according to the procedures in RFC 2939 [6].		to new DHCP options, according to the procedures in RFC 2939 [6].
	IANA is requested to reassign these option codes after the list of		IANA is requested to reassign these option codes after the list of
	option codes that have never been assigned or have previously been		option codes that have never been assigned or have previously been
	returned has been exhausted.		returned has been exhausted.
	Informative 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
	February 2003.		2003.
	[2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046,		[2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046,
	January 2001.		January 2001.
	[3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil,		[3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil,
	G., Dooley, M. and A. Kapur, "DHCP Failover Protocol",		G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", Work in
	draft-ietf-dhc-failover-12.txt (work in progress), November		Progress.
	2002.
	[4] Intel Corporation, "Preboot Execution Environment (PXE)		[4] Intel Corporation, "Preboot Execution Environment (PXE)
	Specification Version 2.1", http://www.pix.net/software/pxeboot/		Specification Version 2.1", http://www.pix.net/software/pxeboot/
	archive/pxespec.pdf, September 1999.		archive/pxespec.pdf, September 1999.
	[5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options		[5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options
	Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in		Codes", Work in Progress.
	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
	Ralph Droms
	Cisco Systems
	1414 Massachusetts Avenue
	Boxborough, MA 01719
	USA
	Phone: +1 978 936 1674
	EMail: rdroms@cisco.com
	Intellectual Property Statement		Intellectual Property Statement
	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 or other rights that might be claimed to		intellectual property 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; neither does it represent that it		might or might not be available; neither does it represent that it
	has made any effort to identify any such rights. Information on the		has made any effort to identify any such rights. Information on the
	IETF's procedures with respect to rights in standards-track and		IETF's procedures with respect to rights in standards-track and
	standards-related documentation can be found in BCP-11. Copies of		standards-related documentation can be found in BCP-11. Copies of
	skipping to change at page 10, line 27		skipping to change at page 7, line 34
	obtain a general license or permission for the use of such		obtain a general license or permission for the use of such
	proprietary rights by implementors or users of this specification can		proprietary rights by implementors or users of this specification can
	be obtained from the IETF Secretariat.		be obtained from the IETF Secretariat.
	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 which may cover technology that may be required to practice		rights which may cover technology that may be required to practice
	this standard. Please address the information to the IETF Executive		this standard. Please address the information to the IETF Executive
	Director.		Director.
			Author's Address
			Ralph Droms
			Cisco Systems
			1414 Massachusetts Avenue
			Boxborough, MA 01719
			USA
			Phone: +1 978 936 1674
			EMail: rdroms@cisco.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The Internet Society (2003). All Rights Reserved.		Copyright (C) The Internet Society (2004). 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
	skipping to change at page 11, line 7		skipping to change at page 8, line 33
	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 assignees.		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.
	Acknowledgment		Acknowledgement
	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.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/