CA/Root Store Policy Archive: Difference between revisions

Revision as of 12:11, 28 February 2017

The general process that will be followed to update the Mozilla CA Certificate Policy is as follows. Issues and potential changes will be tracked in the policy issue tracker.

A Mozilla representative will bring forward an item for discussion in the mozilla.dev.security.policy forum.
There will be a discussion of how, if at all, to modify the policy for the item.
At some point, which may be at the start, a Mozilla representative will draft proposed text.
A Mozilla representative will summarize a consensus that has been reached, and/or state the official position of Mozilla in both the discussion in mozilla.dev.security.policy and in the policy issue tracker.
The draft policy in Github will be updated, if required.
The issue will be closed.

At intervals, a new policy version will be released based on the current draft, along with a timeline for compliance.

A Mozilla representative will post notice in the mozilla.dev.security.policy, mozilla.dev.security, and mozilla.governance forums.
A Mozilla representative will send email communication to CAs, indicate the compliance schedule.

 Common CCADB Policy, 
 Mozilla CCADB Policy

Publication date: February 28, 2017
Compliance date: February 28, 2017 (except "CP/CPS in English", which is June 1, 2017)
List of changes and diff

@@ Line 16: / Line 16: @@
 === Versions of the Policy ===
+====2.4====
+* [https://github.com/mozilla/pkipolicy/blob/2.4/rootstore/policy.md Policy document],
+  [https://github.com/mozilla/pkipolicy/blob/2.4/ccadb/policy.md Common CCADB Policy],
+  [https://github.com/mozilla/pkipolicy/blob/2.4/ccadb/mozilla.md Mozilla CCADB Policy]
+* Publication date: February 28, 2017
+* Compliance date: February 28, 2017 (except "CP/CPS in English", which is June 1, 2017)
+* [https://github.com/mozilla/pkipolicy/compare/2.3...2.4 List of changes and diff]
 ====2.3====