Browse Prior Art Database

Cryptographic Algorithm Identifier Allocation for DNSSEC (RFC6014) Disclosure Number: IPCOM000201777D
Original Publication Date: 2010-Nov-01
Included in the Prior Art Database: 2010-Nov-23
Document File: 12 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Hoffman: AUTHOR


[RFC2535] specifies that the IANA registry for DNS Security Algorithm Numbers be updated by IETF Standards Action only, with the exception of two values -- 253 and 254. In essence, this means that for an algorithm to get its own entry in the registry, the algorithm must be defined in an RFC on the Standards Track as defined in [RFC2026]. The requirement from RFC 2535 is repeated in [RFC3755] and the combination of [RFC4033], [RFC4034], and [RFC4035].

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 25% of the total text.

Internet Engineering Task Force (IETF)                        P. Hoffman Request for Comments: 6014                                VPN Consortium Updates: 4033, 4034, 4035                                  November 2010 Category: Standards Track ISSN: 2070-1721

         Cryptographic Algorithm Identifier Allocation for DNSSEC


   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

Hoffman                      Standards Track                    [Page 1]
 RFC 6014                 DNSSEC Alg. Allocation            November 2010

 Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF    Contributions published or made publicly available before November    10, 2008.  The person(s) controlling the copyright in some of this    material may not have granted the IETF Trust the right to allow    modifications of such material outside the IETF Standards Process.    Without obtaining an adequate license from the person(s) controlling    the copyright in such materials, this document may not be modified    outside the IETF Standards Process, and derivative works of it may    not be created outside the IETF Standards Process, except to format    it for publication as an RFC or to transl...