draft-ietf-dhc-unused-optioncodes-02.txt		draft-ietf-dhc-unused-optioncodes-03.txt
	Network Working Group R. Droms		Network Working Group R. Droms
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Expires: October 15, 2003 April 16, 2003		Expires: December 6, 2003 June 7, 2003
	Unused DHCP Option Codes		Unused DHCP Option Codes
	draft-ietf-dhc-unused-optioncodes-02		draft-ietf-dhc-unused-optioncodes-03
	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 groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 31		skipping to change at page 1, line 31
	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 October 15, 2003.		This Internet-Draft will expire on December 6, 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
	skipping to change at page 2, line 20		skipping to change at page 2, line 20
	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		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)
	skipping to change at page 2, line 44		skipping to change at page 2, line 44
	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		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		Contact: Ralph Droms
	Reason to recover: Never published as standard		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)
	skipping to change at page 4, line 15		skipping to change at page 4, line 15
	2.8 IPv6 Transition		2.8 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		Contact: Dan Harrington
	Reason to recover: Never published as standard		Reason to recover: Never published as standard and not in general use
	2.9 Printer Name		2.9 Printer Name
	Code: 100		Code: 100
	Name: Printer Name		Name: Printer Name
	Defined in: (none)		Defined in: (none)
	Contact: (none)		Contact: (none)
	skipping to change at page 4, line 39		skipping to change at page 4, line 39
	2.10 Multicast Assignment through DHCP		2.10 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		Reason to recover: Never published as standard and not in general use
	2.11 Swap Path		2.11 Swap Path
	Code: 108		Code: 108
	Name: Swap Path		Name: Swap Path
	Defined in: (none)		Defined in: (none)
	Contact: (none)		Contact: (none)
	skipping to change at page 6, line 14		skipping to change at page 6, line 14
	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 used in PXE Specification		3. 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, none of		Environment (PXE) Specification, Version 2.1" [4]. However, although
			these options are in widespread use by devices that use PXE, none of
	these option codes have been specified as a Standards-track RFC.		these option codes have been specified as a Standards-track RFC.
			The dhc WG will endeavor to have specifications for these options
			published.
	3.1 Client System		3.1 Client System
	Code: 93		Code: 93
	Name: Client System		Name: Client System
	Defined in: (none)		Defined in: (none)
	Contact: (none)		Contact: (none)
	Reason to recover: Never published as Internet-Draft
	3.2 Client NDI		3.2 Client NDI
	Code: 94		Code: 94
	Name: Client NDI		Name: Client NDI
	Defined in: (none)		Defined in: (none)
	Contact: (none)		Contact: (none)
	Reason to recover: Never published as Internet-Draft
	3.3 UUID/GUID Client Identifier		3.3 UUID/GUID Client Identifier
	Code: 97		Code: 97
	Name: UUID/GUID Client Identifier		Name: UUID/GUID Client Identifier
	Defined in: (expired Internet-Draft)		Defined in: (expired Internet-Draft)
	Contact: Dan Harrington		Contact: Dan Harrington
	Reason to recover: Never published as standard
	4. Option Code Extensions		4. Option Code Extensions
	Note that these option codes are identified in draft-volz-dhc-		Note that these option codes are identified in draft-volz-dhc-
	extended-optioncodes-00 [6] as part of a mechanism for extending the		extended-optioncodes-00 [5] as part of a mechanism for extending the
	set of option codes available to DHCP. If these option codes are not		set of option codes available to DHCP. If these option codes are not
	used for DHCP option code extension, they will be returned to IANA		used for DHCP option code extension, they will be returned to IANA
	for reassignment to other DHCP options.		for 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		Reason to recover: Never published as standard; note that these
	option codes are mentioned as		option codes are mentioned in "Extending DHCP Options Codes" [5].
	5. Already Returned for Reassignment		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		6. 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 [5].		new DHCP options, according to the procedures in RFC 2939 [6].
	References		Normative 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] 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", draft-		G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", draft-
	ietf-dhc-failover-11.txt (work in progress), November 2002.		ietf-dhc-failover-12.txt (work in progress), November 2002.
	[4] Intel Corporation, "Preboot Execution Environment (PXE)		[4] Intel Corporation, , "Preboot Execution Environment (PXE)
	Specification Version 2.1",		Specification Version 2.1",
	http://www.pix.net/software/pxeboot/archive/pxespec.pdf,		http://www.pix.net/software/pxeboot/archive/pxespec.pdf,
	September 1999.		September 1999.
	[5] Droms, R., "Procedures and IANA Guidelines for Definition of New		[5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options
			Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in
			progress), September 2000.
			[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.
	[6] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options Codes",
	draft-volz-dhc-extended-optioncodes-00.txt (work in progress),
	September 2000.
	Author's Address		Author's Address
	Ralph Droms		Ralph Droms
	Cisco Systems		Cisco Systems
	250 Apollo Drive		250 Apollo Drive
	Chelmsford, MA 01824		Chelmsford, MA 01824
	USA		USA
	Phone: +1 978 497 4733		Phone: +1 978 497 4733
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/