Re: NAVER: Public Discussion of Root Inclusion Request

2020-10-21 Thread Ryan Sleevi via dev-security-policy
On Wed, Oct 21, 2020 at 2:09 PM Matthias van de Meent via dev-security-policy wrote: > Hi, > > In the CPS v1.4.3 of NAVER, section 4.9.3, I found the following: > > > 4.9.3 Procedure for Revocation Request > > The NAVER BUSINESS PLATFORM processes a revocation request as follows: > > [...] > >

Re: NAVER: Public Discussion of Root Inclusion Request

2020-10-21 Thread Matthias van de Meent via dev-security-policy
Hi, In the CPS v1.4.3 of NAVER, section 4.9.3, I found the following: > 4.9.3 Procedure for Revocation Request > The NAVER BUSINESS PLATFORM processes a revocation request as follows: > [...] > 4. For requests from third parties, The NAVER BUSINESS PLATFORM personnel > begin investigating the

CCADB Proposal: Add field called Full CRL Issued By This CA

2020-10-21 Thread Kathleen Wilson via dev-security-policy
All, Root store operators would like to easily find and use the URLs to the Full CRLs for things like Mozilla’s CRLite. The BRs do not require CRL URLs in end-entity certificates, and many CAs use partitioned CRLs for end-entity certificates. Proposal: Add field called 'Full CRL Issued By

Re: NAVER: Public Discussion of Root Inclusion Request

2020-10-21 Thread Ben Wilson via dev-security-policy
Here is NAVER's response which I am forwarding from them: Here is NAVER Business Platform's response to the comment: - Hello, I am Sooyoung at NAVER Business Platform. As George mentioned, all the certificates, with both of city and province names in