Storing application public keys in the DNS
draft-schlyter-appkey-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jacob Schlyter | ||
| Last updated | 2002-02-13 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies a new DNS RR type for applications to store public keys in. Experience with DNSSEC has indicated that mixing DNS keys and application keys is a bad idea in many regards. The new RR expands certain fields based on experience from early DNSSEC deployment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)