DHCP
Click on the red underlined text to get to the source
... 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" [2].
...
... DHCP protocol messages are identified by the 'DHCP Message Type'
option (option code 51). Each message type is defined by the data
...
... option (option code 51). Each message type is defined by the data
value carried in the 'DHCP Message Type' option.
...
...
This document describes the procedure for defining new DHCP options
and message types. The procedure will guarantee that:
...
... IANA acts as a central authority
for assignment of numbers such as DHCP option and message type codes.
The new procedure outlined in this document will provide guidance to
...
... New DHCP option codes ...
... 2131draft [2]. The primary
modification is to the time at which a new DHCP option is assigned an
option number. In the procedure described in this document, the
...
... 2132draft, the option number space for
publicly defined DHCP options (1-127) has almost been exhausted.
Many of the defined option numbers have not been followed up with
...
... DHCP option codes will be assigned by IETF
consensus. New DHCP options will be documented in RFCs approved by
the IESG, and the codes for those options will be assigned at the
...
... Site-specific options codes
(128-254) MUST NOT be defined for use by any publicly distributed
DHCP server, client or relay agent implementations. These option
...
... New DHCP message types ...
...
RFC 2131draft does not specify any mechanism for defining new DHCP message
types. In the future, new DHCP message types will be documented in
...
... 2131draft does not specify any mechanism for defining new DHCP message
types. In the future, new DHCP message types will be documented in
RFCs approved by the IESG, and the codes for these new message types ...
...
The author of a new DHCP option or message type will follow these
steps to obtain approval for the option and publication of the
...
... IETF. If the option or message type is accepted
for inclusion in the DHCP specification, the specification of the
option or message type is published as an RFC. It may be
...
...
5. At the time of publication as an RFC, IANA assigns a DHCP option
code or message type code to the new option or message type ...
...
This document extends the procedures for defining new DHCP options
specified in RFC 2489(-> 2939) [5 ...
... specified in RFC 2489(-> 2939) [5] to include the definition of new DHCP
message types. The language reserving site-specific option codes has
...
... requirement that site-specific
option codes must not be encoded in publicly distributed DHCP
implementations.
...
...
An analysis of security issues is required for all newly defined DHCP
options or message types. The description of security issues in the
...
... message type may
reference the "Security Considerations" section in the DHCP
specification [1]; e.g., (from "NetWare ...
... Potential exposures to attack are discussed in section 7 of the
DHCP protocol specification [RFC 2131draft].
...
... IANA on the procedure
it should follow when assigning option numbers for new DHCP options
or message types. This document updates and replaces those
...
... message types. This document updates and replaces those
instructions. In particular, IANA is requested to assign DHCP option
codes or message type codes only for options or message types ...