1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Network Working Group R. Droms
Request for Comments: 3679 Cisco Systems
Category: Informational January 2004
<span class="h1">Unused Dynamic Host Configuration Protocol (DHCP) Option Codes</span>
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
Prior to the publication of <a href="./rfc2489">RFC 2489</a> (which was updated by <a href="./rfc2939">RFC 2939</a>),
several option codes were assigned to proposed Dynamic Host
Configuration Protocol (DHCP) options that were subsequently never
used. This document lists those unused option codes and directs IANA
to make these option codes available for assignment to other DHCP
options in the future.
The document also lists several option codes that are not currently
documented in an RFC but should not be made available for
reassignment to future DHCP options.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
<a href="#section-2">Section 2</a> of this document lists the unused DHCP option codes from
the IANA list of BOOTP and DHCP option codes [<a href="#ref-1" title=""BOOTP and DHCP Parameters"">1</a>]. Each option code
includes any known documentation and contact information from the
IANA list. IANA will make these option codes available for
assignment to other DHCP options in the future.
<a href="#section-3">Section 3</a> lists several DHCP option codes that are not currently
documented in an RFC but should not be made available for
reassignment to future DHCP options.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Unused DHCP Option Codes to be Reassigned to Future DHCP Options</span>
The option codes listed in this section are to be returned to IANA
for reassignment to new options. Responses from associated contact
persons are noted where they have been received.
<span class="grey">Droms Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3679">RFC 3679</a> Unused DHCP Option Codes January 2004</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Service Location Protocol Naming Authority</span>
Code: 80
Name: Service Location Protocol Naming Authority
Defined in: (expired Internet-Draft)
Contact: Charlie Perkins
Reason to recover: Never published as standard and not in general use
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Relay Agent Options</span>
Codes: 83, 84
Name: Relay Agent Options
Defined in: Early draft of <a href="./rfc3046">RFC 3046</a> [<a href="#ref-2" title=""DHCP Relay Agent Information Option"">2</a>]
Contact: (none)
Reason to recover: Not defined in <a href="./rfc3046">RFC 3046</a> as published
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. IEEE 1003.1 POSIX Timezone</span>
Code: 88
Name: IEEE 1003.1 POSIX Timezone
Defined in: (expired Internet-Draft)
Contact: Mike Carney
Reason to recover: Never published as standard and not in general use
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. FQDNs in DHCP Options</span>
Code: 89
Name: FQDNs in DHCP Options
Defined in: (expired Internet-Draft)
Contact: Ralph Droms; agrees that option code should be
reassigned
Reason to recover: Never published as standard and not in general use
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. VINES TCP/IP Server</span>
Code: 91
Name: VINES TCP/IP Server
Defined in: (none)
Contact: (none)
Reason to recover: Never published as Internet-Draft
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Server Selection</span>
Code: 92
Name: Server Selection
Defined in: (none)
Contact: (none)
Reason to recover: Never published as Internet-Draft
<span class="grey">Droms Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3679">RFC 3679</a> Unused DHCP Option Codes January 2004</span>
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a> IPv6 Transition</span>
Code: 96
Name: IPv6 Transition
Defined in: (expired Internet-Draft)
Contact: Dan Harrington; agrees that option code should be
reassigned
Reason to recover: Never published as standard and not in general use
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Printer Name</span>
Code: 100
Name: Printer Name
Defined in: (none)
Contact: (none)
Reason to recover: Never published as Internet-Draft
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Multicast Assignment through DHCP</span>
Code: 101
Name: Multicast Assignment through DHCP
Defined in: (expired Internet-Draft)
Contact: Baiju Patel, Munil Shah
Reason to recover: Never published as standard and not in general use
<span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. Swap Path</span>
Code: 108
Name: Swap Path
Defined in: (none)
Contact: (none)
Reason to recover: Never published as Internet-Draft
<span class="h3"><a class="selflink" id="section-2.11" href="#section-2.11">2.11</a>. IPX Compatibility</span>
Code: 110
Name: IPX Compatibility
Defined in: (none)
Contact: Juan Luciani; agrees that option code should be
reassigned
Reason to recover: Never published as Internet-Draft
<span class="grey">Droms Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3679">RFC 3679</a> Unused DHCP Option Codes January 2004</span>
<span class="h3"><a class="selflink" id="section-2.12" href="#section-2.12">2.12</a>. Failover</span>
Code: 115
Name: Failover
Defined in: Early revisions of "DHCP Failover Protocol" [<a href="#ref-3" title=""DHCP Failover Protocol"">3</a>]
Contact: Kim Kinnear
Reason to recover: Current version of "DHCP Failover Protocol" does
not use a DHCP option
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Option codes to be reserved by IANA</span>
The option codes listed in this section are the subject of ongoing
work in the DHC Working Group (WG). These option codes should remain
on the IANA list of assigned option codes [<a href="#ref-1" title=""BOOTP and DHCP Parameters"">1</a>] until the DHC WG has
made a final decision about their disposition.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Option codes used in PXE Specification</span>
The following option codes are used in the "Preboot Execution
Environment (PXE) Specification, Version 2.1" [<a href="#ref-4" title=""Preboot Execution Environment (PXE) Specification Version 2.1"">4</a>]. However, although
these options are in widespread use by devices that use PXE, none of
these option codes have been described in a published RFC.
The DHC WG will endeavor to have specifications for these options
published.
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Client System</span>
Code: 93
Name: Client System
Defined in: "Preboot Execution Environment (PXE)
Specification, Version 2.1" [<a href="#ref-4" title=""Preboot Execution Environment (PXE) Specification Version 2.1"">4</a>]
Contact: Michael Johnston
(frenchy@quiet-like-a-panther.org)
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Client NDI</span>
Code: 94
Name: Client NDI
Defined in: "Preboot Execution Environment (PXE)
Specification, Version 2.1" [<a href="#ref-4" title=""Preboot Execution Environment (PXE) Specification Version 2.1"">4</a>]
Contact: Michael Johnston
(frenchy@quiet-like-a-panther.org)
<span class="grey">Droms Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3679">RFC 3679</a> Unused DHCP Option Codes January 2004</span>
<span class="h4"><a class="selflink" id="section-3.1.3" href="#section-3.1.3">3.1.3</a>. UUID/GUID Client Identifier</span>
Code: 97
Name: UUID/GUID Client Identifier
Defined in: "Preboot Execution Environment (PXE)
Specification, Version 2.1" [<a href="#ref-4" title=""Preboot Execution Environment (PXE) Specification Version 2.1"">4</a>] (and an expired
Internet-Draft)
Contact: Dan Harrington, Michael Johnston
(frenchy@quiet-like-a-panther.org)
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. In Use by Apple</span>
The following option codes are used by devices from Apple Computer.
However, none of these option codes have been described in a
published RFC.
The DHC WG will endeavor to have specifications for these options
published.
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. LDAP Servers</span>
Code: 95
Name: LDAP Servers
Defined in: (none)
Contact: Dieter Siegmund, dieter@apple.com
Reason to recover: Never published in an RFC
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Netinfo Parameters</span>
Codes: 112, 113
Name: Netinfo Address, Netinfo Tag
Defined in: (none)
Contact: Dieter Siegmund, dieter@apple.com
Reason to recover: Never published in an RFC
<span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. URL</span>
Code: 114
Name: URL
Defined in: (none)
Contact: Dieter Siegmund, dieter@apple.com
Reason to recover: Never published in an RFC
<span class="grey">Droms Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3679">RFC 3679</a> Unused DHCP Option Codes January 2004</span>
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Option Code Extensions</span>
Note that these option codes are identified in "Extending DHCP
Options Codes" [<a href="#ref-5" title=""Extending DHCP Options Codes"">5</a>] as part of a mechanism for extending the set of
option codes available to DHCP. If these option codes are not used
for DHCP option code extension, they will be returned to IANA for
reassignment to other DHCP options.
Codes: 126, 127
Name: Option Code Extensions
Defined in: (expired Internet-Draft)
Contact: Ralph Droms
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Already Returned for Reassignment</span>
The option codes 99, 102-107, 109 and 111 have already been returned
for reassignment to future DHCP options.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
This document has no known security implications, as none of the
reclaimed options are known to be in use.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
IANA has returned the DHCP option codes listed in <a href="#section-2">Section 2</a> to the
list of available option codes. These option codes may be reassigned
to new DHCP options, according to the procedures in <a href="./rfc2939">RFC 2939</a> [<a href="#ref-6" title=""Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types"">6</a>].
IANA is requested to reassign these option codes after the list of
option codes that have never been assigned or have previously been
returned has been exhausted.
Informative References
[<a id="ref-1">1</a>] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters",
<a href="http://www.iana.org/assignments/bootp-dhcp-parameters">http://www.iana.org/assignments/bootp-dhcp-parameters</a>, February
2003.
[<a id="ref-2">2</a>] Patrick, M., "DHCP Relay Agent Information Option", <a href="./rfc3046">RFC 3046</a>,
January 2001.
[<a id="ref-3">3</a>] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil,
G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", Work in
Progress.
[<a id="ref-4">4</a>] Intel Corporation, "Preboot Execution Environment (PXE)
Specification Version 2.1", <a href="http://www.pix.net/software/pxeboot/archive/pxespec.pdf">http://www.pix.net/software/pxeboot/</a>
<a href="http://www.pix.net/software/pxeboot/archive/pxespec.pdf">archive/pxespec.pdf</a>, September 1999.
<span class="grey">Droms Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3679">RFC 3679</a> Unused DHCP Option Codes January 2004</span>
[<a id="ref-5">5</a>] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options
Codes", Work in Progress.
[<a id="ref-6">6</a>] Droms, R., "Procedures and IANA Guidelines for Definition of New
DHCP Options and Message Types", <a href="https://www.rfc-editor.org/bcp/bcp43">BCP 43</a>, <a href="./rfc2939">RFC 2939</a>, September
2000.
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Author's Address
Ralph Droms
Cisco Systems
1414 Massachusetts Avenue
Boxborough, MA 01719
USA
Phone: +1 978 936 1674
EMail: rdroms@cisco.com
<span class="grey">Droms Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3679">RFC 3679</a> Unused DHCP Option Codes January 2004</span>
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Droms Informational [Page 8]
</pre>
|
