| 1 |
<pre>Network Working Group R. Droms |
| 2 |
Request for Comments: 2939 Bucknell University |
| 3 |
BCP: 43 September 2000 |
| 4 |
Obsoletes: <a href="./rfc2489">2489</a> |
| 5 |
Category: Best Current Practice |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">Procedures and IANA Guidelines for Definition of</span> |
| 9 |
<span class="h1">New DHCP Options and Message Types</span> |
| 10 |
|
| 11 |
Status of this Memo |
| 12 |
|
| 13 |
This document specifies an Internet Best Current Practices for the |
| 14 |
Internet Community, and requests discussion and suggestions for |
| 15 |
improvements. Distribution of this memo is unlimited. |
| 16 |
|
| 17 |
Copyright Notice |
| 18 |
|
| 19 |
Copyright (C) The Internet Society (2000). All Rights Reserved. |
| 20 |
|
| 21 |
Abstract |
| 22 |
|
| 23 |
The Dynamic Host Configuration Protocol (DHCP) provides a framework |
| 24 |
for passing configuration information to hosts on a Transmission |
| 25 |
Control Protocol/Internet Protocol (TCP/IP) network. Configuration |
| 26 |
parameters and other control information are carried in tagged data |
| 27 |
items that are stored in the 'options' field of the DHCP message. |
| 28 |
The data items themselves are also called "options". |
| 29 |
|
| 30 |
DHCP protocol messages are identified by the 'DHCP Message Type' |
| 31 |
option (option code 51). Each message type is defined by the data |
| 32 |
value carried in the 'DHCP Message Type' option. |
| 33 |
|
| 34 |
New DHCP options and message types may be defined after the |
| 35 |
publication of the DHCP specification to accommodate requirements for |
| 36 |
conveyance of new configuration parameters or to accommodate new |
| 37 |
protocol semantics. This document describes the procedure for |
| 38 |
defining new DHCP options and message types. |
| 39 |
|
| 40 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 41 |
|
| 42 |
The Dynamic Host Configuration Protocol (DHCP) [<a href="#ref-1" title=""Dynamic Host Configuration Protocol"">1</a>] provides a |
| 43 |
framework for passing configuration information to hosts on a TCP/IP |
| 44 |
network. Configuration parameters and other control information are |
| 45 |
carried in tagged data items that are stored in the 'options' field |
| 46 |
of the DHCP message. The data items themselves are also called |
| 47 |
"options" [<a href="#ref-2" title=""DHCP Options and BOOTP Vendor Extensions"">2</a>]. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Droms Best Current Practice [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2939">RFC 2939</a> Procedures for New DHCP Options September 2000</span> |
| 55 |
|
| 56 |
|
| 57 |
DHCP protocol messages are identified by the 'DHCP Message Type' |
| 58 |
option (option code 51). Each message type is defined by the data |
| 59 |
value carried in the 'DHCP Message Type' option. |
| 60 |
|
| 61 |
This document describes the procedure for defining new DHCP options |
| 62 |
and message types. The procedure will guarantee that: |
| 63 |
|
| 64 |
* allocation of new option numbers and message type numbers is |
| 65 |
coordinated from a single authority, |
| 66 |
* new options and message types are reviewed for technical |
| 67 |
correctness and appropriateness, and |
| 68 |
* documentation for new options and message types is complete and |
| 69 |
published. |
| 70 |
|
| 71 |
As indicated in, "Guidelines for Writing an IANA Considerations |
| 72 |
Section in RFCs", (see references), IANA acts as a central authority |
| 73 |
for assignment of numbers such as DHCP option and message type codes. |
| 74 |
The new procedure outlined in this document will provide guidance to |
| 75 |
IANA in the assignment of new option and message type codes. |
| 76 |
|
| 77 |
This document updates and replaces <a href="./rfc2489">RFC 2489</a>. |
| 78 |
|
| 79 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview and background</span> |
| 80 |
|
| 81 |
This document specifies procedures for defining new option codes and |
| 82 |
message types. |
| 83 |
|
| 84 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> New DHCP option codes</span> |
| 85 |
|
| 86 |
The procedure described in this document modifies and clarifies the |
| 87 |
procedure for defining new options in <a href="./rfc2131">RFC 2131</a> [<a href="#ref-2" title=""DHCP Options and BOOTP Vendor Extensions"">2</a>]. The primary |
| 88 |
modification is to the time at which a new DHCP option is assigned an |
| 89 |
option number. In the procedure described in this document, the |
| 90 |
option number is not assigned until specification for the option is |
| 91 |
about to be published as an RFC. |
| 92 |
|
| 93 |
Since the publication of <a href="./rfc2132">RFC 2132</a>, the option number space for |
| 94 |
publicly defined DHCP options (1-127) has almost been exhausted. |
| 95 |
Many of the defined option numbers have not been followed up with |
| 96 |
Internet Drafts submitted to the DHC WG. There has been a lack of |
| 97 |
specific guidance to IANA from the DHC WG as to the assignment of |
| 98 |
DHCP option numbers. |
| 99 |
|
| 100 |
The procedure as specified in <a href="./rfc2132">RFC 2132</a> does not clearly state that |
| 101 |
new options are to be reviewed individually for technical |
| 102 |
correctness, appropriateness and complete documentation. <a href="./rfc2132">RFC 2132</a> |
| 103 |
also does not require that new options are to be submitted to the |
| 104 |
IESG for review, and that the author of the option specification is |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Droms Best Current Practice [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2939">RFC 2939</a> Procedures for New DHCP Options September 2000</span> |
| 111 |
|
| 112 |
|
| 113 |
responsible for bringing new options to the attention of the IESG. |
| 114 |
Finally, <a href="./rfc2132">RFC 2132</a> does not make clear that newly defined options are |
| 115 |
not to be incorporated into products, included in other |
| 116 |
specifications or otherwise used until the specification for the |
| 117 |
option is published as an RFC. |
| 118 |
|
| 119 |
In the future, new DHCP option codes will be assigned by IETF |
| 120 |
consensus. New DHCP options will be documented in RFCs approved by |
| 121 |
the IESG, and the codes for those options will be assigned at the |
| 122 |
time the relevant RFCs are published. Typically, the IESG will seek |
| 123 |
input on prospective assignments from appropriate sources (e.g., a |
| 124 |
relevant Working Group if one exists). Groups of related options may |
| 125 |
be combined into a single specification and reviewed as a set by the |
| 126 |
IESG. Prior to assignment of an option code, it is not appropriate |
| 127 |
to incorporate new options into products, include the specification |
| 128 |
in other documents or otherwise make use of the new options. |
| 129 |
|
| 130 |
The DHCP option number space (1-254) is split into two parts. The |
| 131 |
site-specific option codes [<a href="#ref-2" title=""DHCP Options and BOOTP Vendor Extensions"">2</a>] (128-254) are defined as "Private Use" |
| 132 |
and require no review by the DHC WG. Site-specific options codes |
| 133 |
(128-254) MUST NOT be defined for use by any publicly distributed |
| 134 |
DHCP server, client or relay agent implementations. These option |
| 135 |
codes are explicitly reserved for private definition and use within a |
| 136 |
site or an organization. |
| 137 |
|
| 138 |
The public option codes (0-127, 255) are defined as "Specification |
| 139 |
Required" and new options must be reviewed prior to assignment of an |
| 140 |
option number by IANA. The details of the review process are given |
| 141 |
in the following section of this document. |
| 142 |
|
| 143 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> New DHCP message types</span> |
| 144 |
|
| 145 |
<a href="./rfc2131">RFC 2131</a> does not specify any mechanism for defining new DHCP message |
| 146 |
types. In the future, new DHCP message types will be documented in |
| 147 |
RFCs approved by the IESG, and the codes for these new message types |
| 148 |
will be assigned at the time the relevant RFCs are published. |
| 149 |
|
| 150 |
Typically, the IESG will seek input on new message types from |
| 151 |
appropriate sources (e.g., a relevant Working Group if one exists). |
| 152 |
Prior to assignment of a message type code, it is not appropriate to |
| 153 |
incorporate new message types into products, include the |
| 154 |
specification in other documents or otherwise make use of the new |
| 155 |
message types. |
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Droms Best Current Practice [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2939">RFC 2939</a> Procedures for New DHCP Options September 2000</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Procedure</span> |
| 170 |
|
| 171 |
The author of a new DHCP option or message type will follow these |
| 172 |
steps to obtain approval for the option and publication of the |
| 173 |
specification of the option as an RFC: |
| 174 |
|
| 175 |
1. The author devises the new option or message type. |
| 176 |
|
| 177 |
2. The author documents the new option or message type, leaving the |
| 178 |
option code or message type code as "To Be Determined" (TBD), as |
| 179 |
an Internet Draft. |
| 180 |
|
| 181 |
The requirement that the new option or message type be documented |
| 182 |
as an Internet Draft is a matter of expediency. In theory, the |
| 183 |
new option or message type could be documented on the back of an |
| 184 |
envelope for submission; as a practical matter, the specification |
| 185 |
will eventually become an Internet Draft as part of the review |
| 186 |
process. |
| 187 |
|
| 188 |
3. The author submits the Internet Draft for review by the IESG. |
| 189 |
Preferably, the author will submit the Internet Draft to the DHC |
| 190 |
Working Group, but the author may choose to submit the Internet |
| 191 |
Draft directly to the IESG. |
| 192 |
|
| 193 |
Note that simply publishing the new option or message type as an |
| 194 |
Internet Draft does not automatically bring the option to the |
| 195 |
attention of the IESG. The author of the new option or message |
| 196 |
type must explicitly forward a request for action on the new |
| 197 |
option to the DHC WG or the IESG. |
| 198 |
|
| 199 |
4. The specification of the new option or message type is reviewed by |
| 200 |
the IESG. The specification is reviewed by the DHC WG (if it |
| 201 |
exists) or by the IETF. If the option or message type is accepted |
| 202 |
for inclusion in the DHCP specification, the specification of the |
| 203 |
option or message type is published as an RFC. It may be |
| 204 |
published as either a standards-track or a non-standards-track |
| 205 |
RFC. |
| 206 |
|
| 207 |
5. At the time of publication as an RFC, IANA assigns a DHCP option |
| 208 |
code or message type code to the new option or message type. |
| 209 |
|
| 210 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span> |
| 211 |
|
| 212 |
[<a id="ref-1">1</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC 2131</a>, March |
| 213 |
1997. |
| 214 |
|
| 215 |
[<a id="ref-2">2</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor |
| 216 |
Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Droms Best Current Practice [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2939">RFC 2939</a> Procedures for New DHCP Options September 2000</span> |
| 223 |
|
| 224 |
|
| 225 |
[<a id="ref-3">3</a>] Droms, R. and K. Fong, "NetWare/IP Domain Name and Information", |
| 226 |
<a href="./rfc2142">RFC 2142</a>, November 1997. |
| 227 |
|
| 228 |
[<a id="ref-4">4</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA |
| 229 |
Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>, October 1998. |
| 230 |
|
| 231 |
[<a id="ref-5">5</a>] Droms, R., "Procedure for Defining New DHCP Options", <a href="./rfc2489">RFC 2489</a>, |
| 232 |
January 1999. |
| 233 |
|
| 234 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Changes from <a href="./rfc2489">RFC 2489</a></span> |
| 235 |
|
| 236 |
This document extends the procedures for defining new DHCP options |
| 237 |
specified in <a href="./rfc2489">RFC 2489</a> [<a href="#ref-5" title=""Procedure for Defining New DHCP Options"">5</a>] to include the definition of new DHCP |
| 238 |
message types. The language reserving site-specific option codes has |
| 239 |
been strengthened to emphasize the requirement that site-specific |
| 240 |
option codes must not be encoded in publicly distributed DHCP |
| 241 |
implementations. |
| 242 |
|
| 243 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 244 |
|
| 245 |
Information that creates or updates an option code or message type |
| 246 |
code assignment needs to be authenticated. |
| 247 |
|
| 248 |
An analysis of security issues is required for all newly defined DHCP |
| 249 |
options or message types. The description of security issues in the |
| 250 |
specification of new options or message types must be as accurate as |
| 251 |
possible. The specification for a new option or message type may |
| 252 |
reference the "Security Considerations" section in the DHCP |
| 253 |
specification [<a href="#ref-1" title=""Dynamic Host Configuration Protocol"">1</a>]; e.g., (from "NetWare/IP Domain Name and |
| 254 |
Information" [<a href="#ref-3" title=""NetWare/IP Domain Name and Information"">3</a>]): |
| 255 |
|
| 256 |
DHCP currently provides no authentication or security mechanisms. |
| 257 |
Potential exposures to attack are discussed in <a href="#section-7">section 7</a> of the |
| 258 |
DHCP protocol specification [<a href="./rfc2131">RFC 2131</a>]. |
| 259 |
|
| 260 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span> |
| 261 |
|
| 262 |
<a href="./rfc2132">RFC 2132</a> and <a href="./rfc2489">RFC 2489</a> provided guidance to the IANA on the procedure |
| 263 |
it should follow when assigning option numbers for new DHCP options |
| 264 |
or message types. This document updates and replaces those |
| 265 |
instructions. In particular, IANA is requested to assign DHCP option |
| 266 |
codes or message type codes only for options or message types that |
| 267 |
have been approved for publication as RFCs; i.e., documents that have |
| 268 |
been approved through "IETF consensus" as defined in <a href="./rfc2434">RFC 2434</a> [<a href="#ref-4" title="">4</a>]. |
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Droms Best Current Practice [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2939">RFC 2939</a> Procedures for New DHCP Options September 2000</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Author's Address</span> |
| 282 |
|
| 283 |
Ralph Droms |
| 284 |
Computer Science Department |
| 285 |
323 Dana Engineering |
| 286 |
Bucknell University |
| 287 |
Lewisburg, PA 17837 |
| 288 |
|
| 289 |
Phone: (570) 524-1145 |
| 290 |
EMail: [email protected] |
| 291 |
|
| 292 |
|
| 293 |
|
| 294 |
|
| 295 |
|
| 296 |
|
| 297 |
|
| 298 |
|
| 299 |
|
| 300 |
|
| 301 |
|
| 302 |
|
| 303 |
|
| 304 |
|
| 305 |
|
| 306 |
|
| 307 |
|
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Droms Best Current Practice [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2939">RFC 2939</a> Procedures for New DHCP Options September 2000</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Full Copyright Statement</span> |
| 338 |
|
| 339 |
Copyright (C) The Internet Society (2000). All Rights Reserved. |
| 340 |
|
| 341 |
This document and translations of it may be copied and furnished to |
| 342 |
others, and derivative works that comment on or otherwise explain it |
| 343 |
or assist in its implementation may be prepared, copied, published |
| 344 |
and distributed, in whole or in part, without restriction of any |
| 345 |
kind, provided that the above copyright notice and this paragraph are |
| 346 |
included on all such copies and derivative works. However, this |
| 347 |
document itself may not be modified in any way, such as by removing |
| 348 |
the copyright notice or references to the Internet Society or other |
| 349 |
Internet organizations, except as needed for the purpose of |
| 350 |
developing Internet standards in which case the procedures for |
| 351 |
copyrights defined in the Internet Standards process must be |
| 352 |
followed, or as required to translate it into languages other than |
| 353 |
English. |
| 354 |
|
| 355 |
The limited permissions granted above are perpetual and will not be |
| 356 |
revoked by the Internet Society or its successors or assigns. |
| 357 |
|
| 358 |
This document and the information contained herein is provided on an |
| 359 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 360 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 361 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 362 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 363 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 364 |
|
| 365 |
Acknowledgement |
| 366 |
|
| 367 |
Funding for the RFC Editor function is currently provided by the |
| 368 |
Internet Society. |
| 369 |
|
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
Droms Best Current Practice [Page 7] |
| 389 |
</pre> |