[cabf_validation] FW: [cabfcert_policy] A question about EV SSL Certificate Guidelines 11.2.1. Verification Requirements

Tue Feb 23 03:27:09 MST 2016

Dear Kirk,

        Thank you for your arrangement and future discussion in VWG call this week. 

        It is very good for us to use zoom to attend F2F meeting as we can fly to F2F meeting once a year by our company’s budget.

        Li-Chun 

From: kirk_hall at trendmicro.com [mailto:kirk_hall at trendmicro.com] 
Sent: Tuesday, February 23, 2016 8:52 AM
To: 陳立群; 'Dean Coclin'; validation at cabforum.org
Cc: 王文正
Subject: RE: [cabf_validation] FW: [cabfcert_policy] A question about EV SSL Certificate Guidelines 11.2.1. Verification Requirements

Li-Chun – I apologize for not responding to you earlier on this.

The Validation Working Group (VWG) spent all its time on its last two phone calls on the new domain validation methods.  This was so we would be ready for the face to face meeting in Scottsdale last week.

We have a VWG call this week, and I will bring up your suggestion – I think it looks good and is an improvement to the EV Guidelines.

Thanks for your patience.

Kirk

From: 陳立群 [mailto:realsky at cht.com.tw] 
Sent: Monday, February 15, 2016 2:51 AM
To: Kirk Hall (RD-US); 'Dean Coclin'; validation at cabforum.org
Cc: 王文正
Subject: RE: [cabf_validation] FW: [cabfcert_policy] A question about EV SSL Certificate Guidelines 11.2.1. Verification Requirements

Dear Kirk,

      As below sentences in EVGL 8.5.4 section about Registration Agency for Business Entity Subjects,  I suggest to modify the wording of EVGL 11.2.1 3(B)

      8.5.4. Business Entity Subjects

An Applicant qualifies as a Business Entity if:

(1) The entity is a legally recognized entity that filed certain forms with a Registration Agency in its jurisdiction, the

Registration Agency issued or approved the entity’s charter, certificate, or license, and the entity’s existence can be

verified with that Registration Agency;

(2) The entity has a verifiable physical existence and business presence;

(3) At least one Principal Individual associated with the entity is identified and validated by the CA;

(4) The identified Principal Individual attests to the representations made in the Subscriber Agreement;

(5) the CA verifies the entity’s use of any assumed name used to represent the entity pursuant to the requirements of

Section 11.3 herein;

Sincerely Yours,

           Li-Chun

From: 陳立群 [mailto:realsky at cht.com.tw] 
Sent: Thursday, January 28, 2016 6:37 PM
To: 'kirk_hall at trendmicro.com'; 'Dean Coclin'; 'validation at cabforum.org'
Cc: 王文正
Subject: RE: [cabf_validation] FW: [cabfcert_policy] A question about EV SSL Certificate Guidelines 11.2.1. Verification Requirements

Dear Kirk,

        I hope as  

     EVGL 11.2.1 (

3) Business Entity Subjects ***

(B) Organization Name: Verify that the Applicant’s formal legal name as recognized by the Registration agency or Registration Authority in the Applicant’s Jurisdiction of Registration matches the Applicant’s name in the EV Certificate Request.

       Note that, in the 4. Definitions, there are

Registration Agency: A Governmental Agency that registers business information in connection with an entity’s

business formation or authorization to conduct business under a license, charter or other certification. A Registration

Agency MAY include, but is not limited to (i) a State Department of Corporations or a Secretary of State; (ii) a

licensing agency, such as a State Department of Insurance; or (iii) a chartering agency, such as a state office or

department of financial regulation, banking or finance, or a federal agency such as the Office of the Comptroller of the

Currency or Office of Thrift Supervision.

Incorporating Agency: In the context of a Private Organization, the government agency in the Jurisdiction of

Incorporation under whose authority the legal existence of the entity is registered (e.g., the government agency that

issues certificates of formation or incorporation). In the context of a Government Entity, the entity that enacts law,

regulations, or decrees establishing the legal existence of Government Entities.

And it SSL BR:

1.6. DEFINITIONS AND ACRONYMS

Registration Authority (RA): Any Legal Entity that is responsible for identification and authentication of

subjects of Certificates, but is not a CA, and hence does not sign or issue Certificates. An RA may assist in the

certificate application process or revocation process or both. When “RA” is used as an adjective to describe a

role or function, it does not necessarily imply a separate body, but can be part of the CA.

      But you said “in the US, Business Entities (non-incorporated entities like a general partnership) generally do not file any documents with an “Incorporating Authority” the way a Private Organization (like a corporation) does.”, so maybe we have to reserve the term Registration Authority
and read as 

3) Business Entity Subjects ***

(B) Organization Name: Verify that the Applicant’s formal legal name as recognized by the Registration agency or Registration Authority in the Applicant’s Jurisdiction of Registration matches the Applicant’s name in the EV Certificate Request.

Sincerely Yours,

       Li-Chun

From: kirk_hall at trendmicro.com [mailto:kirk_hall at trendmicro.com] 
Sent: Thursday, January 28, 2016 10:02 AM
To: Dean Coclin; validation at cabforum.org
Cc: 陳立群
Subject: RE: [cabf_validation] FW: [cabfcert_policy] A question about EV SSL Certificate Guidelines 11.2.1. Verification Requirements

Hi, Li-Chun – I think I agree with your suggested change, but I want to make sure I understand exactly what your suggested change is.

Do you want to amend EVGL 11.2.1(3)(b) to read as follows?

EVGL 11.2.1 (

3) Business Entity Subjects ***

(B) Organization Name: Verify that the Applicant’s formal legal name as recognized by the Incorporating or Registration Authority in the Applicant’s Jurisdiction of Registration matches the Applicant’s name in the EV Certificate Request.

This would make (3)(B) for Business Entity Subjects the same as (1)(B) for Private Organizations.  (A Business Entity is like a partnership, while a Private Organization is like a corporation.)

Is that the change that you are suggesting?

My only thought is that in the US, Business Entities (non-incorporated entities like a general partnership) generally do not file any documents with an “Incorporating Authority” the way a Private Organization (like a corporation) does.  However, it is possible that in some countries they do – so I would not object to a change.

Kirk

From: validation-bounces at cabforum.org [mailto:validation-bounces at cabforum.org] On Behalf Of Dean Coclin
Sent: Sunday, January 24, 2016 12:39 AM
To: validation at cabforum.org
Cc: 陳立群
Subject: [cabf_validation] FW: [cabfcert_policy] A question about EV SSL Certificate Guidelines 11.2.1. Verification Requirements

Forwarding on behalf of Li-Chun. Please see his question below.  Can someone from the Validation group please answer?

Thanks
Dean

From: 陳立群 [mailto:realsky at cht.com.tw] 
Sent: Sunday, January 24, 2016 3:06 PM
To: Dean Coclin <Dean_Coclin at symantec.com>; 'Ben Wilson' <ben.wilson at digicert.com>; policyreview at cabforum.org
Subject: RE: [cabfcert_policy] A question about EV SSL Certificate Guidelines 11.2.1. Verification Requirements

Dear Dean,

      I am not a member of validation working group. (Although I have joined a conference call one time of validation working group as I remember a wrong time for Certificate Policy Working Group).

      Please help me to post my question to the validation working group. Thank you.

Sincerely Yours,

             Li-Chun 

From: Dean Coclin [mailto:Dean_Coclin at symantec.com] 
Sent: Saturday, January 23, 2016 1:59 PM
To: 陳立群; 'Ben Wilson'; policyreview at cabforum.org
Subject: RE: [cabfcert_policy] A question about EV SSL Certificate Guidelines 11.2.1. Verification Requirements

Sounds like a question more for the validation working group. Would you like to post it there? If you are not part of that group, we can post for you. Please advise.

Dean

From: policyreview-bounces at cabforum.org [mailto:policyreview-bounces at cabforum.org] On Behalf Of ???
Sent: Friday, January 22, 2016 5:59 PM
To: 'Ben Wilson' <ben.wilson at digicert.com>; policyreview at cabforum.org
Subject: [cabfcert_policy] A question about EV SSL Certificate Guidelines 11.2.1. Verification Requirements

Dear All,

       For EV SSL Certificate Guidelines 11.2.1. Verification Requirements , 

       (3) Business Entity Subjects

       (B) Organization Name: Verify that the Applicant’s formal legal name as recognized by the Registration Authority in the Applicant’s Jurisdiction of Registration matches the Applicant’s name in the EV Certificate

Request.

      Will it be suitable as 

(3) Business Entity Subjects

       (B) Organization Name: Verify that the Applicant’s formal legal name as recognized by the Registration Agency in the Applicant’s Jurisdiction of Registration matches the Applicant’s name in the EV Certificate

Request.

       As I compare with other type  such as 

(1) Private Organization Subjects

(B) Organization Name: Verify that the Applicant’s formal legal name as recorded with the Incorporating or

Registration Agency in the Applicant’s

Sincerely Yours,

Li-Chun CHEN

                    Senior Engineer

                    CISSP, CISA, CISM, PMP,

                    Information & Communication Security Dept.

                    Data Communication Business Group

                    Chunghwa Telecom Co. Ltd.

                    realsky at cht.com.tw

                    +886-2-2344-4820#4025

本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. 

Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.

本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. 

Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.

TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential 
and may be subject to copyright or other intellectual property protection. 
If you are not the intended recipient, you are not authorized to use or 
disclose this information, and we request that you notify us by reply mail or
telephone and delete the original message from your mail system.

本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. 

Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.

TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential 
and may be subject to copyright or other intellectual property protection. 
If you are not the intended recipient, you are not authorized to use or 
disclose this information, and we request that you notify us by reply mail or
telephone and delete the original message from your mail system.

本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. 
Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://cabforum.org/pipermail/validation/attachments/20160223/c96db936/attachment-0001.html 