idnits 2.17.1 draft-ietf-dhc-unused-optioncodes-03.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 7, 2003) is 7628 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Normative reference to a draft: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' -- Possible downref: Normative reference to a draft: ref. '5' Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Droms 3 Internet-Draft Cisco Systems 4 Expires: December 6, 2003 June 7, 2003 6 Unused DHCP Option Codes 7 draft-ietf-dhc-unused-optioncodes-03 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 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt. 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This Internet-Draft will expire on December 6, 2003. 32 Copyright Notice 34 Copyright (C) The Internet Society (2003). All Rights Reserved. 36 Abstract 38 Prior to the publication of RFC2489 (which was updated by RFC2939), 39 several option codes were assigned to proposed DHCP options that were 40 subsequently never used. This document lists those unused option 41 codes and will be used to confirm that these option codes can be 42 reused for other DHCP options in the future. 44 1. Introduction 46 This document lists the unused DHCP option codes from the IANA list 47 of BOOTP and DHCP option codes [1]. Each option code includes any 48 known documentation and contact information from the IANA list. 50 2. Unused Option Codes 52 The option codes listed in this section are to be returned to IANA 53 for reassignment to new options. 55 2.1 Service Location Protocol Naming Authority 57 Code: 80 59 Name: Service Location Protocol Naming Authority 61 Defined in: (expired Internet-Draft) 63 Contact: Charlie Perkins 65 Reason to recover: Never published as standard and not in general use 67 2.2 Relay Agent Options 69 Codes: 83, 84 71 Name: Relay Agent Options 73 Defined in: Early draft of RFC3046 [2] 75 Contact: (none) 77 Reason to recover: Not defined in RFC3046 as published 79 2.3 IEEE 1003.1 POSIX Timezone 81 Code: 88 83 Name: IEEE 1003.1 POSIX Timezone 85 Defined in: (expired Internet-Draft) 87 Contact: Mike Carney 89 Reason to recover: Never published as standard and not in general use 91 2.4 FQDNs in DHCP Options 93 Code: 89 94 Name: FQDNs in DHCP Options 96 Defined in: (expired Internet-Draft) 98 Contact: Ralph Droms 100 Reason to recover: Never published as standard and not in general use 102 2.5 VINES TCP/IP Server 104 Code: 91 106 Name: VINES TCP/IP Server 108 Defined in: (none) 110 Contact: (none) 112 Reason to recover: Never published as Internet-Draft 114 2.6 Server Selection 116 Code: 92 118 Name: Server Selection 120 Defined in: (none) 122 Contact: (none) 124 Reason to recover: Never published as Internet-Draft 126 2.7 LDAP Servers 128 Code: 95 130 Name: LDAP Servers 132 Defined in: (none) 134 Contact: (none) 136 Reason to recover: Never published as Internet-Draft 138 2.8 IPv6 Transition 140 Code: 96 142 Name: IPv6 Transition 144 Defined in: (expired Internet-Draft) 146 Contact: Dan Harrington 148 Reason to recover: Never published as standard and not in general use 150 2.9 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.10 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.11 Swap Path 176 Code: 108 178 Name: Swap Path 180 Defined in: (none) 182 Contact: (none) 183 Reason to recover: Never published as Internet-Draft 185 2.12 IPX Compatibility 187 Code: 110 189 Name: IPX Compatibility 191 Defined in: (none) 193 Contact: Juan Luciani 195 Reason to recover: Never published as Internet-Draft 197 2.13 Netinfo Parameters 199 Codes: 112, 113 201 Name: Netinfo Address, Netinfo Tag 203 Defined in: (none) 205 Contact: Marc Majka 207 Reason to recover: Never published as Internet-Draft 209 2.14 URL 211 Code: 114 213 Name: URL 215 Defined in: (none) 217 Contact: Vinod Valloppillil 219 Reason to recover: Never published as Internet-Draft 221 2.15 Failover 223 Code: 115 225 Name: Failover 226 Defined in: Early revisions of "DHCP Failover Protocol" [3] 228 Contact: Kim Kinnear 230 Reason to recover: Current version of "DHCP Failover Protocol" does 231 not use a DHCP option 233 3. Option codes used in PXE Specification 235 The following option codes are used in the "Preboot Execution 236 Environment (PXE) Specification, Version 2.1" [4]. However, although 237 these options are in widespread use by devices that use PXE, none of 238 these option codes have been specified as a Standards-track RFC. 240 The dhc WG will endeavor to have specifications for these options 241 published. 243 3.1 Client System 245 Code: 93 247 Name: Client System 249 Defined in: (none) 251 Contact: (none) 253 3.2 Client NDI 255 Code: 94 257 Name: Client NDI 259 Defined in: (none) 261 Contact: (none) 263 3.3 UUID/GUID Client Identifier 265 Code: 97 267 Name: UUID/GUID Client Identifier 269 Defined in: (expired Internet-Draft) 270 Contact: Dan Harrington 272 4. Option Code Extensions 274 Note that these option codes are identified in draft-volz-dhc- 275 extended-optioncodes-00 [5] as part of a mechanism for extending the 276 set of option codes available to DHCP. If these option codes are not 277 used for DHCP option code extension, they will be returned to IANA 278 for reassignment to other DHCP options. 280 Codes: 126, 127 282 Name: Option Code Extensions 284 Defined in: (expired Internet-Draft) 286 Contact: Ralph Droms 288 Reason to recover: Never published as standard; note that these 289 option codes are mentioned in "Extending DHCP Options Codes" [5]. 291 5. Already Returned for Reassignment 293 The option codes 99, 102-107, 109 and 111 have already been returned 294 for reassignment to future DHCP options. 296 6. IANA Considerations 298 When this document has been published as an Informational RFC, IANA 299 will be requested to return the unused DHCP option codes to the list 300 of available option codes. These option codes may be reassigned to 301 new DHCP options, according to the procedures in RFC 2939 [6]. 303 Normative References 305 [1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", 306 http://www.iana.org/assignments/bootp-dhcp-parameters, 307 February 2003. 309 [2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, 310 January 2001. 312 [3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, 313 G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", draft- 314 ietf-dhc-failover-12.txt (work in progress), November 2002. 316 [4] Intel Corporation, , "Preboot Execution Environment (PXE) 317 Specification Version 2.1", 318 http://www.pix.net/software/pxeboot/archive/pxespec.pdf, 319 September 1999. 321 [5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options 322 Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in 323 progress), September 2000. 325 [6] Droms, R., "Procedures and IANA Guidelines for Definition of New 326 DHCP Options and Message Types", BCP 43, RFC 2939, September 327 2000. 329 Author's Address 331 Ralph Droms 332 Cisco Systems 333 250 Apollo Drive 334 Chelmsford, MA 01824 335 USA 337 Phone: +1 978 497 4733 338 EMail: rdroms@cisco.com 340 Full Copyright Statement 342 Copyright (C) The Internet Society (2003). All Rights Reserved. 344 This document and translations of it may be copied and furnished to 345 others, and derivative works that comment on or otherwise explain it 346 or assist in its implementation may be prepared, copied, published 347 and distributed, in whole or in part, without restriction of any 348 kind, provided that the above copyright notice and this paragraph are 349 included on all such copies and derivative works. However, this 350 document itself may not be modified in any way, such as by removing 351 the copyright notice or references to the Internet Society or other 352 Internet organizations, except as needed for the purpose of 353 developing Internet standards in which case the procedures for 354 copyrights defined in the Internet Standards process must be 355 followed, or as required to translate it into languages other than 356 English. 358 The limited permissions granted above are perpetual and will not be 359 revoked by the Internet Society or its successors or assigns. 361 This document and the information contained herein is provided on an 362 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 363 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 364 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 365 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 366 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 368 Acknowledgement 370 Funding for the RFC Editor function is currently provided by the 371 Internet Society.