Re: Drafting Q1 2016 CA Communication

2016-03-22 Thread Charles Reiss
On 03/22/16 16:33, kwil...@mozilla.com wrote: > The following 'ACTION #1c' has been added to the communication, which > is here: https://wiki.mozilla.org/CA:Communications#March_2016 and > click on "Link to DRAFT of March 2016 CA Communication". With the current wordings of #1a and #1b, if - a CA

Re: CA ownership (re: Q1 2016 CA communication)

2016-03-22 Thread Kathleen Wilson
The following 'ACTION #7' has been added to the communication, which is here: https://wiki.mozilla.org/CA:Communications#March_2016 and click on "Link to DRAFT of March 2016 CA Communication". ~~ ACTION #7: Finally, please check the 'Owner' column in the spreadsheet of CA Certificates Included in

Re: CA ownership (re: Q1 2016 CA communication)

2016-03-22 Thread Jakob Bohm
On 22/03/2016 19:16, Peter Bowen wrote: Over the last year or so there seems to be a lot of movement in CA ownership. Would it be worth asking for each root to provide an indication of company/organization ownership? For example, NetLock indicates on their website they were acquired by Docler H

CA ownership (re: Q1 2016 CA communication)

2016-03-22 Thread Peter Bowen
Over the last year or so there seems to be a lot of movement in CA ownership. Would it be worth asking for each root to provide an indication of company/organization ownership? For example, NetLock indicates on their website they were acquired by Docler Holding in 2013. Similarly, TrustWave says

Re: FNMT Root Inclusion Request

2016-03-22 Thread kwilson
On Friday, March 11, 2016 at 5:50:47 AM UTC-8, raf...@gmail.com wrote: > El viernes, 15 de enero de 2016, 13:42:41 (UTC+1), raf...@gmail.com escribió: > > Hi all. > > > > We have developed a solution plan for this issues. > > > > We are going to audit in-scope CAs. Finally our FNMT-RCM CAs hiera

Re: ComSign Root Renewal Request

2016-03-22 Thread Jakob Bohm
Just one minor typo issue: On 22/03/2016 17:42, Eli Spitzer wrote: Hello, In response to the issues raised by Mr. Sleevi, we are making a number > of changes in to ComSign's CPS. > Some of the issues raised here will be addressed by the changes in the > CPS, while others will remain the same

Re: Drafting Q1 2016 CA Communication

2016-03-22 Thread kwilson
On Tuesday, March 22, 2016 at 9:33:19 AM UTC-7, kwi...@mozilla.com wrote: > The following 'ACTION #1c' has been added to the communication, which is here: > https://wiki.mozilla.org/CA:Communications#March_2016 > and click on "Link to DRAFT of March 2016 CA Communication". > Also, I have filled i

Re: ComSign Root Renewal Request

2016-03-22 Thread Eli Spitzer
Hello, In response to the issues raised by Mr. Sleevi, we are making a number of changes in to ComSign's CPS. Some of the issues raised here will be addressed by the changes in the CPS, while others will remain the same because we feel that they do not represent problems with our compliance to t

Re: ComSign Root Renewal Request

2016-03-22 Thread Eli Spitzer
Hello, In response to the issues raised by Mr. Sleevi, we are making a number of changes in to ComSign's CPS. Some of the issues raised here will be addressed by the changes in the CPS, while others will remain the same because we feel that they do not represent problems with our compliance to t

Re: Drafting Q1 2016 CA Communication

2016-03-22 Thread kwilson
The following 'ACTION #1c' has been added to the communication, which is here: https://wiki.mozilla.org/CA:Communications#March_2016 and click on "Link to DRAFT of March 2016 CA Communication". ~~ ACTION #1c: It has been pointed out in the mozilla.dev.security.policy forum that a chosen-prefix a