CA/Incident Dashboard: Difference between revisions

Updated the text explaining the [delayed-revocation-ca] or [delayed-revocation-leaf] whiteboard tags
(Separate out delayed revocation incidents and move to a lower table.)
(Updated the text explaining the [delayed-revocation-ca] or [delayed-revocation-leaf] whiteboard tags)
Line 25: Line 25:


== Revocation Delays ==
== Revocation Delays ==
A Revocation Bug is created whenever a CA fails to abide by the Baseline Requirements' requirement to revoke certificates in a timely fashion. As discussed in [[CA/Responding_To_An_Incident#Revocation]], Mozilla recognizes that there may be *exceptional* situations that cause a CA to not abide by the Baseline Requirements, which should be accompanied by an Incident Report.
The compliance bug's whiteboard is appended to add [delayed-revocation-ca] or [delayed-revocation-leaf] whenever a CA fails to abide by the Baseline Requirements' requirement to revoke certificates in a timely fashion. As discussed in [[CA/Responding_To_An_Incident#Revocation]], Mozilla recognizes that there may be *exceptional* situations that cause a CA to not abide by the Baseline Requirements, which should be accompanied by an Incident Report.


Such bugs should be reported as CA compliance issues, and will be categorized appropriately during triage.
Such bugs should be reported as CA compliance issues, and will be categorized appropriately during triage.
Confirmed users, Administrators
5,526

edits