Internet Public Key Infrastructure Real Time Certificate Status Protocol - RCSP
draft-malpani-rcsp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Carlisle Adams , Ambarish N. Malpani , Rich Ankney , Slava Galperin | ||
| Last updated | 1998-03-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
The protocol conventions described in this document satisfy some of the operational requirements of the Internet Public Key Infrastructure (PKI). This document specifies a protocol useful in determining the current status of a digital certificate without the use of CRLs. Additional mechanisms addressing PKIX operational requirements are specified in separate documents. Section 2 provides an overview of the protocol. Section 3 goes through the functional requirements, while section 4 provides the details of the protocol. In section 5 we cover security issues with the protocol. Appendix A demonstrates RCSP over HTTP. Please send comments on this document to the ietf-pkix@tandem.com mail list.
Authors
Dr. Carlisle Adams
Ambarish N. Malpani
Rich Ankney
Slava Galperin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)