idnits 2.17.1 draft-ietf-dhc-unused-optioncodes-04.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 27, 2003) is 7602 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: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Normative reference to a draft: ref. '3' Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 5 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 26, 2003 June 27, 2003 6 Unused DHCP Option Codes 7 draft-ietf-dhc-unused-optioncodes-04 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 26, 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 DHCP Option Codes to be Reassigned to Future DHCP Options 52 The option codes listed in this section are to be returned to IANA 53 for reassignment to new options. Responses from associated contact 54 persons are noted where they have been received. 56 2.1 Service Location Protocol Naming Authority 58 Code: 80 60 Name: Service Location Protocol Naming Authority 62 Defined in: (expired Internet-Draft) 64 Contact: Charlie Perkins 66 Reason to recover: Never published as standard and not in general use 68 2.2 Relay Agent Options 70 Codes: 83, 84 72 Name: Relay Agent Options 74 Defined in: Early draft of RFC3046 [4] 76 Contact: (none) 78 Reason to recover: Not defined in RFC3046 as published 80 2.3 IEEE 1003.1 POSIX Timezone 82 Code: 88 84 Name: IEEE 1003.1 POSIX Timezone 86 Defined in: (expired Internet-Draft) 88 Contact: Mike Carney 90 Reason to recover: Never published as standard and not in general use 92 2.4 FQDNs in DHCP Options 94 Code: 89 96 Name: FQDNs in DHCP Options 98 Defined in: (expired Internet-Draft) 100 Contact: Ralph Droms; agrees that option code should be 101 reassigned 103 Reason to recover: Never published as standard and not in general use 105 2.5 VINES TCP/IP Server 107 Code: 91 109 Name: VINES TCP/IP Server 111 Defined in: (none) 113 Contact: (none) 115 Reason to recover: Never published as Internet-Draft 117 2.6 Server Selection 119 Code: 92 121 Name: Server Selection 123 Defined in: (none) 125 Contact: (none) 127 Reason to recover: Never published as Internet-Draft 129 2.7 LDAP Servers 131 Code: 95 133 Name: LDAP Servers 135 Defined in: (none) 136 Contact: (none) 138 Reason to recover: Never published as Internet-Draft 140 2.8 IPv6 Transition 142 Code: 96 144 Name: IPv6 Transition 146 Defined in: (expired Internet-Draft) 148 Contact: Dan Harrington; agrees that option code should be 149 reassigned 151 Reason to recover: Never published as standard and not in general use 153 2.9 Printer Name 155 Code: 100 157 Name: Printer Name 159 Defined in: (none) 161 Contact: (none) 163 Reason to recover: Never published as Internet-Draft 165 2.10 Multicast Assignment through DHCP 167 Code: 101 169 Name: Multicast Assignment through DHCP 171 Defined in: (expired Internet-Draft) 173 Contact: Baiju Patel, Munil Shah 175 Reason to recover: Never published as standard and not in general use 177 2.11 Swap Path 179 Code: 108 181 Name: Swap Path 183 Defined in: (none) 185 Contact: (none) 187 Reason to recover: Never published as Internet-Draft 189 2.12 IPX Compatibility 191 Code: 110 193 Name: IPX Compatibility 195 Defined in: (none) 197 Contact: Juan Luciani; agress that option code should be 198 reassigned 200 Reason to recover: Never published as Internet-Draft 202 2.13 Netinfo Parameters 204 Codes: 112, 113 206 Name: Netinfo Address, Netinfo Tag 208 Defined in: (none) 210 Contact: Marc Majka 212 Reason to recover: Never published as Internet-Draft 214 2.14 URL 216 Code: 114 218 Name: URL 220 Defined in: (none) 221 Contact: Vinod Valloppillil 223 Reason to recover: Never published as Internet-Draft 225 2.15 Failover 227 Code: 115 229 Name: Failover 231 Defined in: Early revisions of "DHCP Failover Protocol" [5] 233 Contact: Kim Kinnear 235 Reason to recover: Current version of "DHCP Failover Protocol" does 236 not use a DHCP option 238 3. Option codes used in PXE Specification 240 The following option codes are used in the "Preboot Execution 241 Environment (PXE) Specification, Version 2.1" [2]. However, although 242 these options are in widespread use by devices that use PXE, none of 243 these option codes have been described in a published RFC. 245 The dhc WG will endeavor to have specifications for these options 246 published. 248 3.1 Client System 250 Code: 93 252 Name: Client System 254 Defined in: "Preboot Execution Environment (PXE) 255 Specification, Version 2.1" [2] 257 Contact: Michael Johnston 259 3.2 Client NDI 261 Code: 94 263 Name: Client NDI 265 Defined in: "Preboot Execution Environment (PXE) 266 Specification, Version 2.1" [2] 268 Contact: Michael Johnston 270 3.3 UUID/GUID Client Identifier 272 Code: 97 274 Name: UUID/GUID Client Identifier 276 Defined in: "Preboot Execution Environment (PXE) 277 Specification, Version 2.1" [2] (and an expired Internet-Draft) 279 Contact: Dan Harrington, Michael Johnston 281 4. Option Code Extensions 283 Note that these option codes are identified in draft-volz-dhc- 284 extended-optioncodes-00 [3] as part of a mechanism for extending the 285 set of option codes available to DHCP. If these option codes are not 286 used for DHCP option code extension, they will be returned to IANA 287 for reassignment to other DHCP options. 289 Codes: 126, 127 291 Name: Option Code Extensions 293 Defined in: (expired Internet-Draft) 295 Contact: Ralph Droms 297 Reason to recover: Never published as standard; note that these 298 option codes are mentioned in "Extending DHCP Options Codes" [3]. 300 5. Already Returned for Reassignment 302 The option codes 99, 102-107, 109 and 111 have already been returned 303 for reassignment to future DHCP options. 305 6. IANA Considerations 307 When this document has been published as an Informational RFC, IANA 308 will be requested to return the unused DHCP option codes to the list 309 of available option codes. These option codes may be reassigned to 310 new DHCP options, according to the procedures in RFC 2939 [6]. 312 Normative References 314 [1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", 315 http://www.iana.org/assignments/bootp-dhcp-parameters, 316 February 2003. 318 [2] Intel Corporation, "Preboot Execution Environment (PXE) 319 Specification Version 2.1", 320 http://www.pix.net/software/pxeboot/archive/pxespec.pdf, 321 September 1999. 323 [3] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options 324 Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in 325 progress), September 2000. 327 Informative References 329 [4] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, 330 January 2001. 332 [5] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, 333 G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", draft- 334 ietf-dhc-failover-12.txt (work in progress), November 2002. 336 [6] Droms, R., "Procedures and IANA Guidelines for Definition of New 337 DHCP Options and Message Types", BCP 43, RFC 2939, September 338 2000. 340 Author's Address 342 Ralph Droms 343 Cisco Systems 344 1414 Massachusetts Avenue 345 Boxborough, MA 01719 346 USA 348 Phone: +1 978 936 1674 349 EMail: rdroms@cisco.com 351 Full Copyright Statement 353 Copyright (C) The Internet Society (2003). All Rights Reserved. 355 This document and translations of it may be copied and furnished to 356 others, and derivative works that comment on or otherwise explain it 357 or assist in its implementation may be prepared, copied, published 358 and distributed, in whole or in part, without restriction of any 359 kind, provided that the above copyright notice and this paragraph are 360 included on all such copies and derivative works. However, this 361 document itself may not be modified in any way, such as by removing 362 the copyright notice or references to the Internet Society or other 363 Internet organizations, except as needed for the purpose of 364 developing Internet standards in which case the procedures for 365 copyrights defined in the Internet Standards process must be 366 followed, or as required to translate it into languages other than 367 English. 369 The limited permissions granted above are perpetual and will not be 370 revoked by the Internet Society or its successors or assigns. 372 This document and the information contained herein is provided on an 373 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 374 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 375 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 376 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 377 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 379 Acknowledgement 381 Funding for the RFC Editor function is currently provided by the 382 Internet Society.