Lightweight Certificate Validation Protocol (LCVP)
draft-pinkas-pkix-lcvp-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Denis Pinkas | ||
| Last updated | 2007-05-04 | ||
| 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
LCVP allows a client to delegate certificate path validation to a trusted server. The path validation (e.g. making sure that none of the certificates in the path are revoked) is performed according to a set of rules called a validation policy. It allows simplification of client implementations and only uses of a set of predefined validation policies. This document defines a protocol that can be used to: (1) validate one certificate according to one validation policy, (2) query the validation policies supported by an LCVP server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)