Good recommendation, thank you.  Looks like we have 2 endorsers, Mozilla and 
Trend. Assume they agree with the change.

 

From: Peter Bowen [mailto:[email protected]] 
Sent: Thursday, March 17, 2016 12:13 PM
To: Dean Coclin <[email protected]>
Cc: CABFPub <[email protected]>
Subject: Re: [cabfpub] Pre-ballot on membership requirement update

 

Dean,

 

The language is a little wonky.  The Applicant is a CA according to our 
definition, it is not something they have.  Also we have two categories of CAs, 
Root CAs and Issuing CAs, so how about:

 

(7) The URL of at least one third party website that includes a certificate 
issued by the Applicant in the certificate chain.

 

This should cover both types of CAs.

 

Thanks,

Peter

 

On Mar 17, 2016, at 8:28 AM, Dean Coclin <[email protected] 
<mailto:[email protected]> > wrote:

 

I am looking for 2 endorsers for the following:

 

Background:

Section 2.1 (a)(1) says that Issuing CAs “actively issue certificates to Web 
servers…”

 

Section 2.1(b) of the bylaws lists the items needed in a membership application 
by CAs. 

But that section does not ask the CA applicant to provide a 3rd party website 
where the CA/B Forum can validate that they are actively issuing certs to web 
servers.  We do however ask the applicant this question, after they have 
submitted their application. It would be helpful to have this in the bylaws so 
we don’t have to go back and ask every time.

 

Specific change:

 

Add under 2.1(b) 

(7) The URL of at least one third party website that is using a certificate 
from the applicant’s CA which can be examined by Forum members

 

Thanks,
Dean

 

_______________________________________________
Public mailing list
 <mailto:[email protected]> [email protected]
 <https://cabforum.org/mailman/listinfo/public> 
https://cabforum.org/mailman/listinfo/public

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Public mailing list
[email protected]
https://cabforum.org/mailman/listinfo/public

Reply via email to