| 1 |
<pre>Network Working Group J. Reynolds |
| 2 |
Request for Comments: 1395 ISI |
| 3 |
Obsoletes: <a href="./rfc1084">1084</a>, <a href="./rfc1048">1048</a> January 1993 |
| 4 |
Updates: <a href="./rfc951">951</a> |
| 5 |
|
| 6 |
|
| 7 |
BOOTP Vendor Information Extensions |
| 8 |
|
| 9 |
Status of this Memo |
| 10 |
|
| 11 |
This memo is a status report on the vendor information extensions |
| 12 |
used in the Bootstrap Protocol (BOOTP). Distribution of this memo is |
| 13 |
unlimited. |
| 14 |
|
| 15 |
Introduction |
| 16 |
|
| 17 |
This RFC is a slight revision and extension of <a href="./rfc1048">RFC-1048</a> by Philip |
| 18 |
Prindeville, who should be credited with the original work in this |
| 19 |
memo. This memo will be updated as additional tags are are defined. |
| 20 |
This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain |
| 21 |
Name, Tag 16 for Swap Server and Tag 17 for Root Path. |
| 22 |
|
| 23 |
As workstations and personal computers proliferate on the Internet, |
| 24 |
the administrative complexity of maintaining a network is increased |
| 25 |
by an order of magnitude. The assignment of local network resources |
| 26 |
to each client represents one such difficulty. In most environments, |
| 27 |
delegating such responsibility to the user is not plausible and, |
| 28 |
indeed, the solution is to define the resources in uniform terms, and |
| 29 |
to automate their assignment. |
| 30 |
|
| 31 |
The basic Bootstrap Protocol [<a href="./rfc951" title=""Bootstrap Protocol (BOOTP)"">RFC-951</a>] dealt with the issue of |
| 32 |
assigning an internet address to a client, as well as a few other |
| 33 |
resources. The protocol included provisions for vendor-defined |
| 34 |
resource information. |
| 35 |
|
| 36 |
This memo defines a (potentially) vendor-independent interpretation |
| 37 |
of this resource information. |
| 38 |
|
| 39 |
Overview of BOOTP |
| 40 |
|
| 41 |
While the Reverse Address Resolution (RARP) Protocol [<a href="./rfc903" title=""A Reverse Address Resolution Protocol"">RFC-903</a>] may be |
| 42 |
used to assign an IP address to a local network hardware address, it |
| 43 |
provides only part of the functionality needed. Though this protocol |
| 44 |
can be used in conjunction with other supplemental protocols (the |
| 45 |
Resource Location Protocol [<a href="./rfc887" title=""Resource Location Protocol"">RFC-887</a>], the Domain Name System [RFC- |
| 46 |
1034]), a more integrated solution may be desirable. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Reynolds [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1395">RFC 1395</a> BOOTP Extensions January 1993</span> |
| 55 |
|
| 56 |
|
| 57 |
Bootstrap Protocol (BOOTP) is a UDP/IP-based protocol that allows a |
| 58 |
booting host to configure itself dynamically, and more significantly, |
| 59 |
without user supervision. It provides a means to assign a host its |
| 60 |
IP address, a file from which to download a boot program from some |
| 61 |
server, that server's address, and (if present) the address of an |
| 62 |
Internet gateway. |
| 63 |
|
| 64 |
One obvious advantage of this procedure is the centralized management |
| 65 |
of network addresses, which eliminates the need for per-host unique |
| 66 |
configuration files. In an environment with several hundred hosts, |
| 67 |
maintaining local configuration information and operating system |
| 68 |
versions specific to each host might otherwise become chaotic. By |
| 69 |
categorizing hosts into classes and maintaining configuration |
| 70 |
information and boot programs for each class, the complexity of this |
| 71 |
chore may be reduced in magnitude. |
| 72 |
|
| 73 |
BOOTP Vendor Information Format |
| 74 |
|
| 75 |
The full description of the BOOTP request/reply packet format may be |
| 76 |
found in [<a href="./rfc951" title=""Bootstrap Protocol (BOOTP)"">RFC-951</a>]. The rest of this document will concern itself |
| 77 |
with the last field of the packet, a 64 octet area reserved for |
| 78 |
vendor information, to be used in a hitherto unspecified fashion. A |
| 79 |
generalized use of this area for giving information useful to a wide |
| 80 |
class of machines, operating systems, and configurations follows. In |
| 81 |
situations where a single BOOTP server is to be used among |
| 82 |
heterogeneous clients in a single site, a generic class of data may |
| 83 |
be used. |
| 84 |
|
| 85 |
Vendor Information "Magic Cookie" |
| 86 |
|
| 87 |
As suggested in [<a href="./rfc951" title=""Bootstrap Protocol (BOOTP)"">RFC-951</a>], the first four bytes of this field have |
| 88 |
been assigned to the magic cookie, which identifies the mode in |
| 89 |
which the succeeding data is to be interpreted. The value of the |
| 90 |
magic cookie is the 4 octet dotted decimal 99.130.83.99 (or |
| 91 |
hexadecimal number 63.82.53.63) in network byte order. |
| 92 |
|
| 93 |
Format of Individual Fields |
| 94 |
|
| 95 |
The vendor information field has been implemented as a free |
| 96 |
format, with extendable tagged sub-fields. These sub-fields are |
| 97 |
length tagged (with exceptions; see below), allowing clients not |
| 98 |
implementing certain types to correctly skip fields they cannot |
| 99 |
interpret. Lengths are exclusive of the tag and length octets; |
| 100 |
all multi-byte quantities are in network byte-order. |
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Reynolds [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1395">RFC 1395</a> BOOTP Extensions January 1993</span> |
| 111 |
|
| 112 |
|
| 113 |
Fixed Length Data |
| 114 |
|
| 115 |
The fixed length data are comprised of two formats. Those that |
| 116 |
have no data consist of a single tag octet and are implicitly |
| 117 |
of one-octet length, while those that contain data consist of |
| 118 |
one tag octet, one length octet, and length octets of data. |
| 119 |
|
| 120 |
Pad Field (Tag: 0, Data: None) |
| 121 |
|
| 122 |
May be used to align subsequent fields to word boundaries |
| 123 |
required by the target machine (i.e., 32-bit quantities such |
| 124 |
as IP addresses on 32-bit boundaries). |
| 125 |
|
| 126 |
Subnet Mask Field (Tag: 1, Data: 4 subnet mask bytes) |
| 127 |
|
| 128 |
Specifies the net and local subnet mask as per the standard |
| 129 |
on subnetting [<a href="./rfc950" title=""Internet Standard Subnetting Procedure"">RFC-950</a>]. For convenience, this field must |
| 130 |
precede the GATEWAY field (below), if present. |
| 131 |
|
| 132 |
Time Offset Field (Tag: 2, Data: 4 time offset bytes) |
| 133 |
|
| 134 |
Specifies the time offset of the local subnet in seconds |
| 135 |
from Coordinated Universal Time (UTC); signed 32-bit |
| 136 |
integer. |
| 137 |
|
| 138 |
End Field (Tag: 255, Data: None) |
| 139 |
|
| 140 |
Specifies end of usable data in the vendor information area. |
| 141 |
The rest of this field should be filled with PAD zero) |
| 142 |
octets. |
| 143 |
|
| 144 |
Variable Length Data |
| 145 |
|
| 146 |
The variable length data has a single format; it consists of |
| 147 |
one tag octet, one length octet, and length octets of data. |
| 148 |
|
| 149 |
Gateway Field (Tag: 3, Data: N address bytes) |
| 150 |
|
| 151 |
Specifies the IP addresses of N/4 gateways for this subnet. |
| 152 |
If one of many gateways is preferred, that should be first. |
| 153 |
|
| 154 |
Time Server Field (Tag: 4, Data: N address bytes) |
| 155 |
|
| 156 |
Specifies the IP addresses of N/4 time servers [<a href="./rfc868" title=""Time Protocol"">RFC-868</a>]. |
| 157 |
|
| 158 |
IEN-116 Name Server Field (Tag: 5, Data: N address bytes) |
| 159 |
|
| 160 |
Specifies the IP addresses of N/4 name servers [<a href="#ref-IEN-116" title=""Internet Name Server"">IEN-116</a>]. |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Reynolds [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1395">RFC 1395</a> BOOTP Extensions January 1993</span> |
| 167 |
|
| 168 |
|
| 169 |
Domain Name Server Field (Tag: 6, Data: N address bytes) |
| 170 |
|
| 171 |
Specifies the IP addresses of N/4 domain name servers <a href="./rfc1034">RFC-</a> |
| 172 |
<a href="./rfc1034">1034</a>]. |
| 173 |
|
| 174 |
Log Server Field (Tag: 7, Data: N address bytes) |
| 175 |
|
| 176 |
Specifies the IP addresses of N/4 MIT-LCS UDP log server |
| 177 |
[<a href="#ref-LOGGING" title=""Logging and Status Protocol"">LOGGING</a>]. |
| 178 |
|
| 179 |
Cookie/Quote Server Field (Tag: 8, Data: N address bytes) |
| 180 |
|
| 181 |
Specifies the IP addresses of N/4 Quote of the Day servers |
| 182 |
[<a href="./rfc865" title=""Quote of the Day Protocol"">RFC-865</a>]. |
| 183 |
|
| 184 |
LPR Server Field (Tag: 9, Data: N address bytes) |
| 185 |
|
| 186 |
Specifies the IP addresses of N/4 Berkeley 4BSD printer |
| 187 |
servers [<a href="#ref-LPD" title=""4.2BSD Line Printer Spooler Manual"">LPD</a>]. |
| 188 |
|
| 189 |
Impress Server Field (Tag: 10, Data: N address bytes) |
| 190 |
|
| 191 |
Specifies the IP addresses of N/4 Impress network image |
| 192 |
servers [<a href="#ref-IMAGEN" title=""Image Server XT Programmer's Guide"">IMAGEN</a>]. |
| 193 |
|
| 194 |
RLP Server Field (Tag: 11, Data: N address bytes) |
| 195 |
|
| 196 |
Specifies the IP addresses of N/4 Resource Location Protocol |
| 197 |
(RLP) servers [<a href="./rfc887" title=""Resource Location Protocol"">RFC-887</a>]. |
| 198 |
|
| 199 |
Hostname (Tag: 12, Data: N bytes of hostname) |
| 200 |
|
| 201 |
Specifies the name of the client. The name may or may not |
| 202 |
domain qualified: this is a site-specific issue. |
| 203 |
|
| 204 |
Boot File Size (Tag: 13, Data: 2) |
| 205 |
|
| 206 |
A two octet value (in network order) specifying the number |
| 207 |
of 512 octet blocks in the default boot file. Informs BOOTP |
| 208 |
client how large the BOOTP file image is. |
| 209 |
|
| 210 |
Merit Dump File (Tag: 14, Data: N bytes of filename) |
| 211 |
|
| 212 |
Name of a file to dump core of this client to. |
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Reynolds [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1395">RFC 1395</a> BOOTP Extensions January 1993</span> |
| 223 |
|
| 224 |
|
| 225 |
Domain Name (Tag: 15, Data: N bytes of domain name) |
| 226 |
|
| 227 |
Specifies the domain name of the client for Domain Name |
| 228 |
Server (DNS) resolution [<a href="./rfc1034" title=""Domain Names - Concepts and Facilities"">RFC-1034</a>]. |
| 229 |
|
| 230 |
Swap Server (Tag: 16, Data: 4 address bytes) |
| 231 |
|
| 232 |
An IP address to hold the IP address of a swap server. |
| 233 |
|
| 234 |
Root Path (Tag: 17, Data: N bytes of path name) |
| 235 |
|
| 236 |
A string to specify a pathname to mount as a root disk. |
| 237 |
|
| 238 |
Reserved Fields (Tag: 128-254, Data: N bytes of undefined |
| 239 |
content) |
| 240 |
|
| 241 |
Specifies additional site-specific information, to be |
| 242 |
interpreted on an implementation-specific basis. This |
| 243 |
should follow all data with the preceding generic tags 0- |
| 244 |
127). |
| 245 |
|
| 246 |
Extensions |
| 247 |
|
| 248 |
Additional generic data fields may be registered by contacting: |
| 249 |
|
| 250 |
Internet Assigned Numbers Authority (IANA) |
| 251 |
Information Sciences Institute |
| 252 |
University of Southern California |
| 253 |
4676 Admiralty Way |
| 254 |
Marina del Rey, California 90292-6695 |
| 255 |
|
| 256 |
or by email as: [email protected] |
| 257 |
|
| 258 |
Implementation specific use of undefined generic types (those in the |
| 259 |
range 18-127) may conflict with other implementations, and |
| 260 |
registration is required. |
| 261 |
|
| 262 |
When selecting information to put into the vendor specific area, care |
| 263 |
should be taken to not exceed the 64 byte length restriction. |
| 264 |
Nonessential information (such as host name and quote of the day |
| 265 |
server) may be excluded, which may later be located with a more |
| 266 |
appropriate service protocol, such as RLP or the WKS resource-type of |
| 267 |
the domain name system. Indeed, even RLP servers may be discovered |
| 268 |
using a broadcast request to locate a local RLP server. |
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Reynolds [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1395">RFC 1395</a> BOOTP Extensions January 1993</span> |
| 279 |
|
| 280 |
|
| 281 |
Comparison to Alternative Approaches |
| 282 |
|
| 283 |
Extending BOOTP to provide more configuration information than the |
| 284 |
minimum required by boot PROMs may not be necessary. Rather than |
| 285 |
having each module in a host (e.g., the time module, the print |
| 286 |
spooler, the domain name resolver) broadcast to the BOOTP server to |
| 287 |
obtain the addresses of required servers, it would be better for each |
| 288 |
of them to multicast directly to the particular server group of |
| 289 |
interest, possibly using "expanding ring" multicasts. |
| 290 |
|
| 291 |
The multicast approach has the following advantages over the BOOTP |
| 292 |
approach: |
| 293 |
|
| 294 |
- It eliminates dependency on a third party (the BOOTP server) that |
| 295 |
may be temporarily unavailable or whose database may be incorrect or |
| 296 |
incomplete. Multicasting directly to the desired services will |
| 297 |
locate those servers that are currently available, and only those. |
| 298 |
|
| 299 |
- It reduces the administrative chore of keeping the (probably |
| 300 |
replicated) BOOTP database up-to-date and consistent. This is |
| 301 |
especially important in an environment with a growing number of |
| 302 |
services and an evolving population of servers. |
| 303 |
|
| 304 |
- In some cases, it reduces the amount of packet traffic and/or the |
| 305 |
delay required to get the desired information. For example, the |
| 306 |
current time can be obtained by a single multicast to a time server |
| 307 |
group which evokes replies from those time servers that are |
| 308 |
currently up. The BOOTP approach would require a broadcast to the |
| 309 |
BOOTP server, a reply from the BOOTP server, one or more unicasts to |
| 310 |
time servers (perhaps waiting for long timeouts if the initially |
| 311 |
chosen server(s) are down), and finally a reply from a server. |
| 312 |
|
| 313 |
One apparent advantage of the proposed BOOTP extensions is that they |
| 314 |
provide a uniform way to locate servers. However, the multicast |
| 315 |
approach could also be implemented in a consistent way across |
| 316 |
multiple services. The V System naming protocol is a good example of |
| 317 |
this; character string pathnames are used to name any number of |
| 318 |
resources (i.e., not just files) and a standard subroutine library |
| 319 |
looks after multicasting to locate the resources, caching the |
| 320 |
discovered locations, and detecting stale cache data. |
| 321 |
|
| 322 |
Another apparent advantage of the BOOTP approach is that it allows an |
| 323 |
administrator to easily control which hosts use which servers. The |
| 324 |
multicast approach favors more distributed control over resource |
| 325 |
allocation, where each server decides which hosts it will serve, |
| 326 |
using whatever level of authentication is appropriate for the |
| 327 |
particular service. For example, time servers usually don't care who |
| 328 |
they serve (i.e., administrative control via the BOOTP database is |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Reynolds [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1395">RFC 1395</a> BOOTP Extensions January 1993</span> |
| 335 |
|
| 336 |
|
| 337 |
unnecessary), whereas file servers usually require strong |
| 338 |
authentication (i.e., administrative control via the BOOTP database |
| 339 |
is insufficient). |
| 340 |
|
| 341 |
The main drawback of the multicast approach, of course, is that IP |
| 342 |
multicasting is not widely implemented, and there is a need to locate |
| 343 |
existing services which do not understand IP multicasts. |
| 344 |
|
| 345 |
The BOOTP approach may be most efficient in the case that all the |
| 346 |
information needed by the client host is returned by a single BOOTP |
| 347 |
reply and each program module simply reads the information it needs |
| 348 |
from a local table filled in by the BOOTP reply. |
| 349 |
|
| 350 |
Acknowledgments |
| 351 |
|
| 352 |
The following people provided helpful comments on the first edition |
| 353 |
of this memo: Drew Perkins, of Carnagie Mellon University, Bill |
| 354 |
Croft, of Stanford University, and co-author of BOOTP, and Steve |
| 355 |
Deering, also of Stanford University, for contributing the |
| 356 |
"Comparison to Alternative Approaches" section. |
| 357 |
|
| 358 |
References |
| 359 |
|
| 360 |
[<a id="ref-RFC-951">RFC-951</a>] Croft, B., and J. Gilmore, "Bootstrap Protocol (BOOTP)", |
| 361 |
Stanford and SUN Microsystems, September 1985. |
| 362 |
|
| 363 |
[<a id="ref-RFC-903">RFC-903</a>] Finlayson, R., Mann, T., Mogul, J., and M. Theimer, "A |
| 364 |
Reverse Address Resolution Protocol", <a href="./rfc903">RFC 903</a>, Stanford, |
| 365 |
June 1984. |
| 366 |
|
| 367 |
[<a id="ref-RFC-887">RFC-887</a>] Accetta, M., "Resource Location Protocol", <a href="./rfc887">RFC 887</a>, CMU, |
| 368 |
December 1983. |
| 369 |
|
| 370 |
[<a id="ref-RFC-1034">RFC-1034</a>] Mockapetris, P., "Domain Names - Concepts and |
| 371 |
Facilities", STD 13, <a href="./rfc1034">RFC 1034</a>, USC/Information Sciences |
| 372 |
Institute, November 1987. |
| 373 |
|
| 374 |
[<a id="ref-RFC-950">RFC-950</a>] Mogul, J., and J. Postel, "Internet Standard Subnetting |
| 375 |
Procedure", STD 5, <a href="./rfc950">RFC 950</a>, USC/Information Sciences |
| 376 |
Institute, August 1985. |
| 377 |
|
| 378 |
[<a id="ref-RFC-868">RFC-868</a>] Postel, J., "Time Protocol", STD 26, <a href="./rfc868">RFC 868</a>, |
| 379 |
USC/Information Sciences Institute, May 1983. |
| 380 |
|
| 381 |
[<a id="ref-IEN-116">IEN-116</a>] Postel, J., "Internet Name Server", USC/Information |
| 382 |
Sciences Institute, August 1979. |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Reynolds [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1395">RFC 1395</a> BOOTP Extensions January 1993</span> |
| 391 |
|
| 392 |
|
| 393 |
[<a id="ref-LOGGING">LOGGING</a>] Clark, D., "Logging and Status Protocol", Massachusetts |
| 394 |
Institute of Technology Laboratory for Computer Science, |
| 395 |
Cambridge, Massachusetts, 1981. |
| 396 |
|
| 397 |
[<a id="ref-RFC-865">RFC-865</a>] Postel, J., "Quote of the Day Protocol", STD 23, <a href="./rfc865">RFC 865</a>, |
| 398 |
USC/Information Sciences Institute, May 1983. |
| 399 |
|
| 400 |
[<a id="ref-LPD">LPD</a>] Campbell, R., "4.2BSD Line Printer Spooler Manual", UNIX |
| 401 |
Programmer's Manual, Vol II, University of California at |
| 402 |
Berkeley, Computer Science Division, July 1983. |
| 403 |
|
| 404 |
[<a id="ref-IMAGEN">IMAGEN</a>] "Image Server XT Programmer's Guide", Imagen Corporation, |
| 405 |
Santa Clara, California, August 1986. |
| 406 |
|
| 407 |
Security Considerations |
| 408 |
|
| 409 |
Security issues are not discussed in this memo. |
| 410 |
|
| 411 |
Author's Address: |
| 412 |
|
| 413 |
Joyce K. Reynolds |
| 414 |
Information Sciences Institute |
| 415 |
University of Southern California |
| 416 |
4676 Admiralty Way |
| 417 |
Marina del Rey, CA 90292 |
| 418 |
|
| 419 |
Phone: (310) 822-1511 |
| 420 |
|
| 421 |
EMail: [email protected] |
| 422 |
|
| 423 |
|
| 424 |
|
| 425 |
|
| 426 |
|
| 427 |
|
| 428 |
|
| 429 |
|
| 430 |
|
| 431 |
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
Reynolds [Page 8] |
| 445 |
</pre> |