RFC 5702: Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC
In plain English — editorial summary, not part of the RFC
This document describes how to produce RSA/SHA-256 and RSA/SHA-512 DNSKEY and RRSIG resource records for use in the Domain Name System Security Extensions (RFC 4033, RFC 4034, and RFC 4035). [STANDARDS TRACK]
Document record
- Document ID
- RFC5702
- Published
- October 2009
- Authors
- J. Jansen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
- Updated by:
- RFC 6944
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5754Using SHA2 Algorithms with Cryptographic Message SyntaxCurrent
January 2010
- RFC 4634US Secure Hash Algorithms (SHA and HMAC-SHA)Obsoleted
August 2006
- RFC 6014Cryptographic Algorithm Identifier Allocation for DNSSECUpdated
November 2010
- RFC 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
- RFC 4471Derivation of DNS Name Predecessor and SuccessorCurrent
September 2006
- RFC 6975Signaling Cryptographic Algorithm Understanding in DNS Security Extensions (DNSSEC)Current
July 2013
- RFC 4035Protocol Modifications for the DNS Security ExtensionsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?