OCSP over DNS (ODIN)
draft-pala-odin-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Massimiliano Pala | ||
| Last updated | 2016-10-10 (Latest revision 2016-04-08) | ||
| RFC stream | (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
With the increase number of protocols and applications that rely on digital certificates to authenticate either the communication channel (TLS) or the data itself (PKIX), the need for providing an efficient revocation system is paramount. Although the Online Certificate Status Protocol (OCSP) allows for efficient lookup of the revocation status of a certificate, the distribution of this information via HTTP or HTTPS is not particularly efficient for high volume websites without incurring in high distribution costs (e.g., CDN). This draft describes how to provide pre-signed OCSP responses via the DNS system in order to leverage its distributed nature and, therefore lowering operational costs for Certification Authorities.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)