Clarification to Processing Key Usage Values During Certificate Revocation List (CRL) Validation
RFC 10007
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-07-06
|
(System) | Changed publication time to 2026-06-30T17:50:09+00:00 from 2026-06-30T17:50:09.411418+00:00 |
|
2026-07-06
|
(System) | Changed author "T. Okubo": changed order from "2" to "3" |
|
2026-07-06
|
(System) | Changed author "T. Ito": changed order from "1" to "2" |
|
2026-07-06
|
(System) | Changed author "C. Bonnell": changed order from "0" to "1" |
|
2026-07-06
|
(System) | Changed metadata: changed abstract to 'RFC 5280 defines the profile of X.509 certificates and Certificate Revocation Lists (CRLs) for use in the Internet. Section 4.2.1.3 … Changed metadata: changed abstract to 'RFC 5280 defines the profile of X.509 certificates and Certificate Revocation Lists (CRLs) for use in the Internet. Section 4.2.1.3 of RFC 5280 requires CRL issuer certificates to contain the keyUsage extension with the cRLSign bit asserted. However, the CRL validation algorithm specified in Section 6.3 of RFC 5280 does not explicitly include a corresponding check for the presence of the keyUsage certificate extension. This document updates RFC 5280 to require that check.' from 'RFC 5280 defines the profile of X.509 certificates and Certificate Revocation Lists (CRLs) for use in the Internet. Section 4.2.1.3 of RFC 5280 requires CRL issuer certificates to contain the' |
|
2026-07-06
|
(System) | Metadata update from RFC Editor |
|
2026-06-30
|
(System) | RFC published |