idnits 2.17.00 (12 Aug 2021) /tmp/idnits50068/draft-volz-dhc-3942-status-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 259. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 270. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 277. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 283. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust 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 19, 2007) is 5504 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: 'RFC4578' on line 181 -- Looks like a reference, but probably isn't: 'RFC3942' on line 184 == Outdated reference: draft-raj-dhc-tftp-addr-option has been published as RFC 5859 == Outdated reference: draft-ietf-dhc-pxelinux has been published as RFC 5071 == Outdated reference: draft-ietf-dhc-subnet-alloc has been published as RFC 6656 == Outdated reference: draft-ietf-dhc-vpn-option has been published as RFC 6607 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DHC B. Volz 3 Internet-Draft Cisco Systems, Inc. 4 Intended status: Informational April 19, 2007 5 Expires: October 21, 2007 7 Status of Reclassifying DHCPv4 Options (RFC 3942) 8 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on October 21, 2007. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2007). 39 Abstract 41 This document provides a status report as of April 2007 for the 42 effort to reclassify Dynamic Host Configuration Protocol options 128 43 to 223 as managed by IANA in accordance with RFC 3942. This document 44 further recommends actions to be taken by IANA to update this 45 reclassification effort. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. Summary of Activity . . . . . . . . . . . . . . . . . . . . . . 3 51 3. Recommendations . . . . . . . . . . . . . . . . . . . . . . . . 4 52 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 54 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 55 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 56 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 58 Intellectual Property and Copyright Statements . . . . . . . . . . 7 60 1. Introduction 62 This document provides a status report as of March 2007 for the 63 effort to reclassify Dynamic Host Configuration Protocol (DHCPv4) [2] 64 options 128 to 223 as managed by IANA in accordance with RFC 3942 65 [1]. This document further recommends actions to be taken by IANA to 66 finalize this reclassification effort. 68 RFC 3942 was published in November 2004 and stipulated a process and 69 time table for vendors using options in the 128 to 223 range to 70 request IANA to assign those options to the vendors' use. The time 71 table for the process has elapsed. 73 2. Summary of Activity 75 After the publication of RFC 3942, several vendors and other uses of 76 DHCPv4 options 128 to 223 were reported and IANA placed the following 77 options in the tentatively assigned state in June 2005: 79 128 Reported as used by Intel's PXE [4], Etherboot (etherboot 80 signature of octets e4:45:74:68:00:00), Cablelabs (DOCSIS "full 81 security" server IP address), and Mitel (IP phone software load 82 TFTP server IP address) [5]. 83 129 Reported as used by Intel's PXE [4], Etherboot (kernel options), 84 and Mitel (call server IP address) [5]. 85 130 Reported as used by Intel's PXE [4], Etherboot (ethernet 86 interface), and Mitel (discrimination string - identifies 87 vendor) [5]. 88 131 Reported as used by Intel's PXE [4] and Mitel (remote statistics 89 server IP address) [5]. 90 132 Reported as used by Intel's PXE [4] and Mitel (802.1P VLAN id) 91 [5]. 92 133 Reported as used by Intel's PXE [4] and Mitel (802.1Q L2 93 priority) [5]. 94 134 Reported as used by Intel's PXE [4] and Mitel (diffserv code 95 point) [5]. 96 134 Reported as used by Intel's PXE [4] and Mitel (HTTP proxy for 97 phone-specific applications) [5]. 98 150 Reported as used by Cisco (TFTP server address) [6], Etherboot 99 (usage unknown), and GNU Grub (GRUB configuration path name). 100 175 Reported as used by Etherboot (usage unknown). 101 176 Reported as used by Avaya (IP telephone). 102 177 Reported as used by Etherboot (usage unknown) and by Cablelabs 103 (though that use has been deprecated in favor of option 122 104 [3]). 106 208 Reported as used by PXELINUX (MAGIC) [7]. 107 209 Reported as used by PXELINUX (ConfigFile) [7]. 108 210 Reported as used by PXELINUX (Pathprefix) [7]. 109 211 Reported as used by PXELINUX (Reboottime) [7]. 110 220 Reported as used by Cisco (subnet allocation) [8]. 111 221 Reported as used by Cisco (virtual subnet selection option) [9]. 113 For those options where multiple uses were demonstrated to be in 114 reasonably wide usage, RFC 3942 stipulated that none of the users 115 would be allowed to retain that option number. However, this assumed 116 that each of these users would follow through on the process. 118 Since that time: 119 o The Mitel draft [5] expired in November 2005. 120 o The PXELINUX draft [7] expired in November 2006. And, an updated 121 draft has just been published. 122 o The Cisco TFTP server draft [6] expired in December 2005. And, an 123 updated draft is expected to be published shortly. 124 o The Cisco subnet allocation draft [8] is presently active. 125 o The Cisco virtual subnet selection option [9] expired in December 126 2005. And, an updated draft has just been published. 127 o No internet-draft was ever published for options used by 128 Etherboot, GRUB, or Avaya. 130 3. Recommendations 132 Based on the process and time table specified by RFC 3942, the 133 following actions are recommended: 135 128 Assign to Intel's PXE [4]. 136 129 Assign to Intel's PXE [4]. 137 130 Assign to Intel's PXE [4]. 138 131 Assign to Intel's PXE [4]. 139 132 Assign to Intel's PXE [4]. 140 133 Assign to Intel's PXE [4]. 141 134 Assign to Intel's PXE [4]. 142 134 Assign to Intel's PXE [4]. 143 150 Leave tentatively assigned to Cisco (TFTP server address) 144 pending republication and continued forward process on [6]. 145 175 Move to "Unassigned" (thus available for assignment). 146 176 Move to "Unassigned" (thus available for assignment). 147 177 Move to "Unassigned" (thus available for assignment). 148 208 Leave tentatively assigned to PXELINUX (MAGIC) pending 149 republication and continued forward process on [7]. 151 209 Leave tentatively assigned to PXELINUX (ConfigFile) pending 152 republication and continued forward process on [7]. 153 210 Leave tentatively assigned to PXELINUX (Pathprefix) pending 154 republication and continued forward process on [7]. 155 211 Leave tentatively assigned to PXELINUX (Reboottime) pending 156 republication and continued forward process on [7]. 157 220 Leave tentatively assigned to Cisco (subnet allocation) pending 158 republication and continued forward process on [8]. 159 221 Leave tentatively assigned to Cisco (virtual subnet selection 160 option) pending republication and continued forward process on 161 [9]. 163 4. Security Considerations 165 This document has no security considerations. 167 5. IANA Considerations 169 IANA is requested to update 170 http://www.iana.org/assignments/bootp-dhcp-parameters for options 171 128-135, 150, 175-177, 208-211, 220, and 221 as follows based on the 172 above recommendations: 174 128 PXE - undefined (vendor specific) [RFC4578] 175 129 PXE - undefined (vendor specific) [RFC4578] 176 130 PXE - undefined (vendor specific) [RFC4578] 177 131 PXE - undefined (vendor specific) [RFC4578] 178 132 PXE - undefined (vendor specific) [RFC4578] 179 133 PXE - undefined (vendor specific) [RFC4578] 180 134 PXE - undefined (vendor specific) [RFC4578] 181 135 PXE - undefined (vendor specific) [RFC4578] 182 150 TFTP server address (Tentatively Assigned - 23 Jun 2005 - 183 DRAFT-RAJ-DHC-TFTP-ADDR-OPTION-01.TXT) 184 175-177 Unassigned [RFC3942] 185 208 pxelinux.magic (string) = F1:00:74:7E (241.0.116.126) (Tentatively 186 Assigned - 23 Jun 2005 - DRAFT-IETF-DHC-PXELINUX-01.TXT) 187 209 pxelinux.configfile (text) (Tentatively Assigned - 23 Jun 2005 - 188 DRAFT-IETF-DHC-PXELINUX-01.TXT) 189 210 pxelinux.pathprefix (text) (Tentatively Assigned - 23 Jun 2005 - 190 DRAFT-IETF-DHC-PXELINUX-01.TXT) 191 211 pxelinux.reboottime (unsigned integer 32 bits) (Tentatively 192 Assigned - 23 Jun 2005 - DRAFT-IETF-DHC-PXELINUX-01.TXT) 193 220 Subnet Allocation Option (Tentatively Assigned - 23 Jun 2005 - 194 DRAFT-IETF-DHC-SUBNET-ALLOC-04.TXT) 195 221 Virtual Subnet Selection Option (Tentatively Assigned - 23 Jun 196 2005 - DRAFT-IETF-DHC-VPN-OPTION-06.TXT) 198 6. References 200 6.1. Normative References 202 [1] Volz, B., "Reclassifying Dynamic Host Configuration Protocol 203 version 4 (DHCPv4) Options", RFC 3942, November 2004. 205 6.2. Informative References 207 [2] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, 208 March 1997. 210 [3] Beser, B. and P. Duffy, "Dynamic Host Configuration Protocol 211 (DHCP) Option for CableLabs Client Configuration", RFC 3495, 212 March 2003. 214 [4] Johnston, M. and S. Venaas, "Dynamic Host Configuration Protocol 215 (DHCP) Options for the Intel Preboot eXecution Environment 216 (PXE)", RFC 4578, November 2006. 218 [5] Blatherwick, P., "Mitel Usage of DHCPv4 Vendor Options 128 - 219 135", draft-blatherwick-dhc-mitel-site-options-usage-00 (work in 220 progress), May 2005. 222 [6] Johnson, R., "TFTP Server Address DHCP Option", 223 draft-raj-dhc-tftp-addr-option-01 (work in progress), June 2005. 225 [7] Hankins, D., "PXELINUX Use of 'Site Local' Option Space", 226 draft-ietf-dhc-pxelinux-01 (work in progress), April 2007. 228 [8] Johnson, R., "Subnet Allocation Option", 229 draft-ietf-dhc-subnet-alloc-04 (work in progress), October 2006. 231 [9] Johnson, R., "Virtual Subnet Selection Option", 232 draft-ietf-dhc-vpn-option-06 (work in progress), April 2007. 234 Author's Address 236 Bernard Volz 237 Cisco Systems, Inc. 238 1414 Massachusetts Ave. 239 Boxborough, MA 01719 240 USA 242 Phone: +1 978 936 0000 243 Email: volz@cisco.com 245 Full Copyright Statement 247 Copyright (C) The IETF Trust (2007). 249 This document is subject to the rights, licenses and restrictions 250 contained in BCP 78, and except as set forth therein, the authors 251 retain all their rights. 253 This document and the information contained herein are provided on an 254 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 255 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 256 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 257 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 258 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 259 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 261 Intellectual Property 263 The IETF takes no position regarding the validity or scope of any 264 Intellectual Property Rights or other rights that might be claimed to 265 pertain to the implementation or use of the technology described in 266 this document or the extent to which any license under such rights 267 might or might not be available; nor does it represent that it has 268 made any independent effort to identify any such rights. Information 269 on the procedures with respect to rights in RFC documents can be 270 found in BCP 78 and BCP 79. 272 Copies of IPR disclosures made to the IETF Secretariat and any 273 assurances of licenses to be made available, or the result of an 274 attempt made to obtain a general license or permission for the use of 275 such proprietary rights by implementers or users of this 276 specification can be obtained from the IETF on-line IPR repository at 277 http://www.ietf.org/ipr. 279 The IETF invites any interested party to bring to its attention any 280 copyrights, patents or patent applications, or other proprietary 281 rights that may cover technology that may be required to implement 282 this standard. Please address the information to the IETF at 283 ietf-ipr@ietf.org. 285 Acknowledgment 287 Funding for the RFC Editor function is provided by the IETF 288 Administrative Support Activity (IASA).