[dnsext] RFC 6014 on Cryptographic Algorithm Identifier Allocation for DNSSEC
rfc-editor@rfc-editor.org Mon, 22 November 2010 18:25 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 933033A6AE5; Mon, 22 Nov 2010 10:25:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.065
X-Spam-Level:
X-Spam-Status: No, score=-102.065 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdDGSUh2hA6c; Mon, 22 Nov 2010 10:25:09 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id BDCB53A687F; Mon, 22 Nov 2010 10:25:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 163EFE06A6; Mon, 22 Nov 2010 10:26:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20101122182606.163EFE06A6@rfc-editor.org>
Date: Mon, 22 Nov 2010 10:26:06 -0800
Cc: dnsext@ietf.org, rfc-editor@rfc-editor.org
Subject: [dnsext] RFC 6014 on Cryptographic Algorithm Identifier Allocation for DNSSEC
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 22 Nov 2010 18:25:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6014
Title: Cryptographic Algorithm Identifier Allocation for
DNSSEC
Author: P. Hoffman
Status: Standards Track
Stream: IETF
Date: November 2010
Mailbox: paul.hoffman@vpnc.org
Pages: 6
Characters: 11182
Updates: RFC4033, RFC4034, RFC4035
I-D Tag: draft-ietf-dnsext-dnssec-alg-allocation-03.txt
URL: http://www.rfc-editor.org/rfc/rfc6014.txt
This document specifies how DNSSEC cryptographic algorithm
identifiers in the IANA registries are allocated. It changes the
requirement from "standard required" to "RFC Required". It does not
change the list of algorithms that are recommended or required for
DNSSEC implementations. [STANDARDS-TRACK]
This document is a product of the DNS Extensions Working Group of the IETF.
This is now a Proposed Standard Protocol.
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