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

Wed Jan 27 19:01:33 MST 2016

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<mailto:Dean_Coclin at symantec.com>>; 'Ben Wilson' <ben.wilson at digicert.com<mailto:ben.wilson at digicert.com>>; policyreview at cabforum.org<mailto: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<mailto: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> [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<mailto:ben.wilson at digicert.com>>; policyreview at cabforum.org<mailto: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<mailto: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.

<table class="TM_EMAIL_NOTICE"><tr><td><pre>
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.
</pre></td></tr></table>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://cabforum.org/pipermail/validation/attachments/20160128/11a61e28/attachment-0001.html 