idnits 2.17.1 draft-ietf-dhc-unused-optioncodes-01.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. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. 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 (April 11, 2003) is 7685 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' == Outdated reference: A later version (-12) exists of draft-ietf-dhc-failover-11 -- Possible downref: Normative reference to a draft: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' Summary: 3 errors (**), 0 flaws (~~), 3 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: October 10, 2003 April 11, 2003 6 Unused DHCP Option Codes 7 draft-ietf-dhc-unused-optioncodes-01 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 October 10, 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. Service Location Protocol Naming Authority 52 Code: 80 54 Name: Service Location Protocol Naming Authority 56 Defined in: (expired Internet-Draft) 58 Contact: Charlie Perkins 60 Reason to recover: Never published as standard 62 3. Relay Agent Options 64 Codes: 83, 84 66 Name: Relay Agent Options 68 Defined in: Early draft of RFC3046 [2] 70 Contact: (none) 72 Reason to recover: Not defined in RFC3046 as published 74 4. IEEE 1003.1 POSIX Timezone 76 Code: 88 78 Name: IEEE 1003.1 POSIX Timezone 80 Defined in: (expired Internet-Draft) 82 Contact: Mike Carney 84 Reason to recover: Never published as standard 86 5. FQDNs in DHCP Options 88 Code: 89 90 Name: FQDNs in DHCP Options 92 Defined in: (expired Internet-Draft) 94 Contact: Ralph Droms 95 Reason to recover: Never published as standard 97 6. VINES TCP/IP Server 99 Code: 91 101 Name: VINES TCP/IP Server 103 Defined in: (none) 105 Contact: (none) 107 Reason to recover: Never published as Internet-Draft 109 7. Server Selection 111 Code: 92 113 Name: Server Selection 115 Defined in: (none) 117 Contact: (none) 119 Reason to recover: Never published as Internet-Draft 121 8. LDAP Servers 123 Code: 95 125 Name: LDAP Servers 127 Defined in: (none) 129 Contact: (none) 131 Reason to recover: Never published as Internet-Draft 133 9. IPv6 Transition 135 Code: 96 137 Name: IPv6 Transition 138 Defined in: (expired Internet-Draft) 140 Contact: Dan Harrington 142 Reason to recover: Never published as standard 144 10. Printer Name 146 Code: 100 148 Name: Printer Name 150 Defined in: (none) 152 Contact: (none) 154 Reason to recover: Never published as Internet-Draft 156 11. Multicast Assignment through DHCP 158 Code: 101 160 Name: Multicast Assignment through DHCP 162 Defined in: (expired Internet-Draft) 164 Contact: Baiju Patel, Munil Shah 166 Reason to recover: Never published as standard 168 12. Swap Path 170 Code: 108 172 Name: Swap Path 174 Defined in: (none) 176 Contact: (none) 178 Reason to recover: Never published as Internet-Draft 180 13. IPX Compatibility 182 Code: 110 184 Name: IPX Compatibility 186 Defined in: (none) 188 Contact: Juan Luciani 190 Reason to recover: Never published as Internet-Draft 192 14. Netinfo Parameters 194 Codes: 112, 113 196 Name: Netinfo Address, Netinfo Tag 198 Defined in: (none) 200 Contact: Marc Majka 202 Reason to recover: Never published as Internet-Draft 204 15. URL 206 Code: 114 208 Name: URL 210 Defined in: (none) 212 Contact: Vinod Valloppillil 214 Reason to recover: Never published as Internet-Draft 216 16. Failover 218 Code: 115 220 Name: Failover 222 Defined in: Early revisions of "DHCP Failover Protocol" [3] 224 Contact: Kim Kinnear 225 Reason to recover: Current version of "DHCP Failover Protocol" does 226 not use a DHCP option 228 17. Option Code Extensions 230 Codes: 126, 127 232 Name: Option Code Extensions 234 Defined in: (expired Internet-Draft) 236 Contact: Ralph Droms 238 Reason to recover: Never published as standard 240 18. Option codes used in PXE Specification 242 The following option codes are used in the "Preboot Execution 243 Environment (PXE) Specification, Version 2.1" [4]. However, none of 244 these option codes have been specified as a Standards-track RFC. 246 18.1 Client System 248 Code: 93 250 Name: Client System 252 Defined in: (none) 254 Contact: (none) 256 Reason to recover: Never published as Internet-Draft 258 18.2 Client NDI 260 Code: 94 262 Name: Client NDI 264 Defined in: (none) 266 Contact: (none) 268 Reason to recover: Never published as Internet-Draft 270 18.3 UUID/GUID Client Identifier 272 Code: 97 274 Name: UUID/GUID Client Identifier 276 Defined in: (expired Internet-Draft) 278 Contact: Dan Harrington 280 Reason to recover: Never published as standard 282 19. Already Returned for Reassignment 284 The option codes 99, 102-107, 109 and 111 have already been returned 285 for reassignment to future DHCP options. 287 20. IANA Considerations 289 When this document has been published as an Informational RFC, IANA 290 will be requested to return the unused DHCP option codes to the list 291 of available option codes. These option codes may be reassigned to 292 new DHCP options, according to the procedures in RFC 2939 [5]. 294 References 296 [1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", 297 http://www.iana.org/assignments/bootp-dhcp-parameters, 298 February 2003. 300 [2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, 301 January 2001. 303 [3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, 304 G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", draft- 305 ietf-dhc-failover-11.txt (work in progress), November 2002. 307 [4] Intel Corporation, "Preboot Execution Environment (PXE) 308 Specification Version 2.1", 309 http://www.pix.net/software/pxeboot/archive/pxespec.pdf, 310 September 1999. 312 [5] Droms, R., "Procedures and IANA Guidelines for Definition of New 313 DHCP Options and Message Types", BCP 43, RFC 2939, September 314 2000. 316 Author's Address 318 Ralph Droms 319 Cisco Systems 320 250 Apollo Drive 321 Chelmsford, MA 01824 322 USA 324 Phone: +1 978 497 4733 325 EMail: rdroms@cisco.com 327 Full Copyright Statement 329 Copyright (C) The Internet Society (2003). All Rights Reserved. 331 This document and translations of it may be copied and furnished to 332 others, and derivative works that comment on or otherwise explain it 333 or assist in its implementation may be prepared, copied, published 334 and distributed, in whole or in part, without restriction of any 335 kind, provided that the above copyright notice and this paragraph are 336 included on all such copies and derivative works. However, this 337 document itself may not be modified in any way, such as by removing 338 the copyright notice or references to the Internet Society or other 339 Internet organizations, except as needed for the purpose of 340 developing Internet standards in which case the procedures for 341 copyrights defined in the Internet Standards process must be 342 followed, or as required to translate it into languages other than 343 English. 345 The limited permissions granted above are perpetual and will not be 346 revoked by the Internet Society or its successors or assigns. 348 This document and the information contained herein is provided on an 349 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 350 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 351 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 352 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 353 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 355 Acknowledgement 357 Funding for the RFC Editor function is currently provided by the 358 Internet Society.