Storing Certificates in the Domain Name System (DNS)
draft-josefsson-rfc2538bis-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Simon Josefsson | ||
| Last updated | 2005-01-03 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-josefsson-rfc2538bis-01.txt
https://www.ietf.org/archive/id/draft-josefsson-rfc2538bis-01.txt
Abstract
Cryptographic public key are frequently published and their authenticity demonstrated by certificates. A CERT resource record (RR) is defined so that such certificates and related certificate revocation lists can be stored in the Domain Name System (DNS). More information on this document, including rfcdiff output, may be found at <http://josefsson.org/rfc2538bis/>.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)