Adding Multiple TLS Certificate Status Extension requests
draft-pettersen-tls-ext-multiple-ocsp-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yngve Pettersen | ||
| Last updated | 2012-09-07 (Latest revision 2012-03-06) | ||
| 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 introduces a replacement of the TLS Certificate Status Extension to allow clients to specify and support multiple certificate status methods. Also being introduced is a new OCSP- based method that servers can use to provide status information not just about the server's own certificate, but also the status of intermediate certificates in the chain.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)