All,

As of this week I am using SalesForce to process root inclusion/change requests, instead of the Word document I previously used. This means that the output will be slightly different than the CAInformation.pdf document.

For comparison, here's the new output for the Entrust request that is currently under discussion:
https://bugzilla.mozilla.org/attachment.cgi?id=8532105

The old format CA Information Document is here:
https://bugzilla.mozilla.org/attachment.cgi?id=8513832


In the new form, the CA-level information is listed first, then the information for each root certificate is listed one at a time.

In SalesForce, I have "Cases" and "Root Cases". CAs often open one Bugzilla Bug requesting inclusion of more than one root certificates. Sometimes only a subset of those root certificates get approved. Frequently each root certificate has a different CP/CPS and other related information. So, even though a CA may create one inclusion request in Bugzilla, we actually need to consider each root certificate separately. Therefore, for a root inclusion request, one Case will be opened, with a Root Case for each root certificate under consideration. The Case has the CA-level information, and each Root Case has the information specific to each root certificate.

For now, I will be entering the data into SalesForce myself, but in the future I am hoping to set it up so that CAs can enter the data themselves, and then I just have to verify it.

I will appreciate your thoughtful and constructive feedback on the new CAInformation document.

Kathleen
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to