| < draft-hoffman-dnssec-iana-cons-00.txt | draft-hoffman-dnssec-iana-cons-01.txt > | |||
|---|---|---|---|---|
| Network Working Group P. Hoffman | Network Working Group P. Hoffman | |||
| Internet-Draft ICANN | Internet-Draft ICANN | |||
| Updates: RFC 3658, RFC 5155, RFC 6014 June 21, 2020 | Updates: RFC 3658, RFC 5155, RFC 6014 July 06, 2020 | |||
| (if approved) | (if approved) | |||
| Intended status: Standards Track | Intended status: Standards Track | |||
| Expires: December 23, 2020 | Expires: January 7, 2021 | |||
| Revised IANA Considerations for DNSSEC | Revised IANA Considerations for DNSSEC | |||
| draft-hoffman-dnssec-iana-cons-00 | draft-hoffman-dnssec-iana-cons-01 | |||
| Abstract | Abstract | |||
| This document changes the review requirements needed to get DNSSEC | This document changes the review requirements needed to get some | |||
| algorithms and resource records added to IANA registries. It updates | DNSSEC algorithms and resource records added to IANA registries. It | |||
| RFC 6014, which did not include hash algorithms for DS records or | updates RFC 6014 to include hash algorithms for DS records and NSEC3 | |||
| NSEC3 parameters in the change to all registries requiring RFCs, not | parameters. | |||
| standards, for inclusion in the IANA registries. | ||||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on December 23, 2020. | This Internet-Draft will expire on January 7, 2021. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2020 IETF Trust and the persons identified as the | Copyright (c) 2020 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 2, line 19 ¶ | skipping to change at page 2, line 19 ¶ | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 | 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 | 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 | |||
| 4. Normative References . . . . . . . . . . . . . . . . . . . . 3 | 4. Normative References . . . . . . . . . . . . . . . . . . . . 3 | |||
| Appendix A. Other Options for Requirements Level . . . . . . . . 3 | Appendix A. Other Options for Requirements Level . . . . . . . . 3 | |||
| Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 | Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 1. Introduction | 1. Introduction | |||
| DNSSEC is primarily described in [RFC4033], [RFC4034], and [RFC4035]. | DNSSEC is primarily described in [RFC4033], [RFC4034], and [RFC4035]. | |||
| DNSSEC in common uses two resource records beyond those defined in | DNSSEC commonly uses two resource records beyond those defined in RFC | |||
| RFC 4034, namely DS [RFC3658] and NSEC3 [RFC5155]. | 4034: DS [RFC3658] and NSEC3 [RFC5155]. | |||
| [RFC8126] describes the requirements for listing in the myriad IANA | [RFC8126] describes the requirements for listing in the myriad IANA | |||
| registries. [RFC6014] updated the requirements for how DNSSEC | registries. | |||
| cryptographic algorithm identifiers in the IANA registries are | ||||
| allocated, reducing the requirements from being "Standards Action" to | ||||
| "RFC Required". | ||||
| The IANA registry requirements for hash algorithms for DS records and | [RFC6014] updated the requirements for how DNSSEC cryptographic | |||
| for the hash algorithms used in NSEC3 are still "Standards Action". | algorithm identifiers in the IANA registries are allocated, reducing | |||
| This document updates RFC 6014 to bring the requirements for DS | the requirements from being "Standards Action" to "RFC Required". | |||
| records and NSEC3 hash algorithms in line with the rest of the DNSSEC | However, the IANA registry requirements for hash algorithms for DS | |||
| cryptographic algorithms, . | records and for the hash algorithms used in NSEC3 are still | |||
| "Standards Action". This document updates RFC 6014 to bring the | ||||
| requirements for DS records and NSEC3 hash algorithms in line with | ||||
| the rest of the DNSSEC cryptographic algorithms. | ||||
| 2. IANA Considerations | 2. IANA Considerations | |||
| In the "Domain Name System Security (DNSSEC) NextSECure3 (NSEC3) | In the "Domain Name System Security (DNSSEC) NextSECure3 (NSEC3) | |||
| Parameters" registry, the registration procedure for "DNSSEC NSEC3 | Parameters" registry, the registration procedure for "DNSSEC NSEC3 | |||
| Flags", "DNSSEC NSEC3 Hash Algorithms", and "DNSSEC NSEC3PARAM Flags" | Flags", "DNSSEC NSEC3 Hash Algorithms", and "DNSSEC NSEC3PARAM Flags" | |||
| are changed from "Standards Action" to "RFC Required". | are changed from "Standards Action" to "RFC Required". | |||
| In the "Delegation Signer (DS) Resource Record (RR) Type Digest | In the "Delegation Signer (DS) Resource Record (RR) Type Digest | |||
| Algorithms" registry, the registration procedure for "Digest | Algorithms" registry, the registration procedure for "Digest | |||
| End of changes. 8 change blocks. | ||||
| 20 lines changed or deleted | 19 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||