Notes on Application Key Distribution
draft-josefsson-siked-framework-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Simon Josefsson , Wesley Griffin | ||
| Last updated | 2002-02-28 | ||
| 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
The debate over whether to store cryptographic keys used by applications in the Domain Name System or not has been going on for some time. There are arguments for and against [6]. This document tries to take a step further and provides some initial terminology, problem statement and use cases for storing application keys in DNS, in order to enable more substantiated input to the discussion. We mention some proposed solutions so far. We also give some requirements on a solution (be it DNS based or not) that would satisfy the use cases.
Authors
Simon Josefsson
Wesley Griffin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)