Cryptographic Algorithm Identifier Allocation for DNSSEC
RFC 6014, “Cryptographic Algorithm Identifier Allocation for DNSSEC”, is a Proposed Standard document published in November 2010 by P. Hoffman. It updates RFC 4033, RFC 4034, RFC 4035. It has since been updated by RFC 9157. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6014 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6015 RTP Payload Format for 1-D Interleaved Parity Forward Error Correction
- RFC 6012 Datagram Transport Layer Security Transport Mapping for Syslog
- RFC 6016 Support for the Resource Reservation Protocol in Layer 3 VPNs
- RFC 6011 Session Initiation Protocol User Agent Configuration
- RFC 6017 Electronic Data Interchange - Internet Integration Features Header Field
- RFC 6010 Cryptographic Message Syntax Content Constraints Extension
- RFC 6018 IPv4 and IPv6 Greynets
- RFC 6009 Sieve Email Filtering: Delivery Status Notifications and Deliver-By Extensions