idnits 2.17.1 draft-ietf-dhc-unused-optioncodes-06.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 (August 12, 2003) is 7562 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 Network Working Group R. Droms 3 Internet-Draft Cisco Systems 4 Expires: February 10, 2004 August 12, 2003 6 Unused DHCP Option Codes 7 draft-ietf-dhc-unused-optioncodes-06 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 February 10, 2004. 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 directs IANA to make these option codes available for 42 assignment to other DHCP options in the future. 44 The document also lists several option codes that are not currently 45 documented in an RFC but should not be made available for 46 reassignment to future DHCP options. 48 1. Introduction 50 Section 2 of this document lists the unused DHCP option codes from 51 the IANA list of BOOTP and DHCP option codes [1]. Each option code 52 includes any known documentation and contact information from the 53 IANA list. IANA will make these option codes available for 54 assignment to other DHCP options in the future. 56 Section 3 lists several DHCP option codes that are not currently 57 documented in an RFC but should not be made available for 58 reassignment to future DHCP options. 60 2. Unused DHCP Option Codes to be Reassigned to Future DHCP Options 62 The option codes listed in this section are to be returned to IANA 63 for reassignment to new options. Responses from associated contact 64 persons are noted where they have been received. 66 2.1 Service Location Protocol Naming Authority 68 Code: 80 70 Name: Service Location Protocol Naming Authority 72 Defined in: (expired Internet-Draft) 74 Contact: Charlie Perkins 76 Reason to recover: Never published as standard and not in general use 78 2.2 Relay Agent Options 80 Codes: 83, 84 82 Name: Relay Agent Options 84 Defined in: Early draft of RFC3046 [2] 86 Contact: (none) 88 Reason to recover: Not defined in RFC3046 as published 90 2.3 IEEE 1003.1 POSIX Timezone 92 Code: 88 93 Name: IEEE 1003.1 POSIX Timezone 95 Defined in: (expired Internet-Draft) 97 Contact: Mike Carney 99 Reason to recover: Never published as standard and not in general use 101 2.4 FQDNs in DHCP Options 103 Code: 89 105 Name: FQDNs in DHCP Options 107 Defined in: (expired Internet-Draft) 109 Contact: Ralph Droms; agrees that option code should be 110 reassigned 112 Reason to recover: Never published as standard and not in general use 114 2.5 VINES TCP/IP Server 116 Code: 91 118 Name: VINES TCP/IP Server 120 Defined in: (none) 122 Contact: (none) 124 Reason to recover: Never published as Internet-Draft 126 2.6 Server Selection 128 Code: 92 130 Name: Server Selection 132 Defined in: (none) 134 Contact: (none) 136 Reason to recover: Never published as Internet-Draft 138 2.7 LDAP Servers 140 Code: 95 142 Name: LDAP Servers 144 Defined in: (none) 146 Contact: (none) 148 Reason to recover: Never published as Internet-Draft 150 2.8 IPv6 Transition 152 Code: 96 154 Name: IPv6 Transition 156 Defined in: (expired Internet-Draft) 158 Contact: Dan Harrington; agrees that option code should be 159 reassigned 161 Reason to recover: Never published as standard and not in general use 163 2.9 Printer Name 165 Code: 100 167 Name: Printer Name 169 Defined in: (none) 171 Contact: (none) 173 Reason to recover: Never published as Internet-Draft 175 2.10 Multicast Assignment through DHCP 177 Code: 101 179 Name: Multicast Assignment through DHCP 181 Defined in: (expired Internet-Draft) 182 Contact: Baiju Patel, Munil Shah 184 Reason to recover: Never published as standard and not in general use 186 2.11 Swap Path 188 Code: 108 190 Name: Swap Path 192 Defined in: (none) 194 Contact: (none) 196 Reason to recover: Never published as Internet-Draft 198 2.12 IPX Compatibility 200 Code: 110 202 Name: IPX Compatibility 204 Defined in: (none) 206 Contact: Juan Luciani; agrees that option code should be 207 reassigned 209 Reason to recover: Never published as Internet-Draft 211 2.13 Netinfo Parameters 213 Codes: 112, 113 215 Name: Netinfo Address, Netinfo Tag 217 Defined in: (none) 219 Contact: Marc Majka 221 Reason to recover: Never published as Internet-Draft 223 2.14 URL 225 Code: 114 227 Name: URL 229 Defined in: (none) 231 Contact: Vinod Valloppillil 233 Reason to recover: Never published as Internet-Draft 235 2.15 Failover 237 Code: 115 239 Name: Failover 241 Defined in: Early revisions of "DHCP Failover Protocol" [3] 243 Contact: Kim Kinnear 245 Reason to recover: Current version of "DHCP Failover Protocol" does 246 not use a DHCP option 248 3. Option codes to be reserved by IANA 250 The option codes listed in this section are the subject of ongoing 251 work in the dhc working group. These options codes should remain on 252 the IANA list of assigned option codes [1] until the dhc working 253 group has made a final decision about their disposition. 255 3.1 Option codes used in PXE Specification 257 The following option codes are used in the "Preboot Execution 258 Environment (PXE) Specification, Version 2.1" [4]. However, although 259 these options are in widespread use by devices that use PXE, none of 260 these option codes have been described in a published RFC. 262 The dhc WG will endeavor to have specifications for these options 263 published. 265 3.1.1 Client System 267 Code: 93 268 Name: Client System 270 Defined in: "Preboot Execution Environment (PXE) 271 Specification, Version 2.1" [4] 273 Contact: Michael Johnston (frenchy@quiet-like-a- 274 panther.org) 276 3.1.2 Client NDI 278 Code: 94 280 Name: Client NDI 282 Defined in: "Preboot Execution Environment (PXE) 283 Specification, Version 2.1" [4] 285 Contact: Michael Johnston (frenchy@quiet-like-a- 286 panther.org) 288 3.1.3 UUID/GUID Client Identifier 290 Code: 97 292 Name: UUID/GUID Client Identifier 294 Defined in: "Preboot Execution Environment (PXE) 295 Specification, Version 2.1" [4] (and an expired Internet-Draft) 297 Contact: Dan Harrington, Michael Johnston (frenchy@quiet- 298 like-a-panther.org) 300 3.2 Option Code Extensions 302 Note that these option codes are identified in "Extending DHCP 303 Options Codes" [5] as part of a mechanism for extending the set of 304 option codes available to DHCP. If these option codes are not used 305 for DHCP option code extension, they will be returned to IANA for 306 reassignment to other DHCP options. 308 Codes: 126, 127 310 Name: Option Code Extensions 312 Defined in: (expired Internet-Draft) 313 Contact: Ralph Droms 315 4. Already Returned for Reassignment 317 The option codes 99, 102-107, 109 and 111 have already been returned 318 for reassignment to future DHCP options. 320 5. Security Considerations 322 This document has no known security implications, as none of the 323 reclaimed options are known to be in use. 325 6. IANA Considerations 327 IANA has returned the DHCP option codes listed in Section 2 to the 328 list of available option codes. These option codes may be reassigned 329 to new DHCP options, according to the procedures in RFC 2939 [6]. 331 Informative References 333 [1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", 334 http://www.iana.org/assignments/bootp-dhcp-parameters, 335 February 2003. 337 [2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, 338 January 2001. 340 [3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, 341 G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", draft- 342 ietf-dhc-failover-12.txt (work in progress), November 2002. 344 [4] Intel Corporation, , "Preboot Execution Environment (PXE) 345 Specification Version 2.1", 346 http://www.pix.net/software/pxeboot/archive/pxespec.pdf, 347 September 1999. 349 [5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options 350 Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in 351 progress), February 2003. 353 [6] Droms, R., "Procedures and IANA Guidelines for Definition of New 354 DHCP Options and Message Types", BCP 43, RFC 2939, September 355 2000. 357 Author's Address 359 Ralph Droms 360 Cisco Systems 361 1414 Massachusetts Avenue 362 Boxborough, MA 01719 363 USA 365 Phone: +1 978 936 1674 366 EMail: rdroms@cisco.com 368 Full Copyright Statement 370 Copyright (C) The Internet Society (2003). All Rights Reserved. 372 This document and translations of it may be copied and furnished to 373 others, and derivative works that comment on or otherwise explain it 374 or assist in its implementation may be prepared, copied, published 375 and distributed, in whole or in part, without restriction of any 376 kind, provided that the above copyright notice and this paragraph are 377 included on all such copies and derivative works. However, this 378 document itself may not be modified in any way, such as by removing 379 the copyright notice or references to the Internet Society or other 380 Internet organizations, except as needed for the purpose of 381 developing Internet standards in which case the procedures for 382 copyrights defined in the Internet Standards process must be 383 followed, or as required to translate it into languages other than 384 English. 386 The limited permissions granted above are perpetual and will not be 387 revoked by the Internet Society or its successors or assigns. 389 This document and the information contained herein is provided on an 390 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 391 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 392 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 393 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 394 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 396 Acknowledgement 398 Funding for the RFC Editor function is currently provided by the 399 Internet Society.