idnits 2.17.1 draft-droms-dhc-dhcpv6-iana-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5678, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC5007, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC3315, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC3315, updated by this document, for RFC5378 checks: 1995-02-03) -- 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 (July 5, 2010) is 5016 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) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 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 4 Updates: 3315, 5007, 5678 July 5, 2010 5 (if approved) 6 Intended status: Standards Track 7 Expires: January 6, 2011 9 IANA Rules for DHCPv6 (Dynamic Host Configuration Protocol for IPv6) 10 Registries 11 draft-droms-dhc-dhcpv6-iana-00.txt 13 Abstract 15 This document modifies the IANA rules for some DHCPv6 (Dynamic Host 16 Configuration Protocol for IPv6) registries. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on January 6, 2011. 35 Copyright Notice 37 Copyright (c) 2010 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 1. Introduction 52 This document modifies the IANA rules for some DHCPv6 (Dynamic Host 53 Configuration Protocol for IPv6) [RFC3315] registries. Rules for the 54 following protocol registries are affected: 56 o DHCP Message Types [RFC3315] 58 o DHCP Option Codes [RFC3315] 60 o Status Codes [RFC3315] 62 o DUIDs [RFC3315] 64 o OPTION_LQ_QUERY Option [RFC5007] 66 o IEEE 802.21 Service Type [RFC5678] 68 The rules for these registries are modified because there can be 69 situations in which it is reasonable to grant an allocation in one of 70 these registries under special circumstances. Other DHCPv6 71 registries already use "Standards Action or IESG Approval" as the 72 Registration Procedures. 74 In addition to changing the Registration Procedures for the DHCP 75 Message Types registry, four new DHCP Message Types are added for use 76 in experimentation and testing. 78 The IESG, when this document was written in June, 2010, was reviewing 79 a document for publication that required a new registration in the 80 DHCP Option Codes registry. The document defined a new DHCPv6 option 81 defined by the SIP Forum, but was an independent submission to the 82 IESG and intended for Informational Status. Thus, the document would 83 not meet the Option Code Registration Procedures of "Expert Review 84 and Standards Action". By changing the Option Codes Registration 85 Procedures to "Standards Action or IESG Approval", the IESG can 86 approve such registrations after review and consideration of the 87 special circumstances. 89 2. IANA Considerations 91 IANA is requested to update the Registration Procedures for the 92 DHCPv6 registries DHCP Message Types, DHCP Option Codes, Status 93 Codes, DUIDs, OPTION_LQ_QUERY option and IEEE 802.21 Service Type as 94 specified below. In addition, IANA is requested to add four new DHCP 95 Message Types, which are to be used for experimentation and testing. 96 All other DHCPv6 IANA Registrations Procedures are to remain 97 unchanged. 99 2.1. DHCP Message Types 101 The Registration Procedures for the DHCP Message Types registry are 102 "Standards Action or IESG Approval." Previously, the Registration 103 Procedures were "Expert Review and Standards Action." 105 The following four DHCP Message Type values are reserved for 106 experimentation and testing: 108 Value Description Reference 109 ----- ----------- --------- 110 65532 (0xfffc) EXPERIMENTAL [thisRFC] 111 65533 (0xfffd) EXPERIMENTAL [thisRFC] 112 65534 (0xfffe) EXPERIMENTAL [thisRFC] 113 65535 (0xffff) EXPERIMENTAL [thisRFC] 115 As these message types reserved for experimental and testing 116 purposes, no guarantee is made for interoperability among DHCPv6 117 clients, servers and relay agents that use these experimental message 118 types. 120 2.2. DHCP Option Codes 122 The Registration Procedures for the DHCP Option Code registry are 123 "Standards Action or IESG Approval." Previously, the Registration 124 Procedures were "Expert Review and Standards Action." 126 2.3. Status Codes 128 The Registration Procedures for the Status Codes registry are 129 "Standards Action or IESG Approval." Previously, the Registration 130 Procedures were "Standards Action." 132 2.4. DUIDs 134 The Registration Procedures for the DUIDs registry are "Standards 135 Action or IESG Approval." Previously, the Registration Procedures 136 were "Standards Action." 138 2.5. OPTION_LQ_QUERY option 140 The Registration Procedures for the OPTION_LQ_QUERY option registry 141 are "Standards Action or IESG Approval." Previously, the 142 Registration Procedures were "Standards Action." 144 2.6. IEEE 802.21 Service Type 146 The Registration Procedures for the IEEE 802.21 Service Type registry 147 are "Standards Action or IESG Approval." Previously, the 148 Registration Procedures were "Standards Action." 150 3. Security Considerations 152 This specification does not change the security properties of DHCPv6 153 and the specific components of DHCPv6 documented in the affected 154 registries. 156 4. Normative References 158 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 159 and M. Carney, "Dynamic Host Configuration Protocol for 160 IPv6 (DHCPv6)", RFC 3315, July 2003. 162 [RFC5007] Brzozowski, J., Kinnear, K., Volz, B., and S. Zeng, 163 "DHCPv6 Leasequery", RFC 5007, September 2007. 165 [RFC5678] Bajko, G. and S. Das, "Dynamic Host Configuration Protocol 166 (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility 167 Services (MoS) Discovery", RFC 5678, December 2009. 169 Appendix A. Changes from RFC 3315, RFC 5007 and RFC 5678 171 This document changes the IANA Registration Procedures for the DHCPv6 172 DHCP Message Types, DHCP Option Codes, Status Codes, DUIDs, 173 OPTION_LQ_QUERY option and IEEE 802.21 Service Type registries. Ir 174 also adds four DHCP Message Type values, which are reserved for 175 experimentation and testing. 177 Author's Address 179 Ralph Droms 180 Cisco 181 1414 Massachusetts Avenue 182 Boxborough 01719 183 USA 185 Email: rdroms.ietf@gmail.com