RFC 7929: DNS-Based Authentication of Named Entities (DANE) Bindings for OpenPGP
In plain English — editorial summary, not part of the RFC
OpenPGP is a message format for email (and file) encryption that lacks a standardized lookup mechanism to securely obtain OpenPGP public keys. DNS-Based Authentication of Named Entities (DANE) is a method for publishing public keys in DNS. This document specifies a DANE method for publishing and locating OpenPGP public keys in DNS for a specific email address using a new OPENPGPKEY DNS resource record. Security is provided via Secure DNS, however the OPENPGPKEY record is not a replacement for verification of authenticity via the "web of trust" or manual verification. The OPENPGPKEY record can be used to encrypt an email that would otherwise have to be sent unencrypted.
Document record
- Document ID
- RFC7929
- Published
- August 2016
- Authors
- P. Wouters
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7619The NULL Authentication Method in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
August 2015
- RFC 8164Opportunistic Security for HTTP/2Current
May 2017
- RFC 8643An Opportunistic Approach for Secure Real-time Transport Protocol (OSRTP)Current
August 2019
- RFC 7930Larger Packets for RADIUS over TCPCurrent
August 2016
- RFC 7925Transport Layer Security (TLS) / Datagram Transport Layer Security (DTLS) Profiles for the Internet of ThingsCurrent
July 2016
- RFC 7924Transport Layer Security (TLS) Cached Information ExtensionCurrent
July 2016
- RFC 7919Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)Current
August 2016
- RFC 7918Transport Layer Security (TLS) False StartCurrent
August 2016
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?