idnits 2.17.1 draft-ietf-dhc-unused-optioncodes-05.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 : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. 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 (June 2003) is 7622 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: 2 errors (**), 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: November 30, 2003 June 2003 6 Unused DHCP Option Codes 7 draft-ietf-dhc-unused-optioncodes-05 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 November 30, 2003. 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 LDAP Servers 139 Code: 95 141 Name: LDAP Servers 143 Defined in: (none) 145 Contact: (none) 147 Reason to recover: Never published as Internet-Draft 149 2.8 IPv6 Transition 151 Code: 96 153 Name: IPv6 Transition 155 Defined in: (expired Internet-Draft) 157 Contact: Dan Harrington; agrees that option code should be 158 reassigned 160 Reason to recover: Never published as standard and not in general use 162 2.9 Printer Name 164 Code: 100 166 Name: Printer Name 168 Defined in: (none) 170 Contact: (none) 172 Reason to recover: Never published as Internet-Draft 174 2.10 Multicast Assignment through DHCP 176 Code: 101 178 Name: Multicast Assignment through DHCP 179 Defined in: (expired Internet-Draft) 181 Contact: Baiju Patel, Munil Shah 183 Reason to recover: Never published as standard and not in general use 185 2.11 Swap Path 187 Code: 108 189 Name: Swap Path 191 Defined in: (none) 193 Contact: (none) 195 Reason to recover: Never published as Internet-Draft 197 2.12 IPX Compatibility 199 Code: 110 201 Name: IPX Compatibility 203 Defined in: (none) 205 Contact: Juan Luciani; agrees that option code should be 206 reassigned 208 Reason to recover: Never published as Internet-Draft 210 2.13 Netinfo Parameters 212 Codes: 112, 113 214 Name: Netinfo Address, Netinfo Tag 216 Defined in: (none) 218 Contact: Marc Majka 220 Reason to recover: Never published as Internet-Draft 222 2.14 URL 224 Code: 114 226 Name: URL 228 Defined in: (none) 230 Contact: Vinod Valloppillil 232 Reason to recover: Never published as Internet-Draft 234 2.15 Failover 236 Code: 115 238 Name: Failover 240 Defined in: Early revisions of "DHCP Failover Protocol" [3] 242 Contact: Kim Kinnear 244 Reason to recover: Current version of "DHCP Failover Protocol" does 245 not use a DHCP option 247 3. Option codes to be reserved by IANA 249 The option codes listed in this section are the subject of ongoing 250 work in the dhc working group. These options codes should remain on 251 the IANA list of assigned option codes [1] until the dhc working 252 group has made a final decision about their disposition. 254 3.1 Option codes used in PXE Specification 256 The following option codes are used in the "Preboot Execution 257 Environment (PXE) Specification, Version 2.1" [4]. However, although 258 these options are in widespread use by devices that use PXE, none of 259 these option codes have been described in a published RFC. 261 The dhc WG will endeavor to have specifications for these options 262 published. 264 3.1.1 Client System 265 Code: 93 267 Name: Client System 269 Defined in: "Preboot Execution Environment (PXE) 270 Specification, Version 2.1" [4] 272 Contact: Michael Johnston 274 3.1.2 Client NDI 276 Code: 94 278 Name: Client NDI 280 Defined in: "Preboot Execution Environment (PXE) 281 Specification, Version 2.1" [4] 283 Contact: Michael Johnston 285 3.1.3 UUID/GUID Client Identifier 287 Code: 97 289 Name: UUID/GUID Client Identifier 291 Defined in: "Preboot Execution Environment (PXE) 292 Specification, Version 2.1" [4] (and an expired Internet-Draft) 294 Contact: Dan Harrington, Michael Johnston 296 3.2 Option Code Extensions 298 Note that these option codes are identified in "Extending DHCP 299 Options Codes" [5] as part of a mechanism for extending the set of 300 option codes available to DHCP. If these option codes are not used 301 for DHCP option code extension, they will be returned to IANA for 302 reassignment to other DHCP options. 304 Codes: 126, 127 306 Name: Option Code Extensions 307 Defined in: (expired Internet-Draft) 309 Contact: Ralph Droms 311 4. Already Returned for Reassignment 313 The option codes 99, 102-107, 109 and 111 have already been returned 314 for reassignment to future DHCP options. 316 5. IANA Considerations 318 When this document has been published as an Informational RFC, IANA 319 will be requested to return the unused DHCP option codes to the list 320 of available option codes. These option codes may be reassigned to 321 new DHCP options, according to the procedures in RFC 2939 [6]. 323 Informative References 325 [1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", 326 http://www.iana.org/assignments/bootp-dhcp-parameters, 327 February 2003. 329 [2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, 330 January 2001. 332 [3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, 333 G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", 334 draft-ietf-dhc-failover-12.txt (work in progress), November 335 2002. 337 [4] Intel Corporation, "Preboot Execution Environment (PXE) 338 Specification Version 2.1", http://www.pix.net/software/pxeboot/ 339 archive/pxespec.pdf, September 1999. 341 [5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options 342 Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in 343 progress), February 2003. 345 [6] Droms, R., "Procedures and IANA Guidelines for Definition of New 346 DHCP Options and Message Types", BCP 43, RFC 2939, September 347 2000. 349 Author's Address 351 Ralph Droms 352 Cisco Systems 353 1414 Massachusetts Avenue 354 Boxborough, MA 01719 355 USA 357 Phone: +1 978 936 1674 358 EMail: rdroms@cisco.com 360 Intellectual Property Statement 362 The IETF takes no position regarding the validity or scope of any 363 intellectual property or other rights that might be claimed to 364 pertain to the implementation or use of the technology described in 365 this document or the extent to which any license under such rights 366 might or might not be available; neither does it represent that it 367 has made any effort to identify any such rights. Information on the 368 IETF's procedures with respect to rights in standards-track and 369 standards-related documentation can be found in BCP-11. Copies of 370 claims of rights made available for publication and any assurances of 371 licenses to be made available, or the result of an attempt made to 372 obtain a general license or permission for the use of such 373 proprietary rights by implementors or users of this specification can 374 be obtained from the IETF Secretariat. 376 The IETF invites any interested party to bring to its attention any 377 copyrights, patents or patent applications, or other proprietary 378 rights which may cover technology that may be required to practice 379 this standard. Please address the information to the IETF Executive 380 Director. 382 Full Copyright Statement 384 Copyright (C) The Internet Society (2003). All Rights Reserved. 386 This document and translations of it may be copied and furnished to 387 others, and derivative works that comment on or otherwise explain it 388 or assist in its implementation may be prepared, copied, published 389 and distributed, in whole or in part, without restriction of any 390 kind, provided that the above copyright notice and this paragraph are 391 included on all such copies and derivative works. However, this 392 document itself may not be modified in any way, such as by removing 393 the copyright notice or references to the Internet Society or other 394 Internet organizations, except as needed for the purpose of 395 developing Internet standards in which case the procedures for 396 copyrights defined in the Internet Standards process must be 397 followed, or as required to translate it into languages other than 398 English. 400 The limited permissions granted above are perpetual and will not be 401 revoked by the Internet Society or its successors or assignees. 403 This document and the information contained herein is provided on an 404 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 405 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 406 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 407 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 408 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 410 Acknowledgment 412 Funding for the RFC Editor function is currently provided by the 413 Internet Society.