Using DANE to Associate OpenPGP public keys with email addresses
draft-ietf-dane-openpgpkey-11
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Active Internet-Draft (dane WG) | |
| Last updated | 2016-04-29 | ||
| Stream | IETF | ||
| Intended RFC status | Experimental | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Ólafur Guðmundsson | ||
| Shepherd write-up | Show (last changed 2016-04-21) | ||
| IESG | IESG state | IESG Evaluation::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Has enough positions to pass. |
||
| Responsible AD | Stephen Farrell | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | None | ||
Network Working Group P. Wouters
Internet-Draft Red Hat
Intended status: Experimental April 29, 2016
Expires: October 31, 2016
Using DANE to Associate OpenPGP public keys with email addresses
draft-ietf-dane-openpgpkey-11
Abstract
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 31, 2016.
Copyright Notice
Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of
Wouters Expires October 31, 2016 [Page 1]
Internet-Draft DANE for OpenPGP public keys April 2016
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Experiment goal . . . . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. The OPENPGPKEY Resource Record . . . . . . . . . . . . . . . 4
2.1. The OPENPGPKEY RDATA component . . . . . . . . . . . . . 5
2.1.1. The OPENPGPKEY RDATA content . . . . . . . . . . . . 5
2.1.2. Reducing the Transferable Public Key size . . . . . . 6
2.2. The OPENPGPKEY RDATA wire format . . . . . . . . . . . . 6
2.3. The OPENPGPKEY RDATA presentation format . . . . . . . . 7
3. Location of the OPENPGPKEY record . . . . . . . . . . . . . . 7
4. Email address variants and internationalization
considerations . . . . . . . . . . . . . . . . . . . . . . . 8
5. Application use of OPENPGPKEY . . . . . . . . . . . . . . . . 8
5.1. Obtaining an OpenPGP key for a specific email address . . 9
5.2. Confirming that an OpenPGP key is current . . . . . . . . 9
5.3. Public Key UIDs and query names . . . . . . . . . . . . . 9
6. OpenPGP Key size and DNS . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7.1. MTA behaviour . . . . . . . . . . . . . . . . . . . . . . 11
7.2. MUA behaviour . . . . . . . . . . . . . . . . . . . . . . 12
7.3. Response size . . . . . . . . . . . . . . . . . . . . . . 12
7.4. Email address information leak . . . . . . . . . . . . . 13
7.5. Storage of OPENPGPKEY data . . . . . . . . . . . . . . . 13
7.6. Security of OpenPGP versus DNSSEC . . . . . . . . . . . . 13
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 14
8.1. The GNU Privacy Guard (GNUpg) . . . . . . . . . . . . . . 14
8.2. hash-slinger . . . . . . . . . . . . . . . . . . . . . . 15
8.3. openpgpkey-milter . . . . . . . . . . . . . . . . . . . . 15
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
9.1. OPENPGPKEY RRtype . . . . . . . . . . . . . . . . . . . . 16
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
Show full document text