Conforming CRL validation for relying parties
draft-pinkas-pkix-conf-crl-validation-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Denis Pinkas | ||
| Last updated | 2005-07-19 | ||
| 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 text currently present in section 6.3 from RFC 3280 is dedicated to CRL validation. This text needs to be more detailed to explain exactly how it can made be sure that a CRL is issued by the right entity. In addition, a text dedicated to the characteristics that conforming applications MUST support needs to be provided: the current text covers the most complex case and is too complicated to be easily simplified. Text is proposed to be included in 3280bis and to partially replace section 6.3 .
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)