| 1 |
<pre>Network Working Group B. Volz |
| 2 |
Request for Comments: 3942 Cisco Systems, Inc. |
| 3 |
Updates: <a href="./rfc2132">2132</a> November 2004 |
| 4 |
Category: Standards Track |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">Reclassifying Dynamic Host Configuration Protocol</span> |
| 8 |
<span class="h1">version 4 (DHCPv4) Options</span> |
| 9 |
|
| 10 |
Status of this Memo |
| 11 |
|
| 12 |
This document specifies an Internet standards track protocol for the |
| 13 |
Internet community, and requests discussion and suggestions for |
| 14 |
improvements. Please refer to the current edition of the "Internet |
| 15 |
Official Protocol Standards" (STD 1) for the standardization state |
| 16 |
and status of this protocol. Distribution of this memo is unlimited. |
| 17 |
|
| 18 |
Copyright Notice |
| 19 |
|
| 20 |
Copyright (C) The Internet Society (2004). |
| 21 |
|
| 22 |
Abstract |
| 23 |
|
| 24 |
This document updates <a href="./rfc2132">RFC 2132</a> to reclassify Dynamic Host |
| 25 |
Configuration Protocol version 4 (DHCPv4) option codes 128 to 223 |
| 26 |
(decimal) as publicly defined options to be managed by IANA in |
| 27 |
accordance with <a href="./rfc2939">RFC 2939</a>. This document directs IANA to make these |
| 28 |
option codes available for assignment as publicly defined DHCP |
| 29 |
options for future options. |
| 30 |
|
| 31 |
Table of Contents |
| 32 |
|
| 33 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 34 |
<a href="#section-2">2</a>. Requirements Notation . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 35 |
<a href="#section-3">3</a>. Background . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 36 |
<a href="#section-3.1">3.1</a>. Publicly Defined Options Range . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 37 |
<a href="#section-3.2">3.2</a>. Site-Specific Options Range . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 38 |
<a href="#section-4">4</a>. Reclassifying Options . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 39 |
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 40 |
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 41 |
<a href="#section-7">7</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 42 |
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 43 |
<a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 44 |
<a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 45 |
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 46 |
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Volz Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc3942">RFC 3942</a> Reclassifying DHCPv4 Options November 2004</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
The DHCPv4 [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] publicly defined options range, options 1 - 127, |
| 60 |
is nearly used up. Efforts such as [<a href="./rfc3679" title=""Unused Dynamic Host Configuration Protocol (DHCP) Option Codes"">RFC3679</a>] help extend the life of |
| 61 |
this space, but ultimately the space will be exhausted. |
| 62 |
|
| 63 |
This document reclassifies much of the site-specific option range, |
| 64 |
which has not been widely used for its original intended purpose, to |
| 65 |
extend the publicly defined options space. |
| 66 |
|
| 67 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Notation</span> |
| 68 |
|
| 69 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 70 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 71 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 72 |
|
| 73 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Background</span> |
| 74 |
|
| 75 |
The DHCP option space (0 - 255) is divided into two ranges [<a href="./rfc2132" title=""DHCP Options and BOOTP Vendor Extensions"">RFC2132</a>]: |
| 76 |
|
| 77 |
1. 1 - 127 are publicly defined options, now allocated in accordance |
| 78 |
with [<a href="./rfc2939" title=""Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types"">RFC2939</a>]. |
| 79 |
|
| 80 |
2. 128 - 254 are site-specific options. |
| 81 |
|
| 82 |
Options 0 (pad) and 255 (end) are special and defined in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>]. |
| 83 |
|
| 84 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Publicly Defined Options Range</span> |
| 85 |
|
| 86 |
The publicly defined options space (1 - 127) is nearly exhausted. |
| 87 |
Recent work [<a href="./rfc3679" title=""Unused Dynamic Host Configuration Protocol (DHCP) Option Codes"">RFC3679</a>] will buy more time, as several allocated but |
| 88 |
unused option codes have been reclaimed. A review could be made from |
| 89 |
time to time to determine whether there are other option codes that |
| 90 |
can be reclaimed. |
| 91 |
|
| 92 |
A longer-term solution to the eventual exhaustion of the publicly |
| 93 |
defined options space is desired. The DHC WG evaluated several |
| 94 |
solutions: |
| 95 |
|
| 96 |
1. Using options 126 and 127 to carry 16-bit options as originally |
| 97 |
proposed by Ralph Droms in late 1996. However, this significantly |
| 98 |
penalizes the first option assigned to this new space, as it |
| 99 |
requires implementing the 16-bit option support. Because of this, |
| 100 |
options 126 and 127 have been reclaimed [<a href="./rfc3679" title=""Unused Dynamic Host Configuration Protocol (DHCP) Option Codes"">RFC3679</a>]. |
| 101 |
|
| 102 |
2. Using a new magic cookie and 16-bit option code format. However, |
| 103 |
this proposal |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Volz Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc3942">RFC 3942</a> Reclassifying DHCPv4 Options November 2004</span> |
| 111 |
|
| 112 |
|
| 113 |
* penalizes the first option assigned to this new space, as it |
| 114 |
requires significant changes to clients, servers, and relay |
| 115 |
agents, |
| 116 |
|
| 117 |
* could adversely impact existing clients, servers, and relay |
| 118 |
agents that fail to properly check the magic cookie value, |
| 119 |
|
| 120 |
* requires support of both message formats for the foreseeable |
| 121 |
future, and |
| 122 |
|
| 123 |
* requires clients to send multiple DHCPDISCOVER messages -- one |
| 124 |
for each magic cookie. |
| 125 |
|
| 126 |
3. Reclassifying a portion of the site-specific option codes as |
| 127 |
publicly defined. The impact is minimal, as only those sites |
| 128 |
presently using options in the reclassified range need to renumber |
| 129 |
their options. |
| 130 |
|
| 131 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Site-Specific Options Range</span> |
| 132 |
|
| 133 |
The site-specific option range is rather large (127 options in all) |
| 134 |
and little used. The original intent of the site-specific option |
| 135 |
range was to support local (to a site) configuration options, and it |
| 136 |
is difficult to believe a site would need 127 options for this |
| 137 |
purpose. Further, many DHCP client implementations do not provide a |
| 138 |
well documented means to request site-specific options from a server |
| 139 |
or to allow applications to extract the returned option values. |
| 140 |
|
| 141 |
Some vendors have made use of site-specific option codes that violate |
| 142 |
the intent of the site-specific options, as the options are used to |
| 143 |
configure features of their products and thus are specific to many |
| 144 |
sites. This usage could potentially cause problems if a site that |
| 145 |
has been using the same site-specific option codes for other purposes |
| 146 |
deploys products from one of the vendors, or if two vendors pick the |
| 147 |
same site-specific options. |
| 148 |
|
| 149 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Reclassifying Options</span> |
| 150 |
|
| 151 |
The site-specific option codes 128 to 223 are hereby reclassified as |
| 152 |
publicly defined options. This leaves 31 site-specific options, 224 |
| 153 |
to 254. |
| 154 |
|
| 155 |
To allow vendors that have made use of site-specific options within |
| 156 |
the reclassified range to publish their option usage and to request |
| 157 |
an official assignment of the option number to that usage, the |
| 158 |
following procedure will be used to reclassify these options: |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Volz Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc3942">RFC 3942</a> Reclassifying DHCPv4 Options November 2004</span> |
| 167 |
|
| 168 |
|
| 169 |
1. The reclassified options (128 to 223) will be placed in the |
| 170 |
"Unavailable" state by IANA. These options are not yet available |
| 171 |
for assignment to publicly defined options. |
| 172 |
|
| 173 |
2. Vendors that currently use one or more of the reclassified options |
| 174 |
have 6 months following this RFC's publication date to notify the |
| 175 |
DHC WG and IANA that they are using particular options numbers and |
| 176 |
agree to document that usage in an RFC. IANA will move these |
| 177 |
options from the "Unavailable" to "Tentatively Assigned" state. |
| 178 |
|
| 179 |
Vendors have 18 months from this RFC's publication date to start |
| 180 |
the documentation process by submitting an Internet-Draft. |
| 181 |
|
| 182 |
NOTE: If multiple vendors of an option number come forward and can |
| 183 |
demonstrate that their usage is in reasonably wide use, none of |
| 184 |
the vendors will be allowed to keep the current option number, and |
| 185 |
they MUST go through the normal process of getting a publicly |
| 186 |
assigned option [<a href="./rfc2939" title=""Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types"">RFC2939</a>]. |
| 187 |
|
| 188 |
3. Any options still classified as "Unavailable" 6 months after the |
| 189 |
RFC publication date will be moved to the "Unassigned" state by |
| 190 |
IANA. These options may then be assigned to any new publicly |
| 191 |
defined options in accordance with [<a href="./rfc2939" title=""Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types"">RFC2939</a>]. |
| 192 |
|
| 193 |
4. For those options in the "Tentatively Assigned" state, vendors |
| 194 |
have 18 months following this RFC's publication date to submit an |
| 195 |
Internet-Draft documenting the option. The documented usage MUST |
| 196 |
be consistent with the existing usage. When the option usage is |
| 197 |
published as an RFC, IANA will move the option to the "Assigned" |
| 198 |
state. |
| 199 |
|
| 200 |
If no Internet-Draft is published within the 18 months or should |
| 201 |
one of these Internet-Drafts expire after the 18 months, IANA will |
| 202 |
move the option to the "Unassigned" state, and the option may then |
| 203 |
be assigned to any new publicly defined options in accordance with |
| 204 |
[<a href="./rfc2939" title=""Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types"">RFC2939</a>]. |
| 205 |
|
| 206 |
Sites presently using site-specific option codes within the |
| 207 |
reclassified range SHOULD take steps to renumber these options to |
| 208 |
values within the remaining range. If a site needs more than 31 |
| 209 |
site-specific options, the site must switch to using suboptions, as |
| 210 |
has been done for other options, such as the Relay Agent Information |
| 211 |
Option [<a href="./rfc3046" title=""DHCP Relay Agent Information Option"">RFC3046</a>]. |
| 212 |
|
| 213 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 214 |
|
| 215 |
This document in and by itself provides no security, nor does it |
| 216 |
impact existing DCHP security as described in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>]. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Volz Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc3942">RFC 3942</a> Reclassifying DHCPv4 Options November 2004</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 226 |
|
| 227 |
IANA is requested to |
| 228 |
|
| 229 |
1. expand the publicly defined DHCPv4 options space from 1 - 127 to 1 |
| 230 |
- 223. The new options (128 - 223) are to be listed as |
| 231 |
"Unavailable" and MUST NOT be assigned to any publicly defined |
| 232 |
options. |
| 233 |
|
| 234 |
2. receive notices from vendors that have been using one or more of |
| 235 |
the options in the 128-223 range that they are using the option |
| 236 |
and are willing to document that usage. IANA will list these |
| 237 |
options as "Tentatively Assigned". |
| 238 |
|
| 239 |
3. change the listing of any options listed as "Unavailable" to |
| 240 |
"Available" 6 months from this RFC's publication date. These |
| 241 |
options may now be assigned in accordance with [<a href="./rfc2939" title=""Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types"">RFC2939</a>]. |
| 242 |
|
| 243 |
4. change the listing of any options listed as "Tentatively-Assigned" |
| 244 |
to "Unavailable" 18 months from this RFC's publication date and |
| 245 |
periodically thereafter as long as there is an option listed as |
| 246 |
"Tentatively-Assigned", if no un-expired Internet-Draft exists |
| 247 |
documenting the usage. |
| 248 |
|
| 249 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span> |
| 250 |
|
| 251 |
Many thanks to Ralph Droms and Ted Lemon for their valuable input and |
| 252 |
earlier work on the various alternatives. |
| 253 |
|
| 254 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 255 |
|
| 256 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span> |
| 257 |
|
| 258 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 259 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 260 |
|
| 261 |
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC</a> |
| 262 |
<a href="./rfc2131">2131</a>, March 1997. |
| 263 |
|
| 264 |
[<a id="ref-RFC2132">RFC2132</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor |
| 265 |
Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997. |
| 266 |
|
| 267 |
[<a id="ref-RFC2939">RFC2939</a>] Droms, R., "Procedures and IANA Guidelines for Definition |
| 268 |
of New DHCP Options and Message Types", <a href="https://www.rfc-editor.org/bcp/bcp43">BCP 43</a>, <a href="./rfc2939">RFC 2939</a>, |
| 269 |
September 2000. |
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Volz Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc3942">RFC 3942</a> Reclassifying DHCPv4 Options November 2004</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span> |
| 282 |
|
| 283 |
[<a id="ref-RFC3046">RFC3046</a>] Patrick, M., "DHCP Relay Agent Information Option", <a href="./rfc3046">RFC</a> |
| 284 |
<a href="./rfc3046">3046</a>, January 2001. |
| 285 |
|
| 286 |
[<a id="ref-RFC3679">RFC3679</a>] Droms, R., "Unused Dynamic Host Configuration Protocol |
| 287 |
(DHCP) Option Codes", <a href="./rfc3679">RFC 3679</a>, January 2004. |
| 288 |
|
| 289 |
Author's Address |
| 290 |
|
| 291 |
Bernard Volz |
| 292 |
Cisco Systems, Inc. |
| 293 |
1414 Massachusetts Ave. |
| 294 |
Boxborough, MA 01719 |
| 295 |
USA |
| 296 |
|
| 297 |
Phone: +1 978 936 0382 |
| 298 |
EMail: [email protected] |
| 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">Volz Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc3942">RFC 3942</a> Reclassifying DHCPv4 Options November 2004</span> |
| 335 |
|
| 336 |
|
| 337 |
Full Copyright Statement |
| 338 |
|
| 339 |
Copyright (C) The Internet Society (2004). |
| 340 |
|
| 341 |
This document is subject to the rights, licenses and restrictions |
| 342 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 343 |
retain all their rights. |
| 344 |
|
| 345 |
This document and the information contained herein are provided on an |
| 346 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 347 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
| 348 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
| 349 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
| 350 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 351 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 352 |
|
| 353 |
Intellectual Property |
| 354 |
|
| 355 |
The IETF takes no position regarding the validity or scope of any |
| 356 |
Intellectual Property Rights or other rights that might be claimed to |
| 357 |
pertain to the implementation or use of the technology described in |
| 358 |
this document or the extent to which any license under such rights |
| 359 |
might or might not be available; nor does it represent that it has |
| 360 |
made any independent effort to identify any such rights. Information |
| 361 |
on the IETF's procedures with respect to rights in IETF Documents can |
| 362 |
be found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 363 |
|
| 364 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 365 |
assurances of licenses to be made available, or the result of an |
| 366 |
attempt made to obtain a general license or permission for the use of |
| 367 |
such proprietary rights by implementers or users of this |
| 368 |
specification can be obtained from the IETF on-line IPR repository at |
| 369 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 370 |
|
| 371 |
The IETF invites any interested party to bring to its attention any |
| 372 |
copyrights, patents or patent applications, or other proprietary |
| 373 |
rights that may cover technology that may be required to implement |
| 374 |
this standard. Please address the information to the IETF at ietf- |
| 375 |
[email protected]. |
| 376 |
|
| 377 |
Acknowledgement |
| 378 |
|
| 379 |
Funding for the RFC Editor function is currently provided by the |
| 380 |
Internet Society. |
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
Volz Standards Track [Page 7] |
| 389 |
</pre> |