RFC - 2939
Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types
| Original: | ftp://ftp.isi.edu/in-notes/rfc2939.txt |
|---|---|
| Authors: | R. Droms [Bucknell University] |
| Date: | September 2000 |
| Category: | Best Current Practice [ BCP-43 ] |
| Obsoletes: | |
|---|---|
| RFC-2489 [BCP 29] |
Procedure for Defining New DHCP Options (Obsoleted by RFC-2939) |
| Referred by: | 11 RFC |
| Refers to: | 5 RFC |
Status
This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract
The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a Transmission Control Protocol/Internet Protocol (TCP/IP) network. Configuration parameters and other control information are carried in tagged data items that are stored in the 'options' field of the DHCP message. The data items themselves are also called "options".
DHCP protocol messages are identified by the 'DHCP Message Type' option (option code 51). Each message type is defined by the data value carried in the 'DHCP Message Type' option.
New DHCP options and message types may be defined after the publication of the DHCP specification to accommodate requirements for conveyance of new configuration parameters or to accommodate new protocol semantics. This document describes the procedure for defining new DHCP options and message types.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry
