idnits 2.17.1 draft-ietf-dhc-unused-optioncodes-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 3, 2003) is 7509 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IPv6 Group R. Droms 3 Internet-Draft Cisco Systems 4 Expires: April 2, 2004 October 3, 2003 6 Unused DHCP Option Codes 7 draft-ietf-dhc-unused-optioncodes-07 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that other 16 groups may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at http:// 24 www.ietf.org/ietf/1id-abstracts.txt. 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 This Internet-Draft will expire on April 2, 2004. 31 Copyright Notice 33 Copyright (C) The Internet Society (2003). All Rights Reserved. 35 Abstract 37 Prior to the publication of RFC2489 (which was updated by RFC2939), 38 several option codes were assigned to proposed DHCP options that were 39 subsequently never used. This document lists those unused option 40 codes and directs IANA to make these option codes available for 41 assignment to other DHCP options in the future. 43 The document also lists several option codes that are not currently 44 documented in an RFC but should not be made available for 45 reassignment to future DHCP options. 47 1. Introduction 49 Section 2 of this document lists the unused DHCP option codes from 50 the IANA list of BOOTP and DHCP option codes [1]. Each option code 51 includes any known documentation and contact information from the 52 IANA list. IANA will make these option codes available for 53 assignment to other DHCP options in the future. 55 Section 3 lists several DHCP option codes that are not currently 56 documented in an RFC but should not be made available for 57 reassignment to future DHCP options. 59 2. Unused DHCP Option Codes to be Reassigned to Future DHCP Options 61 The option codes listed in this section are to be returned to IANA 62 for reassignment to new options. Responses from associated contact 63 persons are noted where they have been received. 65 2.1 Service Location Protocol Naming Authority 67 Code: 80 69 Name: Service Location Protocol Naming Authority 71 Defined in: (expired Internet-Draft) 73 Contact: Charlie Perkins 75 Reason to recover: Never published as standard and not in general use 77 2.2 Relay Agent Options 79 Codes: 83, 84 81 Name: Relay Agent Options 83 Defined in: Early draft of RFC3046 [2] 85 Contact: (none) 87 Reason to recover: Not defined in RFC3046 as published 89 2.3 IEEE 1003.1 POSIX Timezone 91 Code: 88 93 Name: IEEE 1003.1 POSIX Timezone 94 Defined in: (expired Internet-Draft) 96 Contact: Mike Carney 98 Reason to recover: Never published as standard and not in general use 100 2.4 FQDNs in DHCP Options 102 Code: 89 104 Name: FQDNs in DHCP Options 106 Defined in: (expired Internet-Draft) 108 Contact: Ralph Droms; agrees that option code should be 109 reassigned 111 Reason to recover: Never published as standard and not in general use 113 2.5 VINES TCP/IP Server 115 Code: 91 117 Name: VINES TCP/IP Server 119 Defined in: (none) 121 Contact: (none) 123 Reason to recover: Never published as Internet-Draft 125 2.6 Server Selection 127 Code: 92 129 Name: Server Selection 131 Defined in: (none) 133 Contact: (none) 135 Reason to recover: Never published as Internet-Draft 137 2.7 IPv6 Transition 139 Code: 96 141 Name: IPv6 Transition 143 Defined in: (expired Internet-Draft) 145 Contact: Dan Harrington; agrees that option code should be 146 reassigned 148 Reason to recover: Never published as standard and not in general use 150 2.8 Printer Name 152 Code: 100 154 Name: Printer Name 156 Defined in: (none) 158 Contact: (none) 160 Reason to recover: Never published as Internet-Draft 162 2.9 Multicast Assignment through DHCP 164 Code: 101 166 Name: Multicast Assignment through DHCP 168 Defined in: (expired Internet-Draft) 170 Contact: Baiju Patel, Munil Shah 172 Reason to recover: Never published as standard and not in general use 174 2.10 Swap Path 176 Code: 108 178 Name: Swap Path 179 Defined in: (none) 181 Contact: (none) 183 Reason to recover: Never published as Internet-Draft 185 2.11 IPX Compatibility 187 Code: 110 189 Name: IPX Compatibility 191 Defined in: (none) 193 Contact: Juan Luciani; agrees that option code should be 194 reassigned 196 Reason to recover: Never published as Internet-Draft 198 2.12 Failover 200 Code: 115 202 Name: Failover 204 Defined in: Early revisions of "DHCP Failover Protocol" [3] 206 Contact: Kim Kinnear 208 Reason to recover: Current version of "DHCP Failover Protocol" does 209 not use a DHCP option 211 3. Option codes to be reserved by IANA 213 The option codes listed in this section are the subject of ongoing 214 work in the dhc working group. These options codes should remain on 215 the IANA list of assigned option codes [1] until the dhc working 216 group has made a final decision about their disposition. 218 3.1 Option codes used in PXE Specification 220 The following option codes are used in the "Preboot Execution 221 Environment (PXE) Specification, Version 2.1" [4]. However, although 222 these options are in widespread use by devices that use PXE, none of 223 these option codes have been described in a published RFC. 225 The dhc WG will endeavor to have specifications for these options 226 published. 228 3.1.1 Client System 230 Code: 93 232 Name: Client System 234 Defined in: "Preboot Execution Environment (PXE) 235 Specification, Version 2.1" [4] 237 Contact: Michael Johnston 238 (frenchy@quiet-like-a-panther.org) 240 3.1.2 Client NDI 242 Code: 94 244 Name: Client NDI 246 Defined in: "Preboot Execution Environment (PXE) 247 Specification, Version 2.1" [4] 249 Contact: Michael Johnston 250 (frenchy@quiet-like-a-panther.org) 252 3.1.3 UUID/GUID Client Identifier 254 Code: 97 256 Name: UUID/GUID Client Identifier 258 Defined in: "Preboot Execution Environment (PXE) 259 Specification, Version 2.1" [4] (and an expired Internet-Draft) 261 Contact: Dan Harrington, Michael Johnston 262 (frenchy@quiet-like-a-panther.org) 264 3.2 In Use by Apple 266 The following option codes are used by devices from Apple Computer. 267 However, none of these option codes have been described in a 268 published RFC. 270 The dhc WG will endeavor to have specifications for these options 271 published. 273 3.2.1 LDAP Servers 275 Code: 95 277 Name: LDAP Servers 279 Defined in: (none) 281 Contact: Dieter Siegmund, dieter@apple.com 283 Reason to recover: Never published in an RFC 285 3.2.2 Netinfo Parameters 287 Codes: 112, 113 289 Name: Netinfo Address, Netinfo Tag 291 Defined in: (none) 293 Contact: Dieter Siegmund, dieter@apple.com 295 Reason to recover: Never published in an RFC 297 3.2.3 URL 299 Code: 114 301 Name: URL 303 Defined in: (none) 305 Contact: Dieter Siegmund, dieter@apple.com 307 Reason to recover: Never published in an RFC 309 3.3 Option Code Extensions 311 Note that these option codes are identified in "Extending DHCP 312 Options Codes" [5] as part of a mechanism for extending the set of 313 option codes available to DHCP. If these option codes are not used 314 for DHCP option code extension, they will be returned to IANA for 315 reassignment to other DHCP options. 317 Codes: 126, 127 319 Name: Option Code Extensions 321 Defined in: (expired Internet-Draft) 323 Contact: Ralph Droms 325 4. Already Returned for Reassignment 327 The option codes 99, 102-107, 109 and 111 have already been returned 328 for reassignment to future DHCP options. 330 5. Security Considerations 332 This document has no known security implications, as none of the 333 reclaimed options are known to be in use. 335 6. IANA Considerations 337 IANA has returned the DHCP option codes listed in Section 2 to the 338 list of available option codes. These option codes may be reassigned 339 to new DHCP options, according to the procedures in RFC 2939 [6]. 340 IANA is requested to reassign these option codes after the list of 341 option codes that have never been assigned or have previously been 342 returned has been exhausted. 344 Informative References 346 [1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", 347 http://www.iana.org/assignments/bootp-dhcp-parameters, 348 February 2003. 350 [2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, 351 January 2001. 353 [3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, 354 G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", 355 draft-ietf-dhc-failover-12.txt (work in progress), November 356 2002. 358 [4] Intel Corporation, "Preboot Execution Environment (PXE) 359 Specification Version 2.1", http://www.pix.net/software/pxeboot/ 360 archive/pxespec.pdf, September 1999. 362 [5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options 363 Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in 364 progress), February 2003. 366 [6] Droms, R., "Procedures and IANA Guidelines for Definition of New 367 DHCP Options and Message Types", BCP 43, RFC 2939, September 368 2000. 370 Author's Address 372 Ralph Droms 373 Cisco Systems 374 1414 Massachusetts Avenue 375 Boxborough, MA 01719 376 USA 378 Phone: +1 978 936 1674 379 EMail: rdroms@cisco.com 381 Intellectual Property Statement 383 The IETF takes no position regarding the validity or scope of any 384 intellectual property or other rights that might be claimed to 385 pertain to the implementation or use of the technology described in 386 this document or the extent to which any license under such rights 387 might or might not be available; neither does it represent that it 388 has made any effort to identify any such rights. Information on the 389 IETF's procedures with respect to rights in standards-track and 390 standards-related documentation can be found in BCP-11. Copies of 391 claims of rights made available for publication and any assurances of 392 licenses to be made available, or the result of an attempt made to 393 obtain a general license or permission for the use of such 394 proprietary rights by implementors or users of this specification can 395 be obtained from the IETF Secretariat. 397 The IETF invites any interested party to bring to its attention any 398 copyrights, patents or patent applications, or other proprietary 399 rights which may cover technology that may be required to practice 400 this standard. Please address the information to the IETF Executive 401 Director. 403 Full Copyright Statement 405 Copyright (C) The Internet Society (2003). All Rights Reserved. 407 This document and translations of it may be copied and furnished to 408 others, and derivative works that comment on or otherwise explain it 409 or assist in its implementation may be prepared, copied, published 410 and distributed, in whole or in part, without restriction of any 411 kind, provided that the above copyright notice and this paragraph are 412 included on all such copies and derivative works. However, this 413 document itself may not be modified in any way, such as by removing 414 the copyright notice or references to the Internet Society or other 415 Internet organizations, except as needed for the purpose of 416 developing Internet standards in which case the procedures for 417 copyrights defined in the Internet Standards process must be 418 followed, or as required to translate it into languages other than 419 English. 421 The limited permissions granted above are perpetual and will not be 422 revoked by the Internet Society or its successors or assignees. 424 This document and the information contained herein is provided on an 425 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 426 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 427 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 428 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 429 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 431 Acknowledgment 433 Funding for the RFC Editor function is currently provided by the 434 Internet Society.