Skip to content

Commit

Permalink
Add effective date. Clarify when a certificate is considered revoked
Browse files Browse the repository at this point in the history
  • Loading branch information
XolphinMartijn authored Nov 29, 2024
1 parent 9b28eda commit aa73544
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions docs/BR.md
Original file line number Diff line number Diff line change
Expand Up @@ -1424,6 +1424,8 @@ No stipulation.

### 4.9.5 Time within which CA must process the revocation request

Prior to 2025-03-15, for Section 4.9.5 of these Requirements, the CA SHALL adhere to these Requirements or Version 2.1.1 of the Baseline Requirements for TLS Server Certificates. Effective 2025-03-12, the CA SHALL adhere to these Requirements.

Within twenty-four (24) hours after receiving a Certificate Problem Report, the CA SHALL investigate the facts and circumstances related to the report and determine if it's "actionanable."

A Certificate Problem Report is considered actionable if it includes:
Expand Down Expand Up @@ -1547,6 +1549,12 @@ Not applicable.

Not applicable.

### 4.9.17 Authoritative certificate status

Effective 2025-03-15, for a certificate to be considered revoked:
1. If the CA publishes a CRL, the CRL containing the certificate serial number MUST have been published to the Repository and be available for consumption for Relying Parties; and
2. If the certificate contains a HTTP URL of the Issuing CA's OCSP responder, at least one (1) OCSP response containing a `certStatus` value of `revoked` MUST have been published to the Repository and be available for consumption for Relying Parties;

## 4.10 Certificate status services

### 4.10.1 Operational characteristics
Expand Down

0 comments on commit aa73544

Please sign in to comment.