Unused Dynamic Host Configuration Protocol (DHCP) Option Codes
RFC 3679
|
| Document |
Type |
|
RFC - Informational
(January 2004; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 3679 (Informational)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Margaret Wasserman
|
|
IESG note |
|
Already approved by IESG, pulled back to remove option codes that were actually in use. Back again for re-approval.
|
|
Send notices to |
|
(None)
|
Network Working Group R. Droms
Request for Comments: 3679 Cisco Systems
Category: Informational January 2004
Unused Dynamic Host Configuration Protocol (DHCP) Option Codes
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
Prior to the publication of RFC 2489 (which was updated by RFC 2939),
several option codes were assigned to proposed Dynamic Host
Configuration Protocol (DHCP) options that were subsequently never
used. This document lists those unused option codes and directs IANA
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
documented in an RFC but should not be made available for
reassignment to future DHCP options.
1. Introduction
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
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
The option codes listed in this section are to be returned to IANA
for reassignment to new options. Responses from associated contact
persons are noted where they have been received.
Droms Informational [Page 1]
RFC 3679 Unused DHCP Option Codes January 2004
2.1. Service Location Protocol Naming Authority
Code: 80
Name: Service Location Protocol Naming Authority
Defined in: (expired Internet-Draft)
Contact: Charlie Perkins
Reason to recover: Never published as standard and not in general use
2.2. Relay Agent Options
Codes: 83, 84
Name: Relay Agent Options
Defined in: Early draft of RFC 3046 [2]
Contact: (none)
Reason to recover: Not defined in RFC 3046 as published
2.3. IEEE 1003.1 POSIX Timezone
Code: 88
Name: IEEE 1003.1 POSIX Timezone
Defined in: (expired Internet-Draft)
Contact: Mike Carney
Reason to recover: Never published as standard and not in general use
2.4. FQDNs in DHCP Options
Code: 89
Name: FQDNs in DHCP Options
Defined in: (expired Internet-Draft)
Contact: Ralph Droms; agrees that option code should be
reassigned
Reason to recover: Never published as standard and not in general use
2.5. VINES TCP/IP Server
Code: 91
Name: VINES TCP/IP Server
Defined in: (none)
Contact: (none)
Reason to recover: Never published as Internet-Draft
2.6. Server Selection
Code: 92
Name: Server Selection
Defined in: (none)
Contact: (none)
Reason to recover: Never published as Internet-Draft
Droms Informational [Page 2]
RFC 3679 Unused DHCP Option Codes January 2004
2.7 IPv6 Transition
Code: 96
Name: IPv6 Transition
Defined in: (expired Internet-Draft)
Contact: Dan Harrington; agrees that option code should be
reassigned
Reason to recover: Never published as standard and not in general use
2.8. Printer Name
Code: 100
Name: Printer Name
Defined in: (none)
Contact: (none)
Reason to recover: Never published as Internet-Draft
2.9. Multicast Assignment through DHCP
Code: 101
Name: Multicast Assignment through DHCP
Defined in: (expired Internet-Draft)
Contact: Baiju Patel, Munil Shah
Reason to recover: Never published as standard and not in general use
2.10. Swap Path
Show full document text