RFC 9157: Revised IANA Considerations for DNSSEC
In plain English — editorial summary, not part of the RFC
This document changes the review requirements needed to get DNSSEC algorithms and resource records added to IANA registries. It updates RFC 6014 to include hash algorithms for Delegation Signer (DS) records and NextSECure version 3 (NSEC3) parameters (for Hashed Authenticated Denial of Existence). It also updates RFCs 5155 and 6014, which have requirements for DNSSEC algorithms, and updates RFC 8624 to clarify the implementation recommendation related to the algorithms described in RFCs that are not on the standards track. The rationale for these changes is to bring the requirements for DS records and hash algorithms used in NSEC3 in line with the requirements for all other DNSSEC algorithms.
Document record
- Document ID
- RFC9157
- Published
- December 2021
- Authors
- P. Hoffman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 5
- Also known as
- —
- Updated by:
- RFC 9904
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9156DNS Query Name Minimisation to Improve PrivacyCurrent
November 2021
- RFC 9160Export of MPLS Segment Routing Label Type Information in IP Flow Information Export (IPFIX)Current
December 2021
- RFC 9154Extensible Provisioning Protocol (EPP) Secure Authorization Information for TransferCurrent
December 2021
- RFC 9167Registry Maintenance Notification for the Extensible Provisioning Protocol (EPP)Current
December 2021
- RFC 9144Comparison of Network Management Datastore Architecture (NMDA) DatastoresCurrent
December 2021
- RFC 9179A YANG Grouping for Geographic LocationsCurrent
February 2022
- RFC 9181A Common YANG Data Model for Layer 2 and Layer 3 VPNsCurrent
February 2022
- RFC 9182A YANG Network Data Model for Layer 3 VPNsCurrent
February 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?