[cabfpub] Cert Policy Working Group activity

[Tim Hollebeek]

That may be a good way to handle EV as well.

-----Original Message-----
From: public-bounces at cabforum.org [mailto:public-bounces at cabforum.org] On Behalf Of Gervase Markham
Sent: Wednesday, September 16, 2015 4:51 AM
To: Dean Coclin; richard.smith at comodo.com; public at cabforum.org
Subject: Re: [cabfpub] Cert Policy Working Group activity

On 15/09/15 20:39, Dean Coclin wrote:
> On #2, the group felt that RFC 3647 contains the exact placeholders
> for the items currently in the network security requirements and
> that's why it made sense to merge those in. As many of you know, the
> Network Security requirements were composed after the Diginotar and
> Comodo incidents to address a gap in the BRs. Although they are not as
> stringent as some would have liked, they do provide meaningful
> improvements to the security of the ecosystem, with an opportunity for
> further enhancement as we review them again.

I have no objection to making people's lives easier... but if the Network Security Requirements were converted to an independent document in RFC3647 format (and particularly if both documents were Markdown) then doing an automatic merge of the two, using the section numbers, to produce an unofficial unified document would be the work of a fairly short script, which I would be willing to write.

Is that a way forward which meets people's usability goals without formally combining the two documents?

Gerv
_______________________________________________
Public mailing list
Public at cabforum.org
http://scanmail.trustwave.com/?c=4062&d=kK351Sxkn4W4vSqwznE_KQXkINLKIv1ADOKtFpwycA&s=5&u=https%3a%2f%2fcabforum%2eorg%2fmailman%2flistinfo%2fpublic

________________________________

This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.