idnits 2.17.1 draft-ietf-dnsop-dnssec-iana-cons-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 document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 98: '... [DS-IANA] registries that are not mentioned in this document MAY be...' RFC 2119 keyword, line 100: '... specified as MAY in this document o...' RFC 2119 keyword, line 101: '... from a MUST or a RECOMMENDED to a M...' RFC 2119 keyword, line 109: '... not mentioned in this document MAY be...' RFC 2119 keyword, line 111: '... specified as MAY in this document o...' (1 more instance...) -- The draft header indicates that this document updates RFC3658, 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 RFC3658, updated by this document, for RFC5378 checks: 2001-05-30) -- 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 (22 January 2021) is 1183 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) == Missing Reference: 'DNSKEY-IANA' is mentioned on line 108, but not defined == Missing Reference: 'DS-IANA' is mentioned on line 108, but not defined -- Obsolete informational reference (is this intentional?): RFC 3658 (Obsoleted by RFC 4033, RFC 4034, RFC 4035) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Hoffman 3 Internet-Draft ICANN 4 Updates: 3658, 5155, 6014, 8624 (if approved) 22 January 2021 5 Intended status: Standards Track 6 Expires: 26 July 2021 8 Revised IANA Considerations for DNSSEC 9 draft-ietf-dnsop-dnssec-iana-cons-00 11 Abstract 13 This document changes the review requirements needed to get some 14 DNSSEC algorithms and resource records added to IANA registries. It 15 updates RFC 6014 to include hash algorithms for DS records and NSEC3 16 parameters. It also updates RFC 5155 and RFC 6014, which have 17 requirements for DNSSEC algorithms. It also updates RFC 8624 to say 18 that algorithms that are described in RFCs that are not on standards 19 track are only at the "MAY" level of implementation recommendation. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on 26 July 2021. 38 Copyright Notice 40 Copyright (c) 2021 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 45 license-info) in effect on the date of publication of this document. 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. Code Components 48 extracted from this document must include Simplified BSD License text 49 as described in Section 4.e of the Trust Legal Provisions and are 50 provided without warranty as described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Update to RFC 6014 . . . . . . . . . . . . . . . . . . . . . 2 56 3. Update to RFC 8624 . . . . . . . . . . . . . . . . . . . . . 3 57 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 58 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 59 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 6.1. Normative References . . . . . . . . . . . . . . . . . . 3 61 6.2. Informative References . . . . . . . . . . . . . . . . . 4 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 64 1. Introduction 66 DNSSEC is primarily described in [RFC4033], [RFC4034], and [RFC4035]. 67 DNSSEC commonly uses two resource records beyond those defined in RFC 68 4034: DS [RFC3658] and NSEC3 [RFC5155]. 70 [RFC8126] describes the requirements for listing in the myriad IANA 71 registries. 73 [RFC6014] updated the requirements for how DNSSEC cryptographic 74 algorithm identifiers in the IANA registries are allocated, reducing 75 the requirements from being "Standards Action" to "RFC Required". 76 However, the IANA registry requirements for hash algorithms for DS 77 records and for the hash algorithms used in NSEC3 are still 78 "Standards Action". 80 2. Update to RFC 6014 82 This document updates RFC 6014 to bring the requirements for DS 83 records and NSEC3 hash algorithms in line with the rest of the DNSSEC 84 cryptographic algorithms by allowing any DS or NSEC3 hash algorithms 85 that are fully described in an RFC to have identifiers allocated in 86 the IANA registries. 88 3. Update to RFC 8624 90 This document updates [RFC8624] for all DNSKEY and DS algorithms that 91 are not on standards track. 93 The second paragraph of Section 1.2 of RFC 8624 currently says: 95 This document only provides recommendations with respect to 96 mandatory-to-implement algorithms or algorithms so weak that they 97 cannot be recommended. Any algorithm listed in the [DNSKEY-IANA] and 98 [DS-IANA] registries that are not mentioned in this document MAY be 99 implemented. For clarification and consistency, an algorithm will be 100 specified as MAY in this document only when it has been downgraded 101 from a MUST or a RECOMMENDED to a MAY. 103 That paragraph is now replaced with the following: 105 This document provides recommendations with respect to mandatory-to- 106 implement algorithms, algorithms so weak that they cannot be 107 recommended, and algorithms that are defined in RFCs that are not on 108 standards track. Any algorithm listed in the [DNSKEY-IANA] and [DS- 109 IANA] registries that are not mentioned in this document MAY be 110 implemented. For clarification and consistency, an algorithm will be 111 specified as MAY in this document only when it has been downgraded 112 from a MUST or a RECOMMENDED to a MAY. 114 4. IANA Considerations 116 In the "Domain Name System Security (DNSSEC) NextSECure3 (NSEC3) 117 Parameters" registry, the registration procedure for "DNSSEC NSEC3 118 Flags", "DNSSEC NSEC3 Hash Algorithms", and "DNSSEC NSEC3PARAM Flags" 119 are changed from "Standards Action" to "RFC Required". 121 In the "Delegation Signer (DS) Resource Record (RR) Type Digest 122 Algorithms" registry, the registration procedure for "Digest 123 Algorithms" is changed from "Standards Action" to "RFC Required". 125 5. Security Considerations 127 Changing the requirements for getting security algorithms added to 128 IANA registries as described in this document will make it easier to 129 get good algorithms added to the registries, and will make it easier 130 to get bad algorithms added to the registries. It is impossible to 131 weigh the security impact of those two changes. 133 6. References 135 6.1. Normative References 137 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 138 Rose, "DNS Security Introduction and Requirements", 139 RFC 4033, DOI 10.17487/RFC4033, March 2005, 140 . 142 [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. 143 Rose, "Resource Records for the DNS Security Extensions", 144 RFC 4034, DOI 10.17487/RFC4034, March 2005, 145 . 147 [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. 148 Rose, "Protocol Modifications for the DNS Security 149 Extensions", RFC 4035, DOI 10.17487/RFC4035, March 2005, 150 . 152 [RFC5155] Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS 153 Security (DNSSEC) Hashed Authenticated Denial of 154 Existence", RFC 5155, DOI 10.17487/RFC5155, March 2008, 155 . 157 [RFC6014] Hoffman, P., "Cryptographic Algorithm Identifier 158 Allocation for DNSSEC", RFC 6014, DOI 10.17487/RFC6014, 159 November 2010, . 161 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 162 Writing an IANA Considerations Section in RFCs", BCP 26, 163 RFC 8126, DOI 10.17487/RFC8126, June 2017, 164 . 166 [RFC8624] Wouters, P. and O. Sury, "Algorithm Implementation 167 Requirements and Usage Guidance for DNSSEC", RFC 8624, 168 DOI 10.17487/RFC8624, June 2019, 169 . 171 6.2. Informative References 173 [RFC3658] Gudmundsson, O., "Delegation Signer (DS) Resource Record 174 (RR)", RFC 3658, DOI 10.17487/RFC3658, December 2003, 175 . 177 Author's Address 179 Paul Hoffman 180 ICANN 182 Email: paul.hoffman@icann.org