On Tuesday, March 21, 2017 at 7:17:26 AM UTC-7, Gervase Markham wrote: > On 17/03/17 11:30, Gervase Markham wrote: > > The URL for the draft of the next CA Communication is here: > > https://mozilla-mozillacaprogram.cs54.force.com/Communications/CACommunicationSurveySample?CACommunicationId=a050S000000G3K2 > > A few more wording tweaks on the current version: > > * Action 1 says: "Date must be before June 1, 2017". That gives CAs 2 > months to make a CP/CPS update. Do we normally allow a bit more than > that for non-urgent updates? Say, 3 months?
Updated to "Date must be before July 21, 2017." (3 months from when survey must be completed) > > * "I understand that our CP/CPS documents shall be updated each year" -> > "I understand that our CP/CPS documents should be reviewed and the > version number incremented each year" Action 2 option updated to: "I understand that our CP/CPS documents must be reviewed annually to ensure continued compliance with the CA/Browser Forum's Baseline Requirements, and that at least the version number should be incremented each year." > > * Action 8: "Our current policy is...". In hindsight, this is ambiguous > - it could be Mozilla's policy, and the CA is just affirming they > understand it. Instead say "The current policy of our CA is...". Done. Thanks, Kathleen _______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
