[cabfpub] Ballot 150 - OIDs

Thu Aug 27 13:49:52 UTC 2015

Dear Jeremy,

    What about change the wording of B.R about OV OID to below red line, as
https://bugzilla.cabforum.org/show_bug.cgi?id=2

 or attached file at 33rd F2F meeting that

“Certificate Field: subject:localityName may be absent if a an applicant is
registered as a national company or a national organization, also
stateOrProvinceName field is

absent.

If the Certificate asserts the policy identifier of 2.23.140.1.2.2, then it
MUST also include organizationName, localityName(if applicable),
stateOrProvinceName (if applicable), and countryName in the Subject field.

    Or as we met Ben and Moudrick in conference in Taipei, Ben said that
localityName  field is not mandatory . It depends on the opinion of the
auditor.

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

From: public-bounces at cabforum.org [mailto:public-bounces at cabforum.org] On
Behalf Of Jeremy Rowley
Sent: Thursday, August 20, 2015 11:26 PM
To: public at cabforum.org
Subject: [cabfpub] Ballot 150 - OIDs

Here’s an updated draft of the OID ballot:

Ballot 150-Addition of Optional OID for Individual Validation

 The following motion has been proposed by Dean Coclin of Symantec and
endorsed by Jeremy Rowley of Digicert and Kirk Hall of Trend Micro.

-- MOTION BEGINS -

1)      Modify section 1.2 of Baseline Requirements as follows:

1.2 Document Name and Identification

This certificate policy (CP) contains the requirements for the issuance and
management of publicly‐trusted SSL certificates, as adopted by the
CA/Browser Forum.

The following Certificate Policy identifiers are reserved for use by CAs as
an optional means of asserting compliance with this CP (OID arc
2.23.140.1.2) as follows:

{joint‐iso‐itu‐t(2) international‐organizations(23) ca‐browser‐
forum(140) certificate‐policies(1) baseline‐ requirements(2) domain‐
validated(1)} (2.23.140.1.2.1);

{joint‐iso‐itu‐t(2) international‐organizations(23) ca‐browser‐
forum(140) certificate‐policies(1) baseline‐ requirements(2)
organization-validated(2)} (2.23.140.1.2.2) and

{joint‐iso‐itu‐t(2) international‐organizations(23) ca‐browser‐
forum(140) certificate‐policies(1) baseline‐ requirements(2)
individual-validated(3)} (2.23.140.1.2.3).

2)      Modify section 7.1.6.1 of the Baseline Requirements as follows:

7.1.6.1. Reserved Certificate Policy Identifiers

This section describes the content requirements for the Root CA, Subordinate
CA, and Subscriber Certificates, as they relate to the identification of
Certificate Policy.

The following Certificate Policy identifiers are reserved for use by CAs as
an optional means of asserting compliance with these Requirements as
follows:

{joint‐iso‐itu‐t(2) international‐organizations(23) ca‐browser‐
forum(140) certificate‐policies(1) baseline‐requirements(2) domain‐
validated(1)} (2.23.140.1.2.1), if the Certificate complies with these
Requirements but lacks Subject Identity Information that is verified in
accordance with either Section 3.2.2.1 or Section 3.2.3.

If the Certificate asserts the policy identifier of 2.23.140.1.2.1, then it
MUST NOT include organizationName, givenName, surname, streetAddress,
localityName, stateOrProvinceName, or postalCode in the Subject field.

{joint‐iso‐itu‐t(2) international‐organizations(23) ca‐browser‐
forum(140) certificate‐policies(1) baseline‐requirements(2)
organization-validated(2)} (2.23.140.1.2.2), if the Certificate complies
with these Requirements and includes Subject Identity Information that is
verified in accordance with Section 3.2.2.1.

{joint‐iso‐itu‐t(2) international‐organizations(23) ca‐browser‐
forum(140) certificate‐policies(1) baseline‐requirements(2)
individual-validated(3)} (2.23.140.1.2.3), if the Certificate complies with
these Requirements and includes Subject Identity Information that is
verified in accordance with Section 3.2.3.

If the Certificate asserts the policy identifier of 2.23.140.1.2.2, then it
MUST also include organizationName, localityName, stateOrProvinceName (if
applicable), and countryName in the Subject field. If the Certificate
asserts the policy identifier of 2.23.140.1.2.3, then it MUST also include
(i) either organizationName or givenName and surname, (ii) localityName,
(iii) stateOrProvinceName (if applicable), and (iv) countryName in the
Subject field.

3)      Modify the definition of “EV OID” in the EV Guidelines as follows:

EV OID: An identifying number, in the form of an “object identifier,” that
is included in the certificatePolicies field of a certificate that: (i)
indicates which CA policy statement relates to that certificate, and (ii) is
either the CA/Browser Forum EV policy identifier or a  policy identifier
that, by pre-agreement with one or more Application Software Supplier, marks
the certificate as being an EV Certificate.

4)      Modify Section 9.3.2 of the EV Guidelines as follows:

Each EV Certificate issued by the CA to a Subscriber MUST contain a policy
identifier that is either defined by these Guidelines or the CA in the
certificate’s certificatePolicies extension that: (i) indicates which CA
policy statement relates to that Certificate, (ii) asserts the CA’s
adherence to and compliance with these Guidelines, and (iii), is either the
CA/Browser Forum’s EV policy identifier or a policy identifier that, by
pre-agreement with the Application Software Supplier, marks the Certificate
as being an EV Certificate.

The following Certificate Policy identifier is the CA/Browser Forum’s EV
policy identifier:

{joint‐iso‐itu‐t(2) international‐organizations(23) ca‐browser‐
forum(140) certificate‐policies(1) ev-guidelines (1) } (2.23.140.1.1), if
the Certificate complies with these Guidelines.

If the ballot passes, the custodian of the Forum OIDs will be instructed to
obtain the new OID for IV as indicated above.

-- MOTION ENDS -

The review period for this ballot shall commence at 2200 UTC on Friday,
August 21, 2015, and will close at 2200 UTC on Friday, August 27, 2015.
Unless the motion is withdrawn during the review period, the voting period
will start immediately thereafter and will close at 2200 UTC on Friday,
September 4, 2015. Votes must be cast by posting an on-list reply to this
thread.

A vote in favor of the motion must indicate a clear 'yes' in the response. A
vote against must indicate a clear 'no' in the response. A vote to abstain
must indicate a clear 'abstain' in the response. Unclear responses will not
be counted. The latest vote received from any representative of a voting
member before the close of the voting period will be counted. Voting members
are listed here:  <https://cabforum.org/members/>
https://cabforum.org/members/

In order for the motion to be adopted, two thirds or more of the votes cast
by members in the CA category and greater than 50% of the votes cast by
members in the browser category must be in favor. Quorum is currently nine
(9) members- at least nine members must participate in the ballot, either by
voting in favor, voting against, or abstaining.

本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. 
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: <http://lists.cabforum.org/pipermail/public/attachments/20150827/8c0ab7d0/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Suggestions-to-Correct-Documents.pdf
Type: application/pdf
Size: 1689045 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/public/attachments/20150827/8c0ab7d0/attachment-0003.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7964 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/public/attachments/20150827/8c0ab7d0/attachment-0001.p7s>