Confirmed users, Administrators
5,526
edits
CA/Required or Recommended Practices: Difference between revisions
Added newer examples of CP/CPS review feedback
m (Add sub-section about CAA domains being listed in CP/CPS) |
(Added newer examples of CP/CPS review feedback) |
||
| Line 24: | Line 24: | ||
Here are some examples of previous reviews of CP/CPS documents: | Here are some examples of previous reviews of CP/CPS documents: | ||
* [https://groups.google.com/d/msg/mozilla.dev.security.policy/36t-jbTQnTY/nwkFyzobAgAJ Review Feedback on WISeKey] | |||
** That was after [https://bugzilla.mozilla.org/show_bug.cgi?id=1403591#c17 blocking problems with the CP/CPS] were resolved. | |||
* [https://groups.google.com/d/msg/mozilla.dev.security.policy/skev4gp_bY4/snIuP2JLAgAJ Review Feedback on Camerfirma] | |||
** CA may submit new root inclusion request for newly generated root that is fully compliant with Mozilla's Root Store Policy and the BRs. | |||
* [https://groups.google.com/d/msg/mozilla.dev.security.policy/R2uG3wisU7s/ie_v7RHMBwAJ Review Feedback on TrustCor] | * [https://groups.google.com/d/msg/mozilla.dev.security.policy/R2uG3wisU7s/ie_v7RHMBwAJ Review Feedback on TrustCor] | ||
** CP and CPS documents clear, well written, and they provided sufficient detail to assess the policies in place. | ** CP and CPS documents clear, well written, and they provided sufficient detail to assess the policies in place. | ||