[dnsext] RFC 6944 on Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation Status
rfc-editor@rfc-editor.org Wed, 01 May 2013 05:33 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF8A221F8693; Tue, 30 Apr 2013 22:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.175
X-Spam-Level:
X-Spam-Status: No, score=-102.175 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhU39-fEpkUz; Tue, 30 Apr 2013 22:33:12 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7D621F84E3; Tue, 30 Apr 2013 22:33:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F3427B1E014; Tue, 30 Apr 2013 22:32:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130501053241.F3427B1E014@rfc-editor.org>
Date: Tue, 30 Apr 2013 22:32:41 -0700
Cc: dnsext@ietf.org, rfc-editor@rfc-editor.org
Subject: [dnsext] RFC 6944 on Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation Status
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 05:33:13 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6944
Title: Applicability Statement: DNS Security (DNSSEC)
DNSKEY Algorithm Implementation Status
Author: S. Rose
Status: Standards Track
Stream: IETF
Date: April 2013
Mailbox: scottr.nist@gmail.com
Pages: 7
Characters: 13876
Updates: RFC 2536, RFC 2539, RFC 3110, RFC 4034,
RFC 4398, RFC 5155, RFC 5702, RFC 5933
I-D Tag: draft-ietf-dnsext-dnssec-algo-imp-status-04.txt
URL: http://www.rfc-editor.org/rfc/rfc6944.txt
The DNS Security Extensions (DNSSEC) requires the use of
cryptographic algorithm suites for generating digital signatures over
DNS data. There is currently an IANA registry for these algorithms,
but there is no record of the recommended implementation status of
each algorithm. This document provides an applicability statement on
algorithm implementation status for DNSSEC component software. This
document lists each algorithm's status based on the current
reference. In the case that an algorithm is specified without an
implementation status, this document assigns one. This document
updates RFCs 2536, 2539, 3110, 4034, 4398, 5155, 5702, and 5933.
This document is a product of the DNS Extensions Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC