[DNSOP] I-D Action: draft-ietf-dnsop-rfc8624-bis-12.txt
internet-drafts@ietf.org Tue, 03 June 2025 18:42 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from [10.244.8.226] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 26F6E30549C4; Tue, 3 Jun 2025 11:42:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.40.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174897617301.2747301.15485074301750501773@dt-datatracker-59b84fc74f-84jsl>
Date: Tue, 03 Jun 2025 11:42:53 -0700
Message-ID-Hash: 3XXDX26IJ3MBXQH6O4GVC4HDCT67XRDK
X-Message-ID-Hash: 3XXDX26IJ3MBXQH6O4GVC4HDCT67XRDK
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dnsop@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-rfc8624-bis-12.txt
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/cfSdT1P9ifL8TBtHVXGUUky2tKw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>
Internet-Draft draft-ietf-dnsop-rfc8624-bis-12.txt is now available. It is a
work item of the Domain Name System Operations (DNSOP) WG of the IETF.
Title: DNSSEC Cryptographic Algorithm Recommendation Update Process
Authors: Wes Hardaker
Warren Kumari
Name: draft-ietf-dnsop-rfc8624-bis-12.txt
Pages: 15
Dates: 2025-06-03
Abstract:
The DNSSEC protocol makes use of various cryptographic algorithms to
provide authentication of DNS data and proof of non-existence. To
ensure interoperability between DNS resolvers and DNS authoritative
servers, it is necessary to specify both a set of algorithm
implementation requirements and usage guidelines to ensure that there
is at least one algorithm that all implementations support. This
document replaces and obsoletes RFC8624 and moves the canonical
source of algorithm implementation requirements and usage guidance
for DNSSEC from RFC8624 to an IANA registry. This is done both to
allow the list of requirements to be more easily updated, and to
allow the list to be more easily referenced. Future extensions to
this registry can be made under new, incremental update RFCs. This
document also incorporates the revised IANA DNSSEC considerations
from RFC9157.
The document does not change the status (MUST, MAY, RECOMMENDED,
etc.) of the algorithms listed in RFC8624; that is the work of future
documents.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc8624-bis/
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-rfc8624-bis-12
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-rfc8624-bis-12
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
- [DNSOP] I-D Action: draft-ietf-dnsop-rfc8624-bis-… internet-drafts