[cabfpub] Public Digest, Vol 61, Issue 143

Virginia Fournier vfournier at apple.com
Mon May 22 20:50:49 UTC 2017

Hi Kirk,

Ballot 200 will be in the voting period starting tomorrow I believe.  So by Thursday’s meeting it will be in the voting period rather than the discussion period.

Interesting that there has not been one peep about it.

Best regards,

Virginia Fournier
Senior Standards Counsel
 Apple Inc.
☏ 669-227-9595
✉︎ vmf at apple.com

On May 21, 2017, at 6:03 PM, public-request at cabforum.org wrote:

Send Public mailing list submissions to
	public at cabforum.org

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
	public-request at cabforum.org

You can reach the person managing the list at
	public-owner at cabforum.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Public digest..."

Today's Topics:

  1. Re: Preballot - Revised Ballot 190 (Peter Bowen)
  2. Draft Agenda for Thursday May 25 CABF Teleconference (Kirk Hall)


Message: 1
Date: Sat, 20 May 2017 11:09:23 -0700
From: Peter Bowen <pzb at amzn.com>
To: CA/Browser Forum Public Discussion List <public at cabforum.org>,
	Ryan Sleevi	<sleevi at google.com>, Jeremy Rowley
	<jeremy.rowley at digicert.com>
Subject: Re: [cabfpub] Preballot - Revised Ballot 190
Message-ID: <D7D42F39-304C-465E-9A81-8BFA0295E92C at amzn.com>
Content-Type: text/plain; charset="utf-8"

> On May 20, 2017, at 8:11 AM, Peter Bowen <pzb at amzn.com> wrote:
>> On May 20, 2017, at 7:41 AM, Ryan Sleevi via Public <public at cabforum.org <mailto:public at cabforum.org>> wrote:
>> On Fri, May 19, 2017 at 9:47 PM, Jeremy Rowley <jeremy.rowley at digicert.com <mailto:jeremy.rowley at digicert.com>> wrote:
>> ?The certificate request MAY include all factual information about the Applicant to be included in the Certificate, and such additional information as is necessary for the CA to obtain from the Applicant in order to comply with these Requirements and the CA?s Certificate Policy and/or Certification Practice Statement.?
>> This indicates a certificate request may include partial information.
>> I appreciate you mentioning this - as I've mentioned it several times - but this doesn't address the concern related to 4.1.2
> How about we solve this by changing 4.2.1 to say:
> "The	CA	MUST have obtained documents	and	data used to	verify	certificate	information no	more	than	825	days	prior	to	issuing	the	Certificate.?
> This could also move to section 3.2 itself to help readers and implementers, as having it down in 4.2.1 has clearly caused confusion.

Looking back at this thread, I suggest we also modify

The	CA	MUST confirm, prior to certificate issuance, that either	the	CA	or	a	Delegated	Third	Party	has	validated	each	Fully?Qualified	Domain	Name	(FQDN)	listed	in	the	Certificate using either one	of	the	methods	listed	below or a method that was allowed by the Baseline Requirements if effect at the time of validation.  The validation must have occurred no more than 825 days prior to certificate issuance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/public/attachments/20170520/68be95f1/attachment-0001.html>


Message: 2
Date: Mon, 22 May 2017 01:03:42 +0000
From: Kirk Hall <Kirk.Hall at entrustdatacard.com>
To: CA/Browser Forum Public Discussion List <public at cabforum.org>
Subject: [cabfpub] Draft Agenda for Thursday May 25 CABF
	<e4baa4f6febf4616ae1a2fa2a86a7051 at PMSPEX04.corporate.datacard.com>
Content-Type: text/plain; charset="us-ascii"

Here is a draft agenda for our call this Thursday, May 25.  Please offer edits and suggestions.

1.      Roll Call

2.      Read Antitrust Statement

3.      Review Agenda

Approve Minutes of CABF teleconference of May 11, 2017 as amended

4.      Governance Change Working Group update.

5.      Validation Working Group update.

6.      Policy Review Working Group update.

7.      Charter for new Security Controls Working Group (to update Network Security requirements)

8.      Ballot Status (see list below)

9.      New Bylaw to resolve procedural disputes (ballot errors, voting issues)

10.  Next F2F meeting:
June 20-22, 2017 Berlin (D-Trust) - Suggested F2F Agenda Items

11.  Any Other Business

12.  Next call June 8, 2017

13.  Adjourn


CURRENT STATUS OF BALLOTS (as of May 11, 2017)

1. Ballots in Voting Period

a)      Ballot 191 - Clarify Place of Business Information (Jeremy) - ends May 23

2. Ballots in Discussion Period

a)      Ballot 200 - CA/Browser Forum Code of Conduct (Virginia) - ends May 23

3. Ballots in Review Period

a)     Ballot 197 - Effective Date of Ballot 193 Provisions - ends June 2

b)     Ballot 198 - Onion Revisions  - ends June 8 - Uncertain

c)      Ballot 199 - Require commonName in Root and Intermediate Certificates  - ends June 8

4. Draft Ballots

a)     Ballot 184 - RFC 822 Names and otherNames, SRV names (Jeremy)

b)     Ballot 186 - Limiting reuse of validation information (Ryan)

c)      Ballot 190 - BR Validation Methods (Jeremy)

d)     Ballot 191 - Clarify Place of Business Info (Jeremy)

e)     Ballot 192- Notary Clarification (Jeremy)

f)       Ballot 201 - .Onion Revisions (Jeremy)

g)     RAs and Delegated Third Parties (Gerv)

h)     Expected ASN.1 grammar for BR & EV certificates (Peter)

i)       Bylaws change - Membership requirements (Gerv)

j)       Bylaw change - Voting rules (Jos)

k)      Requiring RFC 3647 format (Ryan)

l)       Profiling OCSP & CRLs (Ryan)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/public/attachments/20170522/0784b522/attachment.html>


Subject: Digest Footer

Public mailing list
Public at cabforum.org


End of Public Digest, Vol 61, Issue 143

More information about the Public mailing list