idnits 2.17.1 draft-ietf-dhc-unused-optioncodes-00.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 an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** 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 (February 19, 2003) is 7736 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' Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 4 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: August 20, 2003 February 19, 2003 6 Unused DHCP Option Codes 7 draft-ietf-dhc-unused-optioncodes-00 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 August 20, 2003. 32 Copyright Notice 34 Copyright (C) The Internet Society (2003). All Rights Reserved. 36 Abstract 38 Prior to the publication of RFC2939 (which was updated by RFC2489), 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. Client System 123 Code: 93 125 Name: Client System 127 Defined in: (none) 129 Contact: (none) 131 Reason to recover: Never published as Internet-Draft 133 9. Client NDI 135 Code: 94 137 Name: Client NDI 138 Defined in: (none) 140 Contact: (none) 142 Reason to recover: Never published as Internet-Draft 144 10. LDAP Servers 146 Code: 95 148 Name: LDAP Servers 150 Defined in: (none) 152 Contact: (none) 154 Reason to recover: Never published as Internet-Draft 156 11. IPv6 Transition 158 Code: 96 160 Name: IPv6 Transition 162 Defined in: (expired Internet-Draft) 164 Contact: Dan Harrington 166 Reason to recover: Never published as standard 168 12. UUID/GUID Client Identifier 170 Code: 97 172 Name: UUID/GUID Client Identifier 174 Defined in: (expired Internet-Draft) 176 Contact: Dan Harrington 178 Reason to recover: Never published as standard 180 13. Printer Name 182 Code: 100 184 Name: Printer Name 186 Defined in: (none) 188 Contact: (none) 190 Reason to recover: Never published as Internet-Draft 192 14. Multicast Assignment through DHCP 194 Code: 101 196 Name: Multicast Assignment through DHCP 198 Defined in: (expired Internet-Draft) 200 Contact: Baiju Patel, Munil Shah 202 Reason to recover: Never published as standard 204 15. Swap Path 206 Code: 108 208 Name: Swap Path 210 Defined in: (none) 212 Contact: (none) 214 Reason to recover: Never published as Internet-Draft 216 16. IPX Compatibility 218 Code: 110 220 Name: IPX Compatibility 222 Defined in: (none) 224 Contact: Juan Luciani 225 Reason to recover: Never published as Internet-Draft 227 17. Netinfo Parameters 229 Codes: 112, 113 231 Name: Netinfo Address, Netinfo Tag 233 Defined in: (none) 235 Contact: Marc Majka 237 Reason to recover: Never published as Internet-Draft 239 18. URL 241 Code: 114 243 Name: URL 245 Defined in: (none) 247 Contact: Vinod Valloppillil 249 Reason to recover: Never published as Internet-Draft 251 19. Failover 253 Code: 115 255 Name: Failover 257 Defined in: Early revisions of "DHCP Failover Protocol" [3] 259 Contact: Kim Kinnear 261 Reason to recover: Current version of "DHCP Failover Protocol" does 262 not use a DHCP option 264 20. Option Code Extensions 266 Codes: 126, 127 268 Name: Option Code Extensions 269 Defined in: (expired Internet-Draft) 271 Contact: Ralph Droms 273 Reason to recover: Never published as standard 275 21. Already Returned for Reassignment 277 The option codes 99, 102-107, 109 and 111 have already been returned 278 for reassignment to future DHCP options. 280 References 282 [1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", 283 http://www.iana.org/assignments/bootp-dhcp-parameters, 284 February 2003. 286 [2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, 287 January 2001. 289 [3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, 290 G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", draft- 291 ietf-dhc-failover-11.txt (work in progress), November 2002. 293 Author's Address 295 Ralph Droms 296 Cisco Systems 297 250 Apollo Drive 298 Chelmsford, MA 01824 299 USA 301 Phone: +1 978 497 4733 302 EMail: rdroms@cisco.com 304 Full Copyright Statement 306 Copyright (C) The Internet Society (2003). All Rights Reserved. 308 This document and translations of it may be copied and furnished to 309 others, and derivative works that comment on or otherwise explain it 310 or assist in its implementation may be prepared, copied, published 311 and distributed, in whole or in part, without restriction of any 312 kind, provided that the above copyright notice and this paragraph are 313 included on all such copies and derivative works. However, this 314 document itself may not be modified in any way, such as by removing 315 the copyright notice or references to the Internet Society or other 316 Internet organizations, except as needed for the purpose of 317 developing Internet standards in which case the procedures for 318 copyrights defined in the Internet Standards process must be 319 followed, or as required to translate it into languages other than 320 English. 322 The limited permissions granted above are perpetual and will not be 323 revoked by the Internet Society or its successors or assigns. 325 This document and the information contained herein is provided on an 326 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 327 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 328 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 329 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 330 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 332 Acknowledgement 334 Funding for the RFC Editor function is currently provided by the 335 Internet Society.