| 1 |
<pre>Network Working Group S. Alexander |
| 2 |
Request for Comments: 2132 Silicon Graphics, Inc. |
| 3 |
Obsoletes: <a href="./rfc1533">1533</a> R. Droms |
| 4 |
Category: Standards Track Bucknell University |
| 5 |
March 1997 |
| 6 |
|
| 7 |
<span class="h1">DHCP Options and BOOTP Vendor Extensions</span> |
| 8 |
|
| 9 |
Status of this memo |
| 10 |
|
| 11 |
This document specifies an Internet standards track protocol for the |
| 12 |
Internet community, and requests discussion and suggestions for |
| 13 |
improvements. Please refer to the current edition of the "Internet |
| 14 |
Official Protocol Standards" (STD 1) for the standardization state |
| 15 |
and status of this protocol. Distribution of this memo is unlimited. |
| 16 |
|
| 17 |
Abstract |
| 18 |
|
| 19 |
The Dynamic Host Configuration Protocol (DHCP) [<a href="#ref-1" title=""Dynamic Host Configuration Protocol"">1</a>] provides a |
| 20 |
framework for passing configuration information to hosts on a TCP/IP |
| 21 |
network. Configuration parameters and other control information are |
| 22 |
carried in tagged data items that are stored in the 'options' field |
| 23 |
of the DHCP message. The data items themselves are also called |
| 24 |
"options." |
| 25 |
|
| 26 |
This document specifies the current set of DHCP options. Future |
| 27 |
options will be specified in separate RFCs. The current list of |
| 28 |
valid options is also available in <a href="ftp://ftp.isi.edu/in-notes/iana/assignments">ftp://ftp.isi.edu/in-</a> |
| 29 |
<a href="ftp://ftp.isi.edu/in-notes/iana/assignments">notes/iana/assignments</a> [<a href="#ref-22" title=""Assigned Numbers"">22</a>]. |
| 30 |
|
| 31 |
All of the vendor information extensions defined in <a href="./rfc1497">RFC 1497</a> [<a href="#ref-2" title=""BOOTP Vendor Information Extensions"">2</a>] may |
| 32 |
be used as DHCP options. The definitions given in <a href="./rfc1497">RFC 1497</a> are |
| 33 |
included in this document, which supersedes <a href="./rfc1497">RFC 1497</a>. All of the |
| 34 |
DHCP options defined in this document, except for those specific to |
| 35 |
DHCP as defined in <a href="#section-9">section 9</a>, may be used as BOOTP vendor information |
| 36 |
extensions. |
| 37 |
|
| 38 |
Table of Contents |
| 39 |
|
| 40 |
<a href="#section-1">1</a>. Introduction .............................................. <a href="#page-2">2</a> |
| 41 |
<a href="#section-2">2</a>. BOOTP Extension/DHCP Option Field Format .................. <a href="#page-4">4</a> |
| 42 |
<a href="#section-3">3</a>. <a href="./rfc1497">RFC 1497</a> Vendor Extensions ................................ <a href="#page-5">5</a> |
| 43 |
<a href="#section-4">4</a>. IP Layer Parameters per Host .............................. <a href="#page-11">11</a> |
| 44 |
<a href="#section-5">5</a>. IP Layer Parameters per Interface ........................ <a href="#page-13">13</a> |
| 45 |
<a href="#section-6">6</a>. Link Layer Parameters per Interface ....................... <a href="#page-16">16</a> |
| 46 |
<a href="#section-7">7</a>. TCP Parameters ............................................ <a href="#page-17">17</a> |
| 47 |
<a href="#section-8">8</a>. Application and Service Parameters ........................ <a href="#page-18">18</a> |
| 48 |
<a href="#section-9">9</a>. DHCP Extensions ........................................... <a href="#page-25">25</a> |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Alexander & Droms 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="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 55 |
|
| 56 |
|
| 57 |
<a href="#section-10">10</a>. Defining new extensions ................................... <a href="#page-31">31</a> |
| 58 |
<a href="#section-11">11</a>. Acknowledgements .......................................... <a href="#page-31">31</a> |
| 59 |
<a href="#section-12">12</a>. References ................................................ <a href="#page-32">32</a> |
| 60 |
<a href="#section-13">13</a>. Security Considerations ................................... <a href="#page-33">33</a> |
| 61 |
<a href="#section-14">14</a>. Authors' Addresses ........................................ <a href="#page-34">34</a> |
| 62 |
|
| 63 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 64 |
|
| 65 |
This document specifies options for use with both the Dynamic Host |
| 66 |
Configuration Protocol and the Bootstrap Protocol. |
| 67 |
|
| 68 |
The full description of DHCP packet formats may be found in the DHCP |
| 69 |
specification document [<a href="#ref-1" title=""Dynamic Host Configuration Protocol"">1</a>], and the full description of BOOTP packet |
| 70 |
formats may be found in the BOOTP specification document [<a href="#ref-3" title=""Bootstrap Protocol"">3</a>]. This |
| 71 |
document defines the format of information in the last field of DHCP |
| 72 |
packets ('options') and of BOOTP packets ('vend'). The remainder of |
| 73 |
this section defines a generalized use of this area for giving |
| 74 |
information useful to a wide class of machines, operating systems and |
| 75 |
configurations. Sites with a single DHCP or BOOTP server that is |
| 76 |
shared among heterogeneous clients may choose to define other, site- |
| 77 |
specific formats for the use of the 'options' field. |
| 78 |
|
| 79 |
<a href="#section-2">Section 2</a> of this memo describes the formats of DHCP options and |
| 80 |
BOOTP vendor extensions. <a href="#section-3">Section 3</a> describes options defined in |
| 81 |
previous documents for use with BOOTP (all may also be used with |
| 82 |
DHCP). Sections <a href="#section-4">4</a>-<a href="#section-8">8</a> define new options intended for use with both |
| 83 |
DHCP and BOOTP. <a href="#section-9">Section 9</a> defines options used only in DHCP. |
| 84 |
|
| 85 |
References further describing most of the options defined in sections |
| 86 |
2-6 can be found in <a href="#section-12">section 12</a>. The use of the options defined in |
| 87 |
<a href="#section-9">section 9</a> is described in the DHCP specification [<a href="#ref-1" title=""Dynamic Host Configuration Protocol"">1</a>]. |
| 88 |
|
| 89 |
Information on registering new options is contained in <a href="#section-10">section 10</a>. |
| 90 |
|
| 91 |
This document updates the definition of DHCP/BOOTP options that |
| 92 |
appears in <a href="./rfc1533">RFC1533</a>. The classing mechanism has been extended to |
| 93 |
include vendor classes as described in <a href="#section-8.4">section 8.4</a> and 9.13. The new |
| 94 |
procedure for defining new DHCP/BOOTP options in described in <a href="#section-10">section</a> |
| 95 |
<a href="#section-10">10</a>. Several new options, including NIS+ domain and servers, Mobile |
| 96 |
IP home agent, SMTP server, TFTP server and Bootfile server, have |
| 97 |
been added. Text giving definitions used throughout the document has |
| 98 |
been added in <a href="#section-1.1">section 1.1</a>. Text emphasizing the need for uniqueness |
| 99 |
of client-identifiers has been added to <a href="#section-9.14">section 9.14</a>. |
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Alexander & Droms 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="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a> Requirements</span> |
| 114 |
|
| 115 |
Throughout this document, the words that are used to define the |
| 116 |
significance of particular requirements are capitalized. These words |
| 117 |
are: |
| 118 |
|
| 119 |
o "MUST" |
| 120 |
|
| 121 |
This word or the adjective "REQUIRED" means that the item is an |
| 122 |
absolute requirement of this specification. |
| 123 |
|
| 124 |
o "MUST NOT" |
| 125 |
|
| 126 |
This phrase means that the item is an absolute prohibition of |
| 127 |
this specification. |
| 128 |
|
| 129 |
o "SHOULD" |
| 130 |
|
| 131 |
This word or the adjective "RECOMMENDED" means that there may |
| 132 |
exist valid reasons in particular circumstances to ignore this |
| 133 |
item, but the full implications should be understood and the case |
| 134 |
carefully weighed before choosing a different course. |
| 135 |
|
| 136 |
o "SHOULD NOT" |
| 137 |
|
| 138 |
This phrase means that there may exist valid reasons in |
| 139 |
particular circumstances when the listed behavior is acceptable |
| 140 |
or even useful, but the full implications should be understood |
| 141 |
and the case carefully weighed before implementing any behavior |
| 142 |
described with this label. |
| 143 |
|
| 144 |
o "MAY" |
| 145 |
|
| 146 |
This word or the adjective "OPTIONAL" means that this item is |
| 147 |
truly optional. One vendor may choose to include the item |
| 148 |
because a particular marketplace requires it or because it |
| 149 |
enhances the product, for example; another vendor may omit the |
| 150 |
same item. |
| 151 |
|
| 152 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a> Terminology</span> |
| 153 |
|
| 154 |
This document uses the following terms: |
| 155 |
|
| 156 |
o "DHCP client" |
| 157 |
|
| 158 |
A DHCP client or "client" is an Internet host using DHCP to |
| 159 |
obtain configuration parameters such as a network address. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Alexander & Droms 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="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 167 |
|
| 168 |
|
| 169 |
o "DHCP server" |
| 170 |
|
| 171 |
A DHCP server of "server"is an Internet host that returns |
| 172 |
configuration parameters to DHCP clients. |
| 173 |
|
| 174 |
o "binding" |
| 175 |
|
| 176 |
A binding is a collection of configuration parameters, including |
| 177 |
at least an IP address, associated with or "bound to" a DHCP |
| 178 |
client. Bindings are managed by DHCP servers. |
| 179 |
|
| 180 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. BOOTP Extension/DHCP Option Field Format</span> |
| 181 |
|
| 182 |
|
| 183 |
DHCP options have the same format as the BOOTP 'vendor extensions' |
| 184 |
defined in <a href="./rfc1497">RFC 1497</a> [<a href="#ref-2" title=""BOOTP Vendor Information Extensions"">2</a>]. Options may be fixed length or variable |
| 185 |
length. All options begin with a tag octet, which uniquely |
| 186 |
identifies the option. Fixed-length options without data consist of |
| 187 |
only a tag octet. Only options 0 and 255 are fixed length. All |
| 188 |
other options are variable-length with a length octet following the |
| 189 |
tag octet. The value of the length octet does not include the two |
| 190 |
octets specifying the tag and length. The length octet is followed |
| 191 |
by "length" octets of data. Options containing NVT ASCII data SHOULD |
| 192 |
NOT include a trailing NULL; however, the receiver of such options |
| 193 |
MUST be prepared to delete trailing nulls if they exist. The |
| 194 |
receiver MUST NOT require that a trailing null be included in the |
| 195 |
data. In the case of some variable-length options the length field |
| 196 |
is a constant but must still be specified. |
| 197 |
|
| 198 |
Any options defined subsequent to this document MUST contain a length |
| 199 |
octet even if the length is fixed or zero. |
| 200 |
|
| 201 |
All multi-octet quantities are in network byte-order. |
| 202 |
|
| 203 |
When used with BOOTP, the first four octets of the vendor information |
| 204 |
field have been assigned to the "magic cookie" (as suggested in <a href="./rfc951">RFC</a> |
| 205 |
<a href="./rfc951">951</a>). This field identifies the mode in which the succeeding data is |
| 206 |
to be interpreted. The value of the magic cookie is the 4 octet |
| 207 |
dotted decimal 99.130.83.99 (or hexadecimal number 63.82.53.63) in |
| 208 |
network byte order. |
| 209 |
|
| 210 |
All of the "vendor extensions" defined in <a href="./rfc1497">RFC 1497</a> are also DHCP |
| 211 |
options. |
| 212 |
|
| 213 |
Option codes 128 to 254 (decimal) are reserved for site-specific |
| 214 |
options. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Alexander & Droms 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="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 223 |
|
| 224 |
|
| 225 |
Except for the options in <a href="#section-9">section 9</a>, all options may be used with |
| 226 |
either DHCP or BOOTP. |
| 227 |
|
| 228 |
Many of these options have their default values specified in other |
| 229 |
documents. In particular, <a href="./rfc1122">RFC 1122</a> [<a href="#ref-4" title=""Requirements for Internet Hosts - Communication Layers"">4</a>] specifies default values for |
| 230 |
most IP and TCP configuration parameters. |
| 231 |
|
| 232 |
Many options supply one or more 32-bit IP address. Use of IP |
| 233 |
addresses rather than fully-qualified Domain Names (FQDNs) may make |
| 234 |
future renumbering of IP hosts more difficult. Use of these |
| 235 |
addresses is discouraged at sites that may require renumbering. |
| 236 |
|
| 237 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. <a href="./rfc1497">RFC 1497</a> Vendor Extensions</span> |
| 238 |
|
| 239 |
This section lists the vendor extensions as defined in <a href="./rfc1497">RFC 1497</a>. |
| 240 |
They are defined here for completeness. |
| 241 |
|
| 242 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Pad Option</span> |
| 243 |
|
| 244 |
The pad option can be used to cause subsequent fields to align on |
| 245 |
word boundaries. |
| 246 |
|
| 247 |
The code for the pad option is 0, and its length is 1 octet. |
| 248 |
|
| 249 |
Code |
| 250 |
+-----+ |
| 251 |
| 0 | |
| 252 |
+-----+ |
| 253 |
|
| 254 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. End Option</span> |
| 255 |
|
| 256 |
The end option marks the end of valid information in the vendor |
| 257 |
field. Subsequent octets should be filled with pad options. |
| 258 |
|
| 259 |
The code for the end option is 255, and its length is 1 octet. |
| 260 |
|
| 261 |
Code |
| 262 |
+-----+ |
| 263 |
| 255 | |
| 264 |
+-----+ |
| 265 |
|
| 266 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Subnet Mask</span> |
| 267 |
|
| 268 |
The subnet mask option specifies the client's subnet mask as per <a href="./rfc950">RFC</a> |
| 269 |
<a href="./rfc950">950</a> [<a href="#ref-5" title=""Internet Standard Subnetting Procedure"">5</a>]. |
| 270 |
|
| 271 |
If both the subnet mask and the router option are specified in a DHCP |
| 272 |
reply, the subnet mask option MUST be first. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Alexander & Droms 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="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 279 |
|
| 280 |
|
| 281 |
The code for the subnet mask option is 1, and its length is 4 octets. |
| 282 |
|
| 283 |
Code Len Subnet Mask |
| 284 |
+-----+-----+-----+-----+-----+-----+ |
| 285 |
| 1 | 4 | m1 | m2 | m3 | m4 | |
| 286 |
+-----+-----+-----+-----+-----+-----+ |
| 287 |
|
| 288 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Time Offset</span> |
| 289 |
|
| 290 |
The time offset field specifies the offset of the client's subnet in |
| 291 |
seconds from Coordinated Universal Time (UTC). The offset is |
| 292 |
expressed as a two's complement 32-bit integer. A positive offset |
| 293 |
indicates a location east of the zero meridian and a negative offset |
| 294 |
indicates a location west of the zero meridian. |
| 295 |
|
| 296 |
The code for the time offset option is 2, and its length is 4 octets. |
| 297 |
|
| 298 |
Code Len Time Offset |
| 299 |
+-----+-----+-----+-----+-----+-----+ |
| 300 |
| 2 | 4 | n1 | n2 | n3 | n4 | |
| 301 |
+-----+-----+-----+-----+-----+-----+ |
| 302 |
|
| 303 |
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Router Option</span> |
| 304 |
|
| 305 |
The router option specifies a list of IP addresses for routers on the |
| 306 |
client's subnet. Routers SHOULD be listed in order of preference. |
| 307 |
|
| 308 |
The code for the router option is 3. The minimum length for the |
| 309 |
router option is 4 octets, and the length MUST always be a multiple |
| 310 |
of 4. |
| 311 |
|
| 312 |
Code Len Address 1 Address 2 |
| 313 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 314 |
| 3 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 315 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 316 |
|
| 317 |
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Time Server Option</span> |
| 318 |
|
| 319 |
The time server option specifies a list of <a href="./rfc868">RFC 868</a> [<a href="#ref-6" title=""Time Protocol"">6</a>] time servers |
| 320 |
available to the client. Servers SHOULD be listed in order of |
| 321 |
preference. |
| 322 |
|
| 323 |
The code for the time server option is 4. The minimum length for |
| 324 |
this option is 4 octets, and the length MUST always be a multiple of |
| 325 |
4. |
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Alexander & Droms 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="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 335 |
|
| 336 |
|
| 337 |
Code Len Address 1 Address 2 |
| 338 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 339 |
| 4 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 340 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 341 |
|
| 342 |
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. Name Server Option</span> |
| 343 |
|
| 344 |
The name server option specifies a list of IEN 116 [<a href="#ref-7" title=""Name Server"">7</a>] name servers |
| 345 |
available to the client. Servers SHOULD be listed in order of |
| 346 |
preference. |
| 347 |
|
| 348 |
The code for the name server option is 5. The minimum length for |
| 349 |
this option is 4 octets, and the length MUST always be a multiple of |
| 350 |
4. |
| 351 |
|
| 352 |
Code Len Address 1 Address 2 |
| 353 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 354 |
| 5 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 355 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 356 |
|
| 357 |
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. Domain Name Server Option</span> |
| 358 |
|
| 359 |
The domain name server option specifies a list of Domain Name System |
| 360 |
(STD 13, <a href="./rfc1035">RFC 1035</a> [<a href="#ref-8" title=""Domain Names - Implementation and Specification"">8</a>]) name servers available to the client. Servers |
| 361 |
SHOULD be listed in order of preference. |
| 362 |
|
| 363 |
The code for the domain name server option is 6. The minimum length |
| 364 |
for this option is 4 octets, and the length MUST always be a multiple |
| 365 |
of 4. |
| 366 |
|
| 367 |
Code Len Address 1 Address 2 |
| 368 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 369 |
| 6 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 370 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 371 |
|
| 372 |
<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>. Log Server Option</span> |
| 373 |
|
| 374 |
The log server option specifies a list of MIT-LCS UDP log servers |
| 375 |
available to the client. Servers SHOULD be listed in order of |
| 376 |
preference. |
| 377 |
|
| 378 |
The code for the log server option is 7. The minimum length for this |
| 379 |
option is 4 octets, and the length MUST always be a multiple of 4. |
| 380 |
|
| 381 |
Code Len Address 1 Address 2 |
| 382 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 383 |
| 7 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 384 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Alexander & Droms Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h3"><a class="selflink" id="section-3.10" href="#section-3.10">3.10</a>. Cookie Server Option</span> |
| 394 |
|
| 395 |
The cookie server option specifies a list of <a href="./rfc865">RFC 865</a> [<a href="#ref-9" title=""Quote of the Day Protocol"">9</a>] cookie |
| 396 |
servers available to the client. Servers SHOULD be listed in order |
| 397 |
of preference. |
| 398 |
|
| 399 |
The code for the log server option is 8. The minimum length for this |
| 400 |
option is 4 octets, and the length MUST always be a multiple of 4. |
| 401 |
|
| 402 |
Code Len Address 1 Address 2 |
| 403 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 404 |
| 8 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 405 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 406 |
|
| 407 |
<span class="h3"><a class="selflink" id="section-3.11" href="#section-3.11">3.11</a>. LPR Server Option</span> |
| 408 |
|
| 409 |
The LPR server option specifies a list of <a href="./rfc1179">RFC 1179</a> [<a href="#ref-10" title=""Line Printer Daemon Protocol"">10</a>] line printer |
| 410 |
servers available to the client. Servers SHOULD be listed in order |
| 411 |
of preference. |
| 412 |
|
| 413 |
The code for the LPR server option is 9. The minimum length for this |
| 414 |
option is 4 octets, and the length MUST always be a multiple of 4. |
| 415 |
|
| 416 |
Code Len Address 1 Address 2 |
| 417 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 418 |
| 9 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 419 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 420 |
|
| 421 |
<span class="h3"><a class="selflink" id="section-3.12" href="#section-3.12">3.12</a>. Impress Server Option</span> |
| 422 |
|
| 423 |
The Impress server option specifies a list of Imagen Impress servers |
| 424 |
available to the client. Servers SHOULD be listed in order of |
| 425 |
preference. |
| 426 |
|
| 427 |
The code for the Impress server option is 10. The minimum length for |
| 428 |
this option is 4 octets, and the length MUST always be a multiple of |
| 429 |
4. |
| 430 |
|
| 431 |
Code Len Address 1 Address 2 |
| 432 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 433 |
| 10 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 434 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 435 |
|
| 436 |
<span class="h3"><a class="selflink" id="section-3.13" href="#section-3.13">3.13</a>. Resource Location Server Option</span> |
| 437 |
|
| 438 |
This option specifies a list of <a href="./rfc887">RFC 887</a> [<a href="#ref-11" title=""Resource Location Protocol"">11</a>] Resource Location |
| 439 |
servers available to the client. Servers SHOULD be listed in order |
| 440 |
of preference. |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Alexander & Droms Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 447 |
|
| 448 |
|
| 449 |
The code for this option is 11. The minimum length for this option |
| 450 |
is 4 octets, and the length MUST always be a multiple of 4. |
| 451 |
|
| 452 |
Code Len Address 1 Address 2 |
| 453 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 454 |
| 11 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 455 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 456 |
|
| 457 |
<span class="h3"><a class="selflink" id="section-3.14" href="#section-3.14">3.14</a>. Host Name Option</span> |
| 458 |
|
| 459 |
This option specifies the name of the client. The name may or may |
| 460 |
not be qualified with the local domain name (see <a href="#section-3.17">section 3.17</a> for the |
| 461 |
preferred way to retrieve the domain name). See <a href="./rfc1035">RFC 1035</a> for |
| 462 |
character set restrictions. |
| 463 |
|
| 464 |
The code for this option is 12, and its minimum length is 1. |
| 465 |
|
| 466 |
Code Len Host Name |
| 467 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 468 |
| 12 | n | h1 | h2 | h3 | h4 | h5 | h6 | ... |
| 469 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 470 |
|
| 471 |
<span class="h3"><a class="selflink" id="section-3.15" href="#section-3.15">3.15</a>. Boot File Size Option</span> |
| 472 |
|
| 473 |
This option specifies the length in 512-octet blocks of the default |
| 474 |
boot image for the client. The file length is specified as an |
| 475 |
unsigned 16-bit integer. |
| 476 |
|
| 477 |
The code for this option is 13, and its length is 2. |
| 478 |
|
| 479 |
Code Len File Size |
| 480 |
+-----+-----+-----+-----+ |
| 481 |
| 13 | 2 | l1 | l2 | |
| 482 |
+-----+-----+-----+-----+ |
| 483 |
|
| 484 |
<span class="h3"><a class="selflink" id="section-3.16" href="#section-3.16">3.16</a>. Merit Dump File</span> |
| 485 |
|
| 486 |
This option specifies the path-name of a file to which the client's |
| 487 |
core image should be dumped in the event the client crashes. The |
| 488 |
path is formatted as a character string consisting of characters from |
| 489 |
the NVT ASCII character set. |
| 490 |
|
| 491 |
The code for this option is 14. Its minimum length is 1. |
| 492 |
|
| 493 |
Code Len Dump File Pathname |
| 494 |
+-----+-----+-----+-----+-----+-----+--- |
| 495 |
| 14 | n | n1 | n2 | n3 | n4 | ... |
| 496 |
+-----+-----+-----+-----+-----+-----+--- |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Alexander & Droms Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h3"><a class="selflink" id="section-3.17" href="#section-3.17">3.17</a>. Domain Name</span> |
| 506 |
|
| 507 |
This option specifies the domain name that client should use when |
| 508 |
resolving hostnames via the Domain Name System. |
| 509 |
|
| 510 |
The code for this option is 15. Its minimum length is 1. |
| 511 |
|
| 512 |
Code Len Domain Name |
| 513 |
+-----+-----+-----+-----+-----+-----+-- |
| 514 |
| 15 | n | d1 | d2 | d3 | d4 | ... |
| 515 |
+-----+-----+-----+-----+-----+-----+-- |
| 516 |
|
| 517 |
<span class="h3"><a class="selflink" id="section-3.18" href="#section-3.18">3.18</a>. Swap Server</span> |
| 518 |
|
| 519 |
This specifies the IP address of the client's swap server. |
| 520 |
|
| 521 |
The code for this option is 16 and its length is 4. |
| 522 |
|
| 523 |
Code Len Swap Server Address |
| 524 |
+-----+-----+-----+-----+-----+-----+ |
| 525 |
| 16 | n | a1 | a2 | a3 | a4 | |
| 526 |
+-----+-----+-----+-----+-----+-----+ |
| 527 |
|
| 528 |
<span class="h3"><a class="selflink" id="section-3.19" href="#section-3.19">3.19</a>. Root Path</span> |
| 529 |
|
| 530 |
This option specifies the path-name that contains the client's root |
| 531 |
disk. The path is formatted as a character string consisting of |
| 532 |
characters from the NVT ASCII character set. |
| 533 |
|
| 534 |
The code for this option is 17. Its minimum length is 1. |
| 535 |
|
| 536 |
Code Len Root Disk Pathname |
| 537 |
+-----+-----+-----+-----+-----+-----+--- |
| 538 |
| 17 | n | n1 | n2 | n3 | n4 | ... |
| 539 |
+-----+-----+-----+-----+-----+-----+--- |
| 540 |
|
| 541 |
<span class="h3"><a class="selflink" id="section-3.20" href="#section-3.20">3.20</a>. Extensions Path</span> |
| 542 |
|
| 543 |
A string to specify a file, retrievable via TFTP, which contains |
| 544 |
information which can be interpreted in the same way as the 64-octet |
| 545 |
vendor-extension field within the BOOTP response, with the following |
| 546 |
exceptions: |
| 547 |
|
| 548 |
- the length of the file is unconstrained; |
| 549 |
- all references to Tag 18 (i.e., instances of the |
| 550 |
BOOTP Extensions Path field) within the file are |
| 551 |
ignored. |
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Alexander & Droms Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 559 |
|
| 560 |
|
| 561 |
The code for this option is 18. Its minimum length is 1. |
| 562 |
|
| 563 |
Code Len Extensions Pathname |
| 564 |
+-----+-----+-----+-----+-----+-----+--- |
| 565 |
| 18 | n | n1 | n2 | n3 | n4 | ... |
| 566 |
+-----+-----+-----+-----+-----+-----+--- |
| 567 |
|
| 568 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IP Layer Parameters per Host</span> |
| 569 |
|
| 570 |
This section details the options that affect the operation of the IP |
| 571 |
layer on a per-host basis. |
| 572 |
|
| 573 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. IP Forwarding Enable/Disable Option</span> |
| 574 |
|
| 575 |
This option specifies whether the client should configure its IP |
| 576 |
layer for packet forwarding. A value of 0 means disable IP |
| 577 |
forwarding, and a value of 1 means enable IP forwarding. |
| 578 |
|
| 579 |
The code for this option is 19, and its length is 1. |
| 580 |
|
| 581 |
Code Len Value |
| 582 |
+-----+-----+-----+ |
| 583 |
| 19 | 1 | 0/1 | |
| 584 |
+-----+-----+-----+ |
| 585 |
|
| 586 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Non-Local Source Routing Enable/Disable Option</span> |
| 587 |
|
| 588 |
This option specifies whether the client should configure its IP |
| 589 |
layer to allow forwarding of datagrams with non-local source routes |
| 590 |
(see Section 3.3.5 of [<a href="#ref-4" title=""Requirements for Internet Hosts - Communication Layers"">4</a>] for a discussion of this topic). A value |
| 591 |
of 0 means disallow forwarding of such datagrams, and a value of 1 |
| 592 |
means allow forwarding. |
| 593 |
|
| 594 |
The code for this option is 20, and its length is 1. |
| 595 |
|
| 596 |
Code Len Value |
| 597 |
+-----+-----+-----+ |
| 598 |
| 20 | 1 | 0/1 | |
| 599 |
+-----+-----+-----+ |
| 600 |
|
| 601 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Policy Filter Option</span> |
| 602 |
|
| 603 |
This option specifies policy filters for non-local source routing. |
| 604 |
The filters consist of a list of IP addresses and masks which specify |
| 605 |
destination/mask pairs with which to filter incoming source routes. |
| 606 |
|
| 607 |
Any source routed datagram whose next-hop address does not match one |
| 608 |
of the filters should be discarded by the client. |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Alexander & Droms Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 615 |
|
| 616 |
|
| 617 |
See [<a href="#ref-4" title=""Requirements for Internet Hosts - Communication Layers"">4</a>] for further information. |
| 618 |
|
| 619 |
The code for this option is 21. The minimum length of this option is |
| 620 |
8, and the length MUST be a multiple of 8. |
| 621 |
|
| 622 |
Code Len Address 1 Mask 1 |
| 623 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+ |
| 624 |
| 21 | n | a1 | a2 | a3 | a4 | m1 | m2 | m3 | m4 | |
| 625 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+ |
| 626 |
Address 2 Mask 2 |
| 627 |
+-----+-----+-----+-----+-----+-----+-----+-----+--- |
| 628 |
| a1 | a2 | a3 | a4 | m1 | m2 | m3 | m4 | ... |
| 629 |
+-----+-----+-----+-----+-----+-----+-----+-----+--- |
| 630 |
|
| 631 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Maximum Datagram Reassembly Size</span> |
| 632 |
|
| 633 |
This option specifies the maximum size datagram that the client |
| 634 |
should be prepared to reassemble. The size is specified as a 16-bit |
| 635 |
unsigned integer. The minimum value legal value is 576. |
| 636 |
|
| 637 |
The code for this option is 22, and its length is 2. |
| 638 |
|
| 639 |
Code Len Size |
| 640 |
+-----+-----+-----+-----+ |
| 641 |
| 22 | 2 | s1 | s2 | |
| 642 |
+-----+-----+-----+-----+ |
| 643 |
|
| 644 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Default IP Time-to-live</span> |
| 645 |
|
| 646 |
This option specifies the default time-to-live that the client should |
| 647 |
use on outgoing datagrams. The TTL is specified as an octet with a |
| 648 |
value between 1 and 255. |
| 649 |
|
| 650 |
The code for this option is 23, and its length is 1. |
| 651 |
|
| 652 |
Code Len TTL |
| 653 |
+-----+-----+-----+ |
| 654 |
| 23 | 1 | ttl | |
| 655 |
+-----+-----+-----+ |
| 656 |
|
| 657 |
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. Path MTU Aging Timeout Option</span> |
| 658 |
|
| 659 |
This option specifies the timeout (in seconds) to use when aging Path |
| 660 |
MTU values discovered by the mechanism defined in <a href="./rfc1191">RFC 1191</a> [<a href="#ref-12" title=""Path MTU Discovery"">12</a>]. The |
| 661 |
timeout is specified as a 32-bit unsigned integer. |
| 662 |
|
| 663 |
The code for this option is 24, and its length is 4. |
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Alexander & Droms Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 671 |
|
| 672 |
|
| 673 |
Code Len Timeout |
| 674 |
+-----+-----+-----+-----+-----+-----+ |
| 675 |
| 24 | 4 | t1 | t2 | t3 | t4 | |
| 676 |
+-----+-----+-----+-----+-----+-----+ |
| 677 |
|
| 678 |
<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. Path MTU Plateau Table Option</span> |
| 679 |
|
| 680 |
This option specifies a table of MTU sizes to use when performing |
| 681 |
Path MTU Discovery as defined in <a href="./rfc1191">RFC 1191</a>. The table is formatted as |
| 682 |
a list of 16-bit unsigned integers, ordered from smallest to largest. |
| 683 |
The minimum MTU value cannot be smaller than 68. |
| 684 |
|
| 685 |
The code for this option is 25. Its minimum length is 2, and the |
| 686 |
length MUST be a multiple of 2. |
| 687 |
|
| 688 |
Code Len Size 1 Size 2 |
| 689 |
+-----+-----+-----+-----+-----+-----+--- |
| 690 |
| 25 | n | s1 | s2 | s1 | s2 | ... |
| 691 |
+-----+-----+-----+-----+-----+-----+--- |
| 692 |
|
| 693 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IP Layer Parameters per Interface</span> |
| 694 |
|
| 695 |
This section details the options that affect the operation of the IP |
| 696 |
layer on a per-interface basis. It is expected that a client can |
| 697 |
issue multiple requests, one per interface, in order to configure |
| 698 |
interfaces with their specific parameters. |
| 699 |
|
| 700 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Interface MTU Option</span> |
| 701 |
|
| 702 |
This option specifies the MTU to use on this interface. The MTU is |
| 703 |
specified as a 16-bit unsigned integer. The minimum legal value for |
| 704 |
the MTU is 68. |
| 705 |
|
| 706 |
The code for this option is 26, and its length is 2. |
| 707 |
|
| 708 |
Code Len MTU |
| 709 |
+-----+-----+-----+-----+ |
| 710 |
| 26 | 2 | m1 | m2 | |
| 711 |
+-----+-----+-----+-----+ |
| 712 |
|
| 713 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. All Subnets are Local Option</span> |
| 714 |
|
| 715 |
This option specifies whether or not the client may assume that all |
| 716 |
subnets of the IP network to which the client is connected use the |
| 717 |
same MTU as the subnet of that network to which the client is |
| 718 |
directly connected. A value of 1 indicates that all subnets share |
| 719 |
the same MTU. A value of 0 means that the client should assume that |
| 720 |
some subnets of the directly connected network may have smaller MTUs. |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Alexander & Droms Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 727 |
|
| 728 |
|
| 729 |
The code for this option is 27, and its length is 1. |
| 730 |
|
| 731 |
Code Len Value |
| 732 |
+-----+-----+-----+ |
| 733 |
| 27 | 1 | 0/1 | |
| 734 |
+-----+-----+-----+ |
| 735 |
|
| 736 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Broadcast Address Option</span> |
| 737 |
|
| 738 |
This option specifies the broadcast address in use on the client's |
| 739 |
subnet. Legal values for broadcast addresses are specified in |
| 740 |
section 3.2.1.3 of [<a href="#ref-4" title=""Requirements for Internet Hosts - Communication Layers"">4</a>]. |
| 741 |
|
| 742 |
The code for this option is 28, and its length is 4. |
| 743 |
|
| 744 |
Code Len Broadcast Address |
| 745 |
+-----+-----+-----+-----+-----+-----+ |
| 746 |
| 28 | 4 | b1 | b2 | b3 | b4 | |
| 747 |
+-----+-----+-----+-----+-----+-----+ |
| 748 |
|
| 749 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Perform Mask Discovery Option</span> |
| 750 |
|
| 751 |
This option specifies whether or not the client should perform subnet |
| 752 |
mask discovery using ICMP. A value of 0 indicates that the client |
| 753 |
should not perform mask discovery. A value of 1 means that the |
| 754 |
client should perform mask discovery. |
| 755 |
|
| 756 |
The code for this option is 29, and its length is 1. |
| 757 |
|
| 758 |
Code Len Value |
| 759 |
+-----+-----+-----+ |
| 760 |
| 29 | 1 | 0/1 | |
| 761 |
+-----+-----+-----+ |
| 762 |
|
| 763 |
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Mask Supplier Option</span> |
| 764 |
|
| 765 |
This option specifies whether or not the client should respond to |
| 766 |
subnet mask requests using ICMP. A value of 0 indicates that the |
| 767 |
client should not respond. A value of 1 means that the client should |
| 768 |
respond. |
| 769 |
|
| 770 |
The code for this option is 30, and its length is 1. |
| 771 |
|
| 772 |
Code Len Value |
| 773 |
+-----+-----+-----+ |
| 774 |
| 30 | 1 | 0/1 | |
| 775 |
+-----+-----+-----+ |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Alexander & Droms Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. Perform Router Discovery Option</span> |
| 786 |
|
| 787 |
This option specifies whether or not the client should solicit |
| 788 |
routers using the Router Discovery mechanism defined in <a href="./rfc1256">RFC 1256</a> |
| 789 |
[<a href="#ref-13" title=""ICMP Router Discovery Messages"">13</a>]. A value of 0 indicates that the client should not perform |
| 790 |
router discovery. A value of 1 means that the client should perform |
| 791 |
router discovery. |
| 792 |
|
| 793 |
The code for this option is 31, and its length is 1. |
| 794 |
|
| 795 |
Code Len Value |
| 796 |
+-----+-----+-----+ |
| 797 |
| 31 | 1 | 0/1 | |
| 798 |
+-----+-----+-----+ |
| 799 |
|
| 800 |
<span class="h3"><a class="selflink" id="section-5.7" href="#section-5.7">5.7</a>. Router Solicitation Address Option</span> |
| 801 |
|
| 802 |
This option specifies the address to which the client should transmit |
| 803 |
router solicitation requests. |
| 804 |
|
| 805 |
The code for this option is 32, and its length is 4. |
| 806 |
|
| 807 |
Code Len Address |
| 808 |
+-----+-----+-----+-----+-----+-----+ |
| 809 |
| 32 | 4 | a1 | a2 | a3 | a4 | |
| 810 |
+-----+-----+-----+-----+-----+-----+ |
| 811 |
|
| 812 |
<span class="h3"><a class="selflink" id="section-5.8" href="#section-5.8">5.8</a>. Static Route Option</span> |
| 813 |
|
| 814 |
This option specifies a list of static routes that the client should |
| 815 |
install in its routing cache. If multiple routes to the same |
| 816 |
destination are specified, they are listed in descending order of |
| 817 |
priority. |
| 818 |
|
| 819 |
The routes consist of a list of IP address pairs. The first address |
| 820 |
is the destination address, and the second address is the router for |
| 821 |
the destination. |
| 822 |
|
| 823 |
The default route (0.0.0.0) is an illegal destination for a static |
| 824 |
route. See <a href="#section-3.5">section 3.5</a> for information about the router option. |
| 825 |
|
| 826 |
The code for this option is 33. The minimum length of this option is |
| 827 |
8, and the length MUST be a multiple of 8. |
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Alexander & Droms Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 839 |
|
| 840 |
|
| 841 |
Code Len Destination 1 Router 1 |
| 842 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+ |
| 843 |
| 33 | n | d1 | d2 | d3 | d4 | r1 | r2 | r3 | r4 | |
| 844 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+ |
| 845 |
Destination 2 Router 2 |
| 846 |
+-----+-----+-----+-----+-----+-----+-----+-----+--- |
| 847 |
| d1 | d2 | d3 | d4 | r1 | r2 | r3 | r4 | ... |
| 848 |
+-----+-----+-----+-----+-----+-----+-----+-----+--- |
| 849 |
|
| 850 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Link Layer Parameters per Interface</span> |
| 851 |
|
| 852 |
This section lists the options that affect the operation of the data |
| 853 |
link layer on a per-interface basis. |
| 854 |
|
| 855 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Trailer Encapsulation Option</span> |
| 856 |
|
| 857 |
This option specifies whether or not the client should negotiate the |
| 858 |
use of trailers (<a href="./rfc893">RFC 893</a> [<a href="#ref-14" title=""Trailer Encapsulations"">14</a>]) when using the ARP protocol. A value |
| 859 |
of 0 indicates that the client should not attempt to use trailers. A |
| 860 |
value of 1 means that the client should attempt to use trailers. |
| 861 |
|
| 862 |
The code for this option is 34, and its length is 1. |
| 863 |
|
| 864 |
Code Len Value |
| 865 |
+-----+-----+-----+ |
| 866 |
| 34 | 1 | 0/1 | |
| 867 |
+-----+-----+-----+ |
| 868 |
|
| 869 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. ARP Cache Timeout Option</span> |
| 870 |
|
| 871 |
This option specifies the timeout in seconds for ARP cache entries. |
| 872 |
The time is specified as a 32-bit unsigned integer. |
| 873 |
|
| 874 |
The code for this option is 35, and its length is 4. |
| 875 |
|
| 876 |
Code Len Time |
| 877 |
+-----+-----+-----+-----+-----+-----+ |
| 878 |
| 35 | 4 | t1 | t2 | t3 | t4 | |
| 879 |
+-----+-----+-----+-----+-----+-----+ |
| 880 |
|
| 881 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Ethernet Encapsulation Option</span> |
| 882 |
|
| 883 |
This option specifies whether or not the client should use Ethernet |
| 884 |
Version 2 (<a href="./rfc894">RFC 894</a> [<a href="#ref-15" title=""Standard for the Transmission of IP Datagrams over Ethernet Networks"">15</a>]) or IEEE 802.3 (<a href="./rfc1042">RFC 1042</a> [<a href="#ref-16" title=""Standard for the Transmission of IP Datagrams Over IEEE 802 Networks"">16</a>]) encapsulation |
| 885 |
if the interface is an Ethernet. A value of 0 indicates that the |
| 886 |
client should use <a href="./rfc894">RFC 894</a> encapsulation. A value of 1 means that the |
| 887 |
client should use <a href="./rfc1042">RFC 1042</a> encapsulation. |
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Alexander & Droms Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 895 |
|
| 896 |
|
| 897 |
The code for this option is 36, and its length is 1. |
| 898 |
|
| 899 |
Code Len Value |
| 900 |
+-----+-----+-----+ |
| 901 |
| 36 | 1 | 0/1 | |
| 902 |
+-----+-----+-----+ |
| 903 |
|
| 904 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. TCP Parameters</span> |
| 905 |
|
| 906 |
This section lists the options that affect the operation of the TCP |
| 907 |
layer on a per-interface basis. |
| 908 |
|
| 909 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. TCP Default TTL Option</span> |
| 910 |
|
| 911 |
This option specifies the default TTL that the client should use when |
| 912 |
sending TCP segments. The value is represented as an 8-bit unsigned |
| 913 |
integer. The minimum value is 1. |
| 914 |
|
| 915 |
The code for this option is 37, and its length is 1. |
| 916 |
|
| 917 |
Code Len TTL |
| 918 |
+-----+-----+-----+ |
| 919 |
| 37 | 1 | n | |
| 920 |
+-----+-----+-----+ |
| 921 |
|
| 922 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. TCP Keepalive Interval Option</span> |
| 923 |
|
| 924 |
This option specifies the interval (in seconds) that the client TCP |
| 925 |
should wait before sending a keepalive message on a TCP connection. |
| 926 |
The time is specified as a 32-bit unsigned integer. A value of zero |
| 927 |
indicates that the client should not generate keepalive messages on |
| 928 |
connections unless specifically requested by an application. |
| 929 |
|
| 930 |
The code for this option is 38, and its length is 4. |
| 931 |
|
| 932 |
Code Len Time |
| 933 |
+-----+-----+-----+-----+-----+-----+ |
| 934 |
| 38 | 4 | t1 | t2 | t3 | t4 | |
| 935 |
+-----+-----+-----+-----+-----+-----+ |
| 936 |
|
| 937 |
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. TCP Keepalive Garbage Option</span> |
| 938 |
|
| 939 |
This option specifies the whether or not the client should send TCP |
| 940 |
keepalive messages with a octet of garbage for compatibility with |
| 941 |
older implementations. A value of 0 indicates that a garbage octet |
| 942 |
should not be sent. A value of 1 indicates that a garbage octet |
| 943 |
should be sent. |
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Alexander & Droms Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 951 |
|
| 952 |
|
| 953 |
The code for this option is 39, and its length is 1. |
| 954 |
|
| 955 |
Code Len Value |
| 956 |
+-----+-----+-----+ |
| 957 |
| 39 | 1 | 0/1 | |
| 958 |
+-----+-----+-----+ |
| 959 |
|
| 960 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Application and Service Parameters</span> |
| 961 |
|
| 962 |
This section details some miscellaneous options used to configure |
| 963 |
miscellaneous applications and services. |
| 964 |
|
| 965 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Network Information Service Domain Option</span> |
| 966 |
|
| 967 |
This option specifies the name of the client's NIS [<a href="#ref-17" title=""System and Network Administration"">17</a>] domain. The |
| 968 |
domain is formatted as a character string consisting of characters |
| 969 |
from the NVT ASCII character set. |
| 970 |
|
| 971 |
The code for this option is 40. Its minimum length is 1. |
| 972 |
|
| 973 |
Code Len NIS Domain Name |
| 974 |
+-----+-----+-----+-----+-----+-----+--- |
| 975 |
| 40 | n | n1 | n2 | n3 | n4 | ... |
| 976 |
+-----+-----+-----+-----+-----+-----+--- |
| 977 |
|
| 978 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Network Information Servers Option</span> |
| 979 |
|
| 980 |
This option specifies a list of IP addresses indicating NIS servers |
| 981 |
available to the client. Servers SHOULD be listed in order of |
| 982 |
preference. |
| 983 |
|
| 984 |
The code for this option is 41. Its minimum length is 4, and the |
| 985 |
length MUST be a multiple of 4. |
| 986 |
|
| 987 |
Code Len Address 1 Address 2 |
| 988 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 989 |
| 41 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 990 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 991 |
|
| 992 |
<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Network Time Protocol Servers Option</span> |
| 993 |
|
| 994 |
This option specifies a list of IP addresses indicating NTP [<a href="#ref-18" title=""Internet Time Synchronization: The Network Time Protocol"">18</a>] |
| 995 |
servers available to the client. Servers SHOULD be listed in order |
| 996 |
of preference. |
| 997 |
|
| 998 |
The code for this option is 42. Its minimum length is 4, and the |
| 999 |
length MUST be a multiple of 4. |
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Alexander & Droms Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
Code Len Address 1 Address 2 |
| 1010 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1011 |
| 42 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1012 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1013 |
|
| 1014 |
<span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a>. Vendor Specific Information</span> |
| 1015 |
|
| 1016 |
This option is used by clients and servers to exchange vendor- |
| 1017 |
specific information. The information is an opaque object of n |
| 1018 |
octets, presumably interpreted by vendor-specific code on the clients |
| 1019 |
and servers. The definition of this information is vendor specific. |
| 1020 |
The vendor is indicated in the vendor class identifier option. |
| 1021 |
Servers not equipped to interpret the vendor-specific information |
| 1022 |
sent by a client MUST ignore it (although it may be reported). |
| 1023 |
Clients which do not receive desired vendor-specific information |
| 1024 |
SHOULD make an attempt to operate without it, although they may do so |
| 1025 |
(and announce they are doing so) in a degraded mode. |
| 1026 |
|
| 1027 |
If a vendor potentially encodes more than one item of information in |
| 1028 |
this option, then the vendor SHOULD encode the option using |
| 1029 |
"Encapsulated vendor-specific options" as described below: |
| 1030 |
|
| 1031 |
The Encapsulated vendor-specific options field SHOULD be encoded as a |
| 1032 |
sequence of code/length/value fields of identical syntax to the DHCP |
| 1033 |
options field with the following exceptions: |
| 1034 |
|
| 1035 |
1) There SHOULD NOT be a "magic cookie" field in the encapsulated |
| 1036 |
vendor-specific extensions field. |
| 1037 |
|
| 1038 |
2) Codes other than 0 or 255 MAY be redefined by the vendor within |
| 1039 |
the encapsulated vendor-specific extensions field, but SHOULD |
| 1040 |
conform to the tag-length-value syntax defined in <a href="#section-2">section 2</a>. |
| 1041 |
|
| 1042 |
3) Code 255 (END), if present, signifies the end of the |
| 1043 |
encapsulated vendor extensions, not the end of the vendor |
| 1044 |
extensions field. If no code 255 is present, then the end of |
| 1045 |
the enclosing vendor-specific information field is taken as the |
| 1046 |
end of the encapsulated vendor-specific extensions field. |
| 1047 |
|
| 1048 |
The code for this option is 43 and its minimum length is 1. |
| 1049 |
|
| 1050 |
Code Len Vendor-specific information |
| 1051 |
+-----+-----+-----+-----+--- |
| 1052 |
| 43 | n | i1 | i2 | ... |
| 1053 |
+-----+-----+-----+-----+--- |
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Alexander & Droms Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
When encapsulated vendor-specific extensions are used, the |
| 1066 |
information bytes 1-n have the following format: |
| 1067 |
|
| 1068 |
Code Len Data item Code Len Data item Code |
| 1069 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+ |
| 1070 |
| T1 | n | d1 | d2 | ... | T2 | n | D1 | D2 | ... | ... | |
| 1071 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+ |
| 1072 |
|
| 1073 |
<span class="h3"><a class="selflink" id="section-8.5" href="#section-8.5">8.5</a>. NetBIOS over TCP/IP Name Server Option</span> |
| 1074 |
|
| 1075 |
The NetBIOS name server (NBNS) option specifies a list of <a href="./rfc1001">RFC</a> |
| 1076 |
<a href="./rfc1001">1001</a>/1002 [<a href="#ref-19" title=""Protocol Standard for a NetBIOS Service on a TCP/UDP transport: Concepts and Methods"">19</a>] [<a href="#ref-20" title=""Protocol Standard for a NetBIOS Service on a TCP/UDP transport: Detailed Specifications"">20</a>] NBNS name servers listed in order of preference. |
| 1077 |
|
| 1078 |
The code for this option is 44. The minimum length of the option is |
| 1079 |
4 octets, and the length must always be a multiple of 4. |
| 1080 |
|
| 1081 |
Code Len Address 1 Address 2 |
| 1082 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+---- |
| 1083 |
| 44 | n | a1 | a2 | a3 | a4 | b1 | b2 | b3 | b4 | ... |
| 1084 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+---- |
| 1085 |
|
| 1086 |
<span class="h3"><a class="selflink" id="section-8.6" href="#section-8.6">8.6</a>. NetBIOS over TCP/IP Datagram Distribution Server Option</span> |
| 1087 |
|
| 1088 |
The NetBIOS datagram distribution server (NBDD) option specifies a |
| 1089 |
list of <a href="./rfc1001">RFC 1001</a>/1002 NBDD servers listed in order of preference. The |
| 1090 |
code for this option is 45. The minimum length of the option is 4 |
| 1091 |
octets, and the length must always be a multiple of 4. |
| 1092 |
|
| 1093 |
Code Len Address 1 Address 2 |
| 1094 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+---- |
| 1095 |
| 45 | n | a1 | a2 | a3 | a4 | b1 | b2 | b3 | b4 | ... |
| 1096 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+---- |
| 1097 |
|
| 1098 |
<span class="h3"><a class="selflink" id="section-8.7" href="#section-8.7">8.7</a>. NetBIOS over TCP/IP Node Type Option</span> |
| 1099 |
|
| 1100 |
The NetBIOS node type option allows NetBIOS over TCP/IP clients which |
| 1101 |
are configurable to be configured as described in <a href="./rfc1001">RFC 1001</a>/1002. The |
| 1102 |
value is specified as a single octet which identifies the client type |
| 1103 |
as follows: |
| 1104 |
|
| 1105 |
Value Node Type |
| 1106 |
----- --------- |
| 1107 |
0x1 B-node |
| 1108 |
0x2 P-node |
| 1109 |
0x4 M-node |
| 1110 |
0x8 H-node |
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Alexander & Droms Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
In the above chart, the notation '0x' indicates a number in base-16 |
| 1122 |
(hexadecimal). |
| 1123 |
|
| 1124 |
The code for this option is 46. The length of this option is always |
| 1125 |
1. |
| 1126 |
|
| 1127 |
Code Len Node Type |
| 1128 |
+-----+-----+-----------+ |
| 1129 |
| 46 | 1 | see above | |
| 1130 |
+-----+-----+-----------+ |
| 1131 |
|
| 1132 |
<span class="h3"><a class="selflink" id="section-8.8" href="#section-8.8">8.8</a>. NetBIOS over TCP/IP Scope Option</span> |
| 1133 |
|
| 1134 |
The NetBIOS scope option specifies the NetBIOS over TCP/IP scope |
| 1135 |
parameter for the client as specified in <a href="./rfc1001">RFC 1001</a>/1002. See [<a href="#ref-19" title=""Protocol Standard for a NetBIOS Service on a TCP/UDP transport: Concepts and Methods"">19</a>], |
| 1136 |
[<a href="#ref-20" title=""Protocol Standard for a NetBIOS Service on a TCP/UDP transport: Detailed Specifications"">20</a>], and [<a href="#ref-8" title=""Domain Names - Implementation and Specification"">8</a>] for character-set restrictions. |
| 1137 |
|
| 1138 |
The code for this option is 47. The minimum length of this option is |
| 1139 |
1. |
| 1140 |
|
| 1141 |
Code Len NetBIOS Scope |
| 1142 |
+-----+-----+-----+-----+-----+-----+---- |
| 1143 |
| 47 | n | s1 | s2 | s3 | s4 | ... |
| 1144 |
+-----+-----+-----+-----+-----+-----+---- |
| 1145 |
|
| 1146 |
<span class="h3"><a class="selflink" id="section-8.9" href="#section-8.9">8.9</a>. X Window System Font Server Option</span> |
| 1147 |
|
| 1148 |
This option specifies a list of X Window System [<a href="#ref-21" title=""FYI On the X Window System"">21</a>] Font servers |
| 1149 |
available to the client. Servers SHOULD be listed in order of |
| 1150 |
preference. |
| 1151 |
|
| 1152 |
The code for this option is 48. The minimum length of this option is |
| 1153 |
4 octets, and the length MUST be a multiple of 4. |
| 1154 |
|
| 1155 |
Code Len Address 1 Address 2 |
| 1156 |
+-----+-----+-----+-----+-----+-----+-----+-----+--- |
| 1157 |
| 48 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1158 |
+-----+-----+-----+-----+-----+-----+-----+-----+--- |
| 1159 |
|
| 1160 |
<span class="h3"><a class="selflink" id="section-8.10" href="#section-8.10">8.10</a>. X Window System Display Manager Option</span> |
| 1161 |
|
| 1162 |
This option specifies a list of IP addresses of systems that are |
| 1163 |
running the X Window System Display Manager and are available to the |
| 1164 |
client. |
| 1165 |
|
| 1166 |
Addresses SHOULD be listed in order of preference. |
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Alexander & Droms Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
The code for the this option is 49. The minimum length of this option |
| 1178 |
is 4, and the length MUST be a multiple of 4. |
| 1179 |
|
| 1180 |
Code Len Address 1 Address 2 |
| 1181 |
|
| 1182 |
+-----+-----+-----+-----+-----+-----+-----+-----+--- |
| 1183 |
| 49 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1184 |
+-----+-----+-----+-----+-----+-----+-----+-----+--- |
| 1185 |
|
| 1186 |
<span class="h3"><a class="selflink" id="section-8.11" href="#section-8.11">8.11</a>. Network Information Service+ Domain Option</span> |
| 1187 |
|
| 1188 |
This option specifies the name of the client's NIS+ [<a href="#ref-17" title=""System and Network Administration"">17</a>] domain. The |
| 1189 |
domain is formatted as a character string consisting of characters |
| 1190 |
from the NVT ASCII character set. |
| 1191 |
|
| 1192 |
The code for this option is 64. Its minimum length is 1. |
| 1193 |
|
| 1194 |
Code Len NIS Client Domain Name |
| 1195 |
+-----+-----+-----+-----+-----+-----+--- |
| 1196 |
| 64 | n | n1 | n2 | n3 | n4 | ... |
| 1197 |
+-----+-----+-----+-----+-----+-----+--- |
| 1198 |
|
| 1199 |
<span class="h3"><a class="selflink" id="section-8.12" href="#section-8.12">8.12</a>. Network Information Service+ Servers Option</span> |
| 1200 |
|
| 1201 |
This option specifies a list of IP addresses indicating NIS+ servers |
| 1202 |
available to the client. Servers SHOULD be listed in order of |
| 1203 |
preference. |
| 1204 |
|
| 1205 |
The code for this option is 65. Its minimum length is 4, and the |
| 1206 |
length MUST be a multiple of 4. |
| 1207 |
|
| 1208 |
Code Len Address 1 Address 2 |
| 1209 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1210 |
| 65 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1211 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1212 |
|
| 1213 |
<span class="h3"><a class="selflink" id="section-8.13" href="#section-8.13">8.13</a>. Mobile IP Home Agent option</span> |
| 1214 |
|
| 1215 |
This option specifies a list of IP addresses indicating mobile IP |
| 1216 |
home agents available to the client. Agents SHOULD be listed in |
| 1217 |
order of preference. |
| 1218 |
|
| 1219 |
The code for this option is 68. Its minimum length is 0 (indicating |
| 1220 |
no home agents are available) and the length MUST be a multiple of 4. |
| 1221 |
It is expected that the usual length will be four octets, containing |
| 1222 |
a single home agent's address. |
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Alexander & Droms Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
Code Len Home Agent Addresses (zero or more) |
| 1234 |
+-----+-----+-----+-----+-----+-----+-- |
| 1235 |
| 68 | n | a1 | a2 | a3 | a4 | ... |
| 1236 |
+-----+-----+-----+-----+-----+-----+-- |
| 1237 |
|
| 1238 |
<span class="h3"><a class="selflink" id="section-8.14" href="#section-8.14">8.14</a>. Simple Mail Transport Protocol (SMTP) Server Option</span> |
| 1239 |
|
| 1240 |
The SMTP server option specifies a list of SMTP servers available to |
| 1241 |
the client. Servers SHOULD be listed in order of preference. |
| 1242 |
|
| 1243 |
The code for the SMTP server option is 69. The minimum length for |
| 1244 |
this option is 4 octets, and the length MUST always be a multiple of |
| 1245 |
4. |
| 1246 |
|
| 1247 |
Code Len Address 1 Address 2 |
| 1248 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1249 |
| 69 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1250 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1251 |
|
| 1252 |
<span class="h3"><a class="selflink" id="section-8.15" href="#section-8.15">8.15</a>. Post Office Protocol (POP3) Server Option</span> |
| 1253 |
|
| 1254 |
The POP3 server option specifies a list of POP3 available to the |
| 1255 |
client. Servers SHOULD be listed in order of preference. |
| 1256 |
|
| 1257 |
The code for the POP3 server option is 70. The minimum length for |
| 1258 |
this option is 4 octets, and the length MUST always be a multiple of |
| 1259 |
4. |
| 1260 |
|
| 1261 |
Code Len Address 1 Address 2 |
| 1262 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1263 |
| 70 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1264 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1265 |
|
| 1266 |
<span class="h3"><a class="selflink" id="section-8.16" href="#section-8.16">8.16</a>. Network News Transport Protocol (NNTP) Server Option</span> |
| 1267 |
|
| 1268 |
The NNTP server option specifies a list of NNTP available to the |
| 1269 |
client. Servers SHOULD be listed in order of preference. |
| 1270 |
|
| 1271 |
The code for the NNTP server option is 71. The minimum length for |
| 1272 |
this option is 4 octets, and the length MUST always be a multiple of |
| 1273 |
4. |
| 1274 |
|
| 1275 |
Code Len Address 1 Address 2 |
| 1276 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1277 |
| 71 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1278 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Alexander & Droms Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
<span class="h3"><a class="selflink" id="section-8.17" href="#section-8.17">8.17</a>. Default World Wide Web (WWW) Server Option</span> |
| 1290 |
|
| 1291 |
The WWW server option specifies a list of WWW available to the |
| 1292 |
client. Servers SHOULD be listed in order of preference. |
| 1293 |
|
| 1294 |
The code for the WWW server option is 72. The minimum length for |
| 1295 |
this option is 4 octets, and the length MUST always be a multiple of |
| 1296 |
4. |
| 1297 |
|
| 1298 |
Code Len Address 1 Address 2 |
| 1299 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1300 |
| 72 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1301 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1302 |
|
| 1303 |
<span class="h3"><a class="selflink" id="section-8.18" href="#section-8.18">8.18</a>. Default Finger Server Option</span> |
| 1304 |
|
| 1305 |
The Finger server option specifies a list of Finger available to the |
| 1306 |
client. Servers SHOULD be listed in order of preference. |
| 1307 |
|
| 1308 |
The code for the Finger server option is 73. The minimum length for |
| 1309 |
this option is 4 octets, and the length MUST always be a multiple of |
| 1310 |
4. |
| 1311 |
|
| 1312 |
Code Len Address 1 Address 2 |
| 1313 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1314 |
| 73 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1315 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1316 |
|
| 1317 |
<span class="h3"><a class="selflink" id="section-8.19" href="#section-8.19">8.19</a>. Default Internet Relay Chat (IRC) Server Option</span> |
| 1318 |
|
| 1319 |
The IRC server option specifies a list of IRC available to the |
| 1320 |
client. Servers SHOULD be listed in order of preference. |
| 1321 |
|
| 1322 |
The code for the IRC server option is 74. The minimum length for |
| 1323 |
this option is 4 octets, and the length MUST always be a multiple of |
| 1324 |
4. |
| 1325 |
|
| 1326 |
Code Len Address 1 Address 2 |
| 1327 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1328 |
| 74 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1329 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1330 |
|
| 1331 |
<span class="h3"><a class="selflink" id="section-8.20" href="#section-8.20">8.20</a>. StreetTalk Server Option</span> |
| 1332 |
|
| 1333 |
The StreetTalk server option specifies a list of StreetTalk servers |
| 1334 |
available to the client. Servers SHOULD be listed in order of |
| 1335 |
preference. |
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Alexander & Droms Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
The code for the StreetTalk server option is 75. The minimum length |
| 1346 |
for this option is 4 octets, and the length MUST always be a multiple |
| 1347 |
of 4. |
| 1348 |
|
| 1349 |
Code Len Address 1 Address 2 |
| 1350 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1351 |
| 75 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1352 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1353 |
|
| 1354 |
<span class="h3"><a class="selflink" id="section-8.21" href="#section-8.21">8.21</a>. StreetTalk Directory Assistance (STDA) Server Option</span> |
| 1355 |
|
| 1356 |
The StreetTalk Directory Assistance (STDA) server option specifies a |
| 1357 |
list of STDA servers available to the client. Servers SHOULD be |
| 1358 |
listed in order of preference. |
| 1359 |
|
| 1360 |
The code for the StreetTalk Directory Assistance server option is 76. |
| 1361 |
The minimum length for this option is 4 octets, and the length MUST |
| 1362 |
always be a multiple of 4. |
| 1363 |
|
| 1364 |
Code Len Address 1 Address 2 |
| 1365 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1366 |
| 76 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... |
| 1367 |
+-----+-----+-----+-----+-----+-----+-----+-----+-- |
| 1368 |
|
| 1369 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. DHCP Extensions</span> |
| 1370 |
|
| 1371 |
This section details the options that are specific to DHCP. |
| 1372 |
|
| 1373 |
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Requested IP Address</span> |
| 1374 |
|
| 1375 |
This option is used in a client request (DHCPDISCOVER) to allow the |
| 1376 |
client to request that a particular IP address be assigned. |
| 1377 |
|
| 1378 |
The code for this option is 50, and its length is 4. |
| 1379 |
|
| 1380 |
Code Len Address |
| 1381 |
+-----+-----+-----+-----+-----+-----+ |
| 1382 |
| 50 | 4 | a1 | a2 | a3 | a4 | |
| 1383 |
+-----+-----+-----+-----+-----+-----+ |
| 1384 |
|
| 1385 |
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. IP Address Lease Time</span> |
| 1386 |
|
| 1387 |
This option is used in a client request (DHCPDISCOVER or DHCPREQUEST) |
| 1388 |
to allow the client to request a lease time for the IP address. In a |
| 1389 |
server reply (DHCPOFFER), a DHCP server uses this option to specify |
| 1390 |
the lease time it is willing to offer. |
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Alexander & Droms Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
The time is in units of seconds, and is specified as a 32-bit |
| 1402 |
unsigned integer. |
| 1403 |
|
| 1404 |
The code for this option is 51, and its length is 4. |
| 1405 |
|
| 1406 |
Code Len Lease Time |
| 1407 |
+-----+-----+-----+-----+-----+-----+ |
| 1408 |
| 51 | 4 | t1 | t2 | t3 | t4 | |
| 1409 |
+-----+-----+-----+-----+-----+-----+ |
| 1410 |
|
| 1411 |
<span class="h3"><a class="selflink" id="section-9.3" href="#section-9.3">9.3</a>. Option Overload</span> |
| 1412 |
|
| 1413 |
This option is used to indicate that the DHCP 'sname' or 'file' |
| 1414 |
fields are being overloaded by using them to carry DHCP options. A |
| 1415 |
DHCP server inserts this option if the returned parameters will |
| 1416 |
exceed the usual space allotted for options. |
| 1417 |
|
| 1418 |
If this option is present, the client interprets the specified |
| 1419 |
additional fields after it concludes interpretation of the standard |
| 1420 |
option fields. |
| 1421 |
|
| 1422 |
The code for this option is 52, and its length is 1. Legal values |
| 1423 |
for this option are: |
| 1424 |
|
| 1425 |
Value Meaning |
| 1426 |
----- -------- |
| 1427 |
1 the 'file' field is used to hold options |
| 1428 |
2 the 'sname' field is used to hold options |
| 1429 |
3 both fields are used to hold options |
| 1430 |
|
| 1431 |
Code Len Value |
| 1432 |
+-----+-----+-----+ |
| 1433 |
| 52 | 1 |1/2/3| |
| 1434 |
+-----+-----+-----+ |
| 1435 |
|
| 1436 |
<span class="h3"><a class="selflink" id="section-9.4" href="#section-9.4">9.4</a> TFTP server name</span> |
| 1437 |
|
| 1438 |
This option is used to identify a TFTP server when the 'sname' field |
| 1439 |
in the DHCP header has been used for DHCP options. |
| 1440 |
|
| 1441 |
The code for this option is 66, and its minimum length is 1. |
| 1442 |
|
| 1443 |
Code Len TFTP server |
| 1444 |
+-----+-----+-----+-----+-----+--- |
| 1445 |
| 66 | n | c1 | c2 | c3 | ... |
| 1446 |
+-----+-----+-----+-----+-----+--- |
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Alexander & Droms Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
<span class="h3"><a class="selflink" id="section-9.5" href="#section-9.5">9.5</a> Bootfile name</span> |
| 1458 |
|
| 1459 |
This option is used to identify a bootfile when the 'file' field in |
| 1460 |
the DHCP header has been used for DHCP options. |
| 1461 |
|
| 1462 |
The code for this option is 67, and its minimum length is 1. |
| 1463 |
|
| 1464 |
Code Len Bootfile name |
| 1465 |
+-----+-----+-----+-----+-----+--- |
| 1466 |
| 67 | n | c1 | c2 | c3 | ... |
| 1467 |
+-----+-----+-----+-----+-----+--- |
| 1468 |
|
| 1469 |
<span class="h3"><a class="selflink" id="section-9.6" href="#section-9.6">9.6</a>. DHCP Message Type</span> |
| 1470 |
|
| 1471 |
This option is used to convey the type of the DHCP message. The code |
| 1472 |
for this option is 53, and its length is 1. Legal values for this |
| 1473 |
option are: |
| 1474 |
|
| 1475 |
Value Message Type |
| 1476 |
----- ------------ |
| 1477 |
1 DHCPDISCOVER |
| 1478 |
2 DHCPOFFER |
| 1479 |
3 DHCPREQUEST |
| 1480 |
4 DHCPDECLINE |
| 1481 |
5 DHCPACK |
| 1482 |
6 DHCPNAK |
| 1483 |
7 DHCPRELEASE |
| 1484 |
8 DHCPINFORM |
| 1485 |
|
| 1486 |
Code Len Type |
| 1487 |
+-----+-----+-----+ |
| 1488 |
| 53 | 1 | 1-9 | |
| 1489 |
+-----+-----+-----+ |
| 1490 |
|
| 1491 |
<span class="h3"><a class="selflink" id="section-9.7" href="#section-9.7">9.7</a>. Server Identifier</span> |
| 1492 |
|
| 1493 |
This option is used in DHCPOFFER and DHCPREQUEST messages, and may |
| 1494 |
optionally be included in the DHCPACK and DHCPNAK messages. DHCP |
| 1495 |
servers include this option in the DHCPOFFER in order to allow the |
| 1496 |
client to distinguish between lease offers. DHCP clients use the |
| 1497 |
contents of the 'server identifier' field as the destination address |
| 1498 |
for any DHCP messages unicast to the DHCP server. DHCP clients also |
| 1499 |
indicate which of several lease offers is being accepted by including |
| 1500 |
this option in a DHCPREQUEST message. |
| 1501 |
|
| 1502 |
The identifier is the IP address of the selected server. |
| 1503 |
|
| 1504 |
The code for this option is 54, and its length is 4. |
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Alexander & Droms Standards Track [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
Code Len Address |
| 1514 |
+-----+-----+-----+-----+-----+-----+ |
| 1515 |
| 54 | 4 | a1 | a2 | a3 | a4 | |
| 1516 |
+-----+-----+-----+-----+-----+-----+ |
| 1517 |
|
| 1518 |
<span class="h3"><a class="selflink" id="section-9.8" href="#section-9.8">9.8</a>. Parameter Request List</span> |
| 1519 |
|
| 1520 |
This option is used by a DHCP client to request values for specified |
| 1521 |
configuration parameters. The list of requested parameters is |
| 1522 |
specified as n octets, where each octet is a valid DHCP option code |
| 1523 |
as defined in this document. |
| 1524 |
|
| 1525 |
The client MAY list the options in order of preference. The DHCP |
| 1526 |
server is not required to return the options in the requested order, |
| 1527 |
but MUST try to insert the requested options in the order requested |
| 1528 |
by the client. |
| 1529 |
|
| 1530 |
The code for this option is 55. Its minimum length is 1. |
| 1531 |
|
| 1532 |
Code Len Option Codes |
| 1533 |
+-----+-----+-----+-----+--- |
| 1534 |
| 55 | n | c1 | c2 | ... |
| 1535 |
+-----+-----+-----+-----+--- |
| 1536 |
|
| 1537 |
<span class="h3"><a class="selflink" id="section-9.9" href="#section-9.9">9.9</a>. Message</span> |
| 1538 |
|
| 1539 |
This option is used by a DHCP server to provide an error message to a |
| 1540 |
DHCP client in a DHCPNAK message in the event of a failure. A client |
| 1541 |
may use this option in a DHCPDECLINE message to indicate the why the |
| 1542 |
client declined the offered parameters. The message consists of n |
| 1543 |
octets of NVT ASCII text, which the client may display on an |
| 1544 |
available output device. |
| 1545 |
|
| 1546 |
The code for this option is 56 and its minimum length is 1. |
| 1547 |
|
| 1548 |
Code Len Text |
| 1549 |
+-----+-----+-----+-----+--- |
| 1550 |
| 56 | n | c1 | c2 | ... |
| 1551 |
+-----+-----+-----+-----+--- |
| 1552 |
|
| 1553 |
<span class="h3"><a class="selflink" id="section-9.10" href="#section-9.10">9.10</a>. Maximum DHCP Message Size</span> |
| 1554 |
|
| 1555 |
This option specifies the maximum length DHCP message that it is |
| 1556 |
willing to accept. The length is specified as an unsigned 16-bit |
| 1557 |
integer. A client may use the maximum DHCP message size option in |
| 1558 |
DHCPDISCOVER or DHCPREQUEST messages, but should not use the option |
| 1559 |
in DHCPDECLINE messages. |
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Alexander & Droms Standards Track [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
The code for this option is 57, and its length is 2. The minimum |
| 1570 |
legal value is 576 octets. |
| 1571 |
|
| 1572 |
Code Len Length |
| 1573 |
+-----+-----+-----+-----+ |
| 1574 |
| 57 | 2 | l1 | l2 | |
| 1575 |
+-----+-----+-----+-----+ |
| 1576 |
|
| 1577 |
<span class="h3"><a class="selflink" id="section-9.11" href="#section-9.11">9.11</a>. Renewal (T1) Time Value</span> |
| 1578 |
|
| 1579 |
This option specifies the time interval from address assignment until |
| 1580 |
the client transitions to the RENEWING state. |
| 1581 |
|
| 1582 |
The value is in units of seconds, and is specified as a 32-bit |
| 1583 |
unsigned integer. |
| 1584 |
|
| 1585 |
The code for this option is 58, and its length is 4. |
| 1586 |
|
| 1587 |
Code Len T1 Interval |
| 1588 |
+-----+-----+-----+-----+-----+-----+ |
| 1589 |
| 58 | 4 | t1 | t2 | t3 | t4 | |
| 1590 |
+-----+-----+-----+-----+-----+-----+ |
| 1591 |
|
| 1592 |
<span class="h3"><a class="selflink" id="section-9.12" href="#section-9.12">9.12</a>. Rebinding (T2) Time Value</span> |
| 1593 |
|
| 1594 |
This option specifies the time interval from address assignment until |
| 1595 |
the client transitions to the REBINDING state. |
| 1596 |
|
| 1597 |
The value is in units of seconds, and is specified as a 32-bit |
| 1598 |
unsigned integer. |
| 1599 |
|
| 1600 |
The code for this option is 59, and its length is 4. |
| 1601 |
|
| 1602 |
Code Len T2 Interval |
| 1603 |
+-----+-----+-----+-----+-----+-----+ |
| 1604 |
| 59 | 4 | t1 | t2 | t3 | t4 | |
| 1605 |
+-----+-----+-----+-----+-----+-----+ |
| 1606 |
|
| 1607 |
<span class="h3"><a class="selflink" id="section-9.13" href="#section-9.13">9.13</a>. Vendor class identifier</span> |
| 1608 |
|
| 1609 |
This option is used by DHCP clients to optionally identify the vendor |
| 1610 |
type and configuration of a DHCP client. The information is a string |
| 1611 |
of n octets, interpreted by servers. Vendors may choose to define |
| 1612 |
specific vendor class identifiers to convey particular configuration |
| 1613 |
or other identification information about a client. For example, the |
| 1614 |
identifier may encode the client's hardware configuration. Servers |
| 1615 |
not equipped to interpret the class-specific information sent by a |
| 1616 |
client MUST ignore it (although it may be reported). Servers that |
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Alexander & Droms Standards Track [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
respond SHOULD only use option 43 to return the vendor-specific |
| 1626 |
information to the client. |
| 1627 |
|
| 1628 |
The code for this option is 60, and its minimum length is 1. |
| 1629 |
|
| 1630 |
Code Len Vendor class Identifier |
| 1631 |
+-----+-----+-----+-----+--- |
| 1632 |
| 60 | n | i1 | i2 | ... |
| 1633 |
+-----+-----+-----+-----+--- |
| 1634 |
|
| 1635 |
<span class="h3"><a class="selflink" id="section-9.14" href="#section-9.14">9.14</a>. Client-identifier</span> |
| 1636 |
|
| 1637 |
This option is used by DHCP clients to specify their unique |
| 1638 |
identifier. DHCP servers use this value to index their database of |
| 1639 |
address bindings. This value is expected to be unique for all |
| 1640 |
clients in an administrative domain. |
| 1641 |
|
| 1642 |
Identifiers SHOULD be treated as opaque objects by DHCP servers. |
| 1643 |
|
| 1644 |
The client identifier MAY consist of type-value pairs similar to the |
| 1645 |
'htype'/'chaddr' fields defined in [<a href="#ref-3" title=""Bootstrap Protocol"">3</a>]. For instance, it MAY consist |
| 1646 |
of a hardware type and hardware address. In this case the type field |
| 1647 |
SHOULD be one of the ARP hardware types defined in STD2 [<a href="#ref-22" title=""Assigned Numbers"">22</a>]. A |
| 1648 |
hardware type of 0 (zero) should be used when the value field |
| 1649 |
contains an identifier other than a hardware address (e.g. a fully |
| 1650 |
qualified domain name). |
| 1651 |
|
| 1652 |
For correct identification of clients, each client's client- |
| 1653 |
identifier MUST be unique among the client-identifiers used on the |
| 1654 |
subnet to which the client is attached. Vendors and system |
| 1655 |
administrators are responsible for choosing client-identifiers that |
| 1656 |
meet this requirement for uniqueness. |
| 1657 |
|
| 1658 |
The code for this option is 61, and its minimum length is 2. |
| 1659 |
|
| 1660 |
Code Len Type Client-Identifier |
| 1661 |
+-----+-----+-----+-----+-----+--- |
| 1662 |
| 61 | n | t1 | i1 | i2 | ... |
| 1663 |
+-----+-----+-----+-----+-----+--- |
| 1664 |
|
| 1665 |
|
| 1666 |
|
| 1667 |
|
| 1668 |
|
| 1669 |
|
| 1670 |
|
| 1671 |
|
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Alexander & Droms Standards Track [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Defining new extensions</span> |
| 1682 |
|
| 1683 |
The author of a new DHCP option will follow these steps to obtain |
| 1684 |
acceptance of the option as a part of the DHCP Internet Standard: |
| 1685 |
|
| 1686 |
1. The author devises the new option. |
| 1687 |
2. The author requests a number for the new option from IANA by |
| 1688 |
contacting: |
| 1689 |
Internet Assigned Numbers Authority (IANA) |
| 1690 |
USC/Information Sciences Institute |
| 1691 |
4676 Admiralty Way |
| 1692 |
Marina del Rey, California 90292-6695 |
| 1693 |
|
| 1694 |
or by email as: [email protected] |
| 1695 |
|
| 1696 |
3. The author documents the new option, using the newly obtained |
| 1697 |
option number, as an Internet Draft. |
| 1698 |
4. The author submits the Internet Draft for review through the IETF |
| 1699 |
standards process as defined in "Internet Official Protocol |
| 1700 |
Standards" (STD 1). The new option will be submitted for eventual |
| 1701 |
acceptance as an Internet Standard. |
| 1702 |
5. The new option progresses through the IETF standards process; the |
| 1703 |
new option will be reviewed by the Dynamic Host Configuration |
| 1704 |
Working Group (if that group still exists), or as an Internet |
| 1705 |
Draft not submitted by an IETF working group. |
| 1706 |
6. If the new option fails to gain acceptance as an Internet |
| 1707 |
Standard, the assigned option number will be returned to IANA for |
| 1708 |
reassignment. |
| 1709 |
|
| 1710 |
This procedure for defining new extensions will ensure that: |
| 1711 |
|
| 1712 |
* allocation of new option numbers is coordinated from a single |
| 1713 |
authority, |
| 1714 |
* new options are reviewed for technical correctness and |
| 1715 |
appropriateness, and |
| 1716 |
* documentation for new options is complete and published. |
| 1717 |
|
| 1718 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgements</span> |
| 1719 |
|
| 1720 |
The author thanks the many (and too numerous to mention!) members of |
| 1721 |
the DHC WG for their tireless and ongoing efforts in the development |
| 1722 |
of DHCP and this document. |
| 1723 |
|
| 1724 |
The efforts of J Allard, Mike Carney, Dave Lapp, Fred Lien and John |
| 1725 |
Mendonca in organizing DHCP interoperability testing sessions are |
| 1726 |
gratefully acknowledged. |
| 1727 |
|
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Alexander & Droms Standards Track [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
The development of this document was supported in part by grants from |
| 1738 |
the Corporation for National Research Initiatives (CNRI), Bucknell |
| 1739 |
University and Sun Microsystems. |
| 1740 |
|
| 1741 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span> |
| 1742 |
|
| 1743 |
[<a id="ref-1">1</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC 2131</a>, |
| 1744 |
Bucknell University, March 1997. |
| 1745 |
|
| 1746 |
[<a id="ref-2">2</a>] Reynolds, J., "BOOTP Vendor Information Extensions", <a href="./rfc1497">RFC 1497</a>, |
| 1747 |
USC/Information Sciences Institute, August 1993. |
| 1748 |
|
| 1749 |
[<a id="ref-3">3</a>] Croft, W., and J. Gilmore, "Bootstrap Protocol", <a href="./rfc951">RFC 951</a>, |
| 1750 |
Stanford University and Sun Microsystems, September 1985. |
| 1751 |
|
| 1752 |
[<a id="ref-4">4</a>] Braden, R., Editor, "Requirements for Internet Hosts - |
| 1753 |
Communication Layers", STD 3, <a href="./rfc1122">RFC 1122</a>, USC/Information Sciences |
| 1754 |
Institute, October 1989. |
| 1755 |
|
| 1756 |
[<a id="ref-5">5</a>] Mogul, J., and J. Postel, "Internet Standard Subnetting |
| 1757 |
Procedure", STD 5, <a href="./rfc950">RFC 950</a>, USC/Information Sciences Institute, |
| 1758 |
August 1985. |
| 1759 |
|
| 1760 |
[<a id="ref-6">6</a>] Postel, J., and K. Harrenstien, "Time Protocol", STD 26, <a href="./rfc868">RFC</a> |
| 1761 |
<a href="./rfc868">868</a>, USC/Information Sciences Institute, SRI, May 1983. |
| 1762 |
|
| 1763 |
[<a id="ref-7">7</a>] Postel, J., "Name Server", IEN 116, USC/Information Sciences |
| 1764 |
Institute, August 1979. |
| 1765 |
|
| 1766 |
[<a id="ref-8">8</a>] Mockapetris, P., "Domain Names - Implementation and |
| 1767 |
Specification", STD 13, <a href="./rfc1035">RFC 1035</a>, USC/Information Sciences |
| 1768 |
Institute, November 1987. |
| 1769 |
|
| 1770 |
[<a id="ref-9">9</a>] Postel, J., "Quote of the Day Protocol", STD 23, <a href="./rfc865">RFC 865</a>, |
| 1771 |
USC/Information Sciences Institute, May 1983. |
| 1772 |
|
| 1773 |
[<a id="ref-10">10</a>] McLaughlin, L., "Line Printer Daemon Protocol", <a href="./rfc1179">RFC 1179</a>, The |
| 1774 |
Wollongong Group, August 1990. |
| 1775 |
|
| 1776 |
[<a id="ref-11">11</a>] Accetta, M., "Resource Location Protocol", <a href="./rfc887">RFC 887</a>, CMU, |
| 1777 |
December 1983. |
| 1778 |
|
| 1779 |
[<a id="ref-12">12</a>] Mogul, J. and S. Deering, "Path MTU Discovery", <a href="./rfc1191">RFC 1191</a>, |
| 1780 |
DECWRL, Stanford University, November 1990. |
| 1781 |
|
| 1782 |
[<a id="ref-13">13</a>] Deering, S., "ICMP Router Discovery Messages", <a href="./rfc1256">RFC 1256</a>, |
| 1783 |
Xerox PARC, September 1991. |
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Alexander & Droms Standards Track [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
[<a id="ref-14">14</a>] Leffler, S. and M. Karels, "Trailer Encapsulations", <a href="./rfc893">RFC 893</a>, |
| 1794 |
U. C. Berkeley, April 1984. |
| 1795 |
|
| 1796 |
[<a id="ref-15">15</a>] Hornig, C., "Standard for the Transmission of IP Datagrams over |
| 1797 |
Ethernet Networks", <a href="./rfc894">RFC 894</a>, Symbolics, April 1984. |
| 1798 |
|
| 1799 |
[<a id="ref-16">16</a>] Postel, J. and J. Reynolds, "Standard for the Transmission of |
| 1800 |
IP Datagrams Over IEEE 802 Networks", <a href="./rfc1042">RFC 1042</a>, USC/Information |
| 1801 |
Sciences Institute, February 1988. |
| 1802 |
|
| 1803 |
[<a id="ref-17">17</a>] Sun Microsystems, "System and Network Administration", March |
| 1804 |
1990. |
| 1805 |
|
| 1806 |
[<a id="ref-18">18</a>] Mills, D., "Internet Time Synchronization: The Network Time |
| 1807 |
Protocol", <a href="./rfc1305">RFC 1305</a>, UDEL, March 1992. |
| 1808 |
|
| 1809 |
[<a id="ref-19">19</a>] NetBIOS Working Group, "Protocol Standard for a NetBIOS Service |
| 1810 |
on a TCP/UDP transport: Concepts and Methods", STD 19, <a href="./rfc1001">RFC 1001</a>, |
| 1811 |
March 1987. |
| 1812 |
|
| 1813 |
[<a id="ref-20">20</a>] NetBIOS Working Group, "Protocol Standard for a NetBIOS Service |
| 1814 |
on a TCP/UDP transport: Detailed Specifications", STD 19, <a href="./rfc1002">RFC</a> |
| 1815 |
<a href="./rfc1002">1002</a>, March 1987. |
| 1816 |
|
| 1817 |
[<a id="ref-21">21</a>] Scheifler, R., "FYI On the X Window System", FYI 6, <a href="./rfc1198">RFC 1198</a>, |
| 1818 |
MIT Laboratory for Computer Science, January 1991. |
| 1819 |
|
| 1820 |
[<a id="ref-22">22</a>] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1700">RFC 1700</a>, |
| 1821 |
USC/Information Sciences Institute, July 1992. |
| 1822 |
|
| 1823 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Security Considerations</span> |
| 1824 |
|
| 1825 |
Security issues are not discussed in this memo. |
| 1826 |
|
| 1827 |
|
| 1828 |
|
| 1829 |
|
| 1830 |
|
| 1831 |
|
| 1832 |
|
| 1833 |
|
| 1834 |
|
| 1835 |
|
| 1836 |
|
| 1837 |
|
| 1838 |
|
| 1839 |
|
| 1840 |
|
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Alexander & Droms Standards Track [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc2132">RFC 2132</a> DHCP Options and BOOTP Vendor Extensions March 1997</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Authors' Addresses</span> |
| 1850 |
|
| 1851 |
Steve Alexander |
| 1852 |
Silicon Graphics, Inc. |
| 1853 |
2011 N. Shoreline Boulevard |
| 1854 |
Mailstop 510 |
| 1855 |
Mountain View, CA 94043-1389 |
| 1856 |
|
| 1857 |
Phone: (415) 933-6172 |
| 1858 |
EMail: [email protected] |
| 1859 |
|
| 1860 |
|
| 1861 |
Ralph Droms |
| 1862 |
Bucknell University |
| 1863 |
Lewisburg, PA 17837 |
| 1864 |
|
| 1865 |
Phone: (717) 524-1145 |
| 1866 |
EMail: [email protected] |
| 1867 |
|
| 1868 |
|
| 1869 |
|
| 1870 |
|
| 1871 |
|
| 1872 |
|
| 1873 |
|
| 1874 |
|
| 1875 |
|
| 1876 |
|
| 1877 |
|
| 1878 |
|
| 1879 |
|
| 1880 |
|
| 1881 |
|
| 1882 |
|
| 1883 |
|
| 1884 |
|
| 1885 |
|
| 1886 |
|
| 1887 |
|
| 1888 |
|
| 1889 |
|
| 1890 |
|
| 1891 |
|
| 1892 |
|
| 1893 |
|
| 1894 |
|
| 1895 |
|
| 1896 |
|
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
Alexander & Droms Standards Track [Page 34] |
| 1901 |
</pre> |