CA:Schedule
Schedule for CA evaluations
Note that this schedule is tentative and may change without warning based on unforeseen circumstances. Nothing in this schedule shall be construed as a commitment by the Mozilla Foundation or the Mozilla project in general.
General timeline
Our process for evaluating CA requests is as follows:
- CAs will be added into the queue for public discussion after they have completed the Information Gathering and Verification phase as described in CA:How_to_apply.
- Prior to entering public discussion we may need to gather further information or an updated audit from the CA; if for some reason we cannot obtain the needed information then the next CA in the queue will be considered for public discussion.
- Once a CA enters the public discussion period a representative of the CA must promptly respond in the discussion to any questions or concerns that are raised. If a CA delays their response for more than one week, then their discussion may be closed.
- During the course of the discussion, we will make a decision as to whether to approve the request.
- If the discussion results in moving forward with approval, then a representative of Mozilla will summarize the request in the bug, and indicate the plan to approve the request. After about one week, if no further questions or concerns are raised, then the representative of Mozilla may approve the request. Once a request is approved then a representative of Mozilla will file bug(s) against the appropriate developer(s) to have the necessary changes made to NSS (for CA root inclusion) or PSM (for EV-enabling a CA) or both.
- A discussion may be put on hold, pending a CA action item, such that the discussion may continue as soon as the CA has provided the requested information.
- If a request is not approved due to outstanding issues that need to be addressed (e.g., a need for further information, or concerns about CA practices) then the request will wither be closed, or will be added to the list of CAs responding to the first discussion. A second round of public discussion may be needed after the issues have been resolved.
Once bugs are filed against NSS and/or PSM the schedule is set first by the NSS/PSM developer(s) (for making the technical changes) and then by the product teams for Firefox and other products (to include the new changes in a release of Firefox, etc.) Root certificate changes to NSS/PSM are usually grouped and done as a batch when there is either a large enough set of changes or about every 3 months. When the developer makes the changes, a test build will be provided and the bug will be updated to request that you test it. After the NSS/PSM changes are committed to an NSS release, then a future version of Firefox will include the updated version of NSS/PSM.
Queue for Public Discussion
The following queue indicates the order in which requests will enter public discussion for root inclusion request from CAs who do not currently have a root certificate included in NSS. In general, only one or two of these requests may be in discussion at any given point. The amount of time that each discussion takes varies dramatically depending on the number of reviewers contributing to the discussion, and the types of concerns that are raised. For each discussion, there must be input from at least two people who have reviewed and commented on the request. To be added to this queue, a request must first achieve the "Information Confirmed Complete" status.
| CA Company Name | Bug ID | Geographic focus | Audit Date yyyy.mm.dd | Status | Notes |
|---|---|---|---|---|---|
| GDCA | bug 1128392 | China | 2016.04.15 | Started Discussion on August 3 | EV |
| OATI | bug 848766 | US | 2015.01.02 | certlint errors - bug 848766#c33 | |
| MULTICERT | bug 1040072 | Portugal | 2016.04.01 | Ready for Discussion | |
| TrustCor | bug 1231853 | Canada, Global | 2015.12.01 | Ready for Discussion | |
| Government of Tunisia | bug 1233645 | Tunisia | 2015.11.30 | Ready for Discussion | |
| SSL.com | bug 1277336 | USA, Global | Re-test when test tool is available | ||
| - | - | - | - | - |
Requests from Already Included CAs that are in or Ready for Discussion
These requests are from CAs that already have roots included in NSS. The requests may be discussed in parallel; the goal is to start each discussion as soon as the information is ready. In general, these requests will remain in discussion for 2 weeks unless further discussion is warranted. To be added to this queue, a request must first achieve the "Information Confirmed Complete" status.
| CA Company Name | Bug ID | Geographic focus | Audit Date yyyy.mm.dd | Status | Notes |
|---|---|---|---|---|---|
| Taiwan GRCA | bug 1065896 | Taiwan | 2016.06.29 | Started Discussion on September 16 | constrain to *.tw |
| EDICOM | bug 1239329 | European Union | 2015.11.03 | Need updated audit statement | |
| D-Trust | bug 1166723 | Germany, Europe, Global | 2016.11.21 | Started Discussion on December 21 | email trust bit only |
| Kamu SM - Government of Turkey | bug 1262809 | Turkey | 2015.12.28 | Ready for discussion | |
| Dhimyotis / Certigna | bug 1265683 | France, Europe | 2016.02.15 | Ready for discussion | |
| Visa | bug 636557 | Global | 2016.09.16 | Ready for discussion | |
| Camerfirma | bug 986854 | Spain | 2016.06.17 | Ready for discussion | |
| - | - | - | - | - | |
| - | - | - | - | - |
CA Dashboard
All other status relating to CA inclusion/update requests may be found here: https://wiki.mozilla.org/CA/Dashboard
Roots Being Removed
Upcoming Root Cert Removals:
Certs that have been Removed:
Included CAs
Spreadsheet of all included root certificates: