Given that the patent disclosures have been withdrawn, the proposed changes in ballot 190, and that the validation working group will be working on a revised ballot for the remaining methods during the face to face, could Action 1 include methods added/revised in ballots adopted after 1.4.1? That way the CAs can introduce the revised methods rather than only the methods in 1.4.1 as written.
-----Original Message----- From: dev-security-policy [mailto:dev-security-policy-bounces+jeremy.rowley=digicert.com@lists.mozilla .org] On Behalf Of Gervase Markham via dev-security-policy Sent: Friday, March 17, 2017 9:41 AM To: mozilla-dev-security-pol...@lists.mozilla.org Subject: Re: Mozilla Root Store Policy 2.4.1 On 06/03/17 15:10, Gervase Markham wrote: > The next stage in the improvement of the Mozilla Root Store Policy is > version 2.4.1. This is version 2.4, but rearranged significantly to > have a more topic-based ordering and structure to it. I have also made > editorial changes to clean up and clarify language, and improved the > Markdown markup. Thanks to Ryan for reviewing this, and I need to come back to his comments. If anyone else has time to look through it, I would be most grateful. CAs: this is worth your time, because you don't want a new normative requirement sprung on you accidentally! ;-) Gerv _______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
