CA/Browser Forum
Home » All CA/Browser Forum Posts » 2022-07-21 Minutes of the CA/Browser Forum Teleconference

2022-07-21 Minutes of the CA/Browser Forum Teleconference

Attendees: Aaron Poulsen (Amazon), Adam Jones (Microsoft), Adrian Mueller (SwissSign), Andrea Holland (SecureTrust), Ben Wilson (Mozilla), Bruce Morton (Entrust), Chris Clements (Google), Chris Kemmerer (SSL.com), Chris McMillan (Visa), Clint Wilson (Apple), Corey Bonnell (Digicert), Corey Rasmussen (OATI), Daryn Wright (GoDaddy), Dean Coclin (Digicert), Devon O’Brien (Google), Dimitris Zacharopoulos (HARICA), Doug Beattie (GlobalSign), Dustin Hollenback (Microsoft), Fumi Yoneda (Japan Registry Services), Hogeun Yoo (NAVER Cloud), Hubert Chao (Google), Inaba Atsushi (GlobalSign), Inigo Barreira (Sectigo), Janet Hines (SecureTrust), Johnny Reading (GoDaddy), Jos Purvis (Fastly), Karina Sirota (Microsoft), Kiran Tummala (Microsoft), Lynn Jeun (Visa), Marcelo Silva (Visa), Michelle Coon (OATI), Nargis Mannan (SecureTrust), Nicolas Lidzborski (Google), Paul van Brouwershaven (Entrust), Peter Miskovic (Disig), Rebecca Kelley (Apple), Sooyoung Eo (NAVER Cloud), Stephen Davidson (Digicert), Steven Deitte (GoDaddy), Tadahiko Ito (SECOM Trust Systems), Thomas Zermeno (SSL.com), Tobias Josefowitz (Opera Software AS), Tyler Myers (GoDaddy), Wayne Thayer (Fastly), Wendy Brown (US Federal PKI Management Authority), Yoshiro Yoneya (Japan Registry Services)

Meeting conducted by vice-chair Karina Sirota

  1. The anti-trust statement was read.

  2. The agenda was reviewed. No changes.

  3. Approval of minutes of last call. Approved.

  4. Forum Infrastructure Report: Jos gave the report. Spam pull requests on github were discussed at the last meeting (as one had recently occurred). This raised the question of how to restrict this. The group is researching it. In the meantime, a field will be added to the management membership tool of github user names. This will help keep track of the authorized users. A discussion of the website also occurred. Ben will discuss with GoDaddy. Also a discussion about mail delivery took place, which seems stable at this point. Lastly, the membership management tool is almost ready. Will discuss with Martijn when he returns. For phase 2, the membership tools will do the mailing list management automatically.

  5. Code Signing Working Group report: Janet Hines gave the update. The signing service discussion was deferred until Bruce’s return. On timestamping, a further discussion needs to take place before a draft ballot is proposed. The malware proposal will be discussed on the next call.

  6. S/MIME Working Group report: Stephen gave the update. Certipath has joined as an Associate Member and Visa has joined as a Certificate Issuer. The S/MIME draft discussions are continuing. Topics around Org ID will necessitate some tweaks to the draft. Expecting a formal ballot at the end of the summer.

  7. NetSec Working Group report: Clint gave the update. A threat assessment update was discussed and the github backlog was reviewed. If anyone has comments, please look in the CA/B Forum Netsec repository and provide your feedback.

  8. Any other business: Forum-18 is in discussion period. Next F2F in Berlin is open for signup. CA Day is also the same week. Wayne asked if any information has been published yet. Enrico and Arno are the ones to follow-up with.

  9. Meeting Adjourned

Latest releases
Server Certificate Requirements
SC100: DNSSEC Clarification and Consolidation - Sep 7, 2026

Code Signing Requirements
v3.8 - Aug 5, 2024

What’s Changed CSC-25: Import EV Guidelines to CS Baseline Requirements by @dzacharo in https://github.com/cabforum/code-signing/pull/38 Full Changelog: https://github.com/cabforum/code-signing/compare/v3.7...v3.8

S/MIME Requirements
v1.0.17 - Ballot SMC020 - Nov 20, 2026

Addresses https://github.com/cabforum/smime/issues/308. Aligns the S/MIME BR with TLS BR Ballot SC-099. Changes Section 3.2.2: Removes the requirement to record the validation method “including the relevant version number” from the TLS BR or S/MIME BR. This version number is unclear and can’t be enforced. It also creates problems for CAs that share validation services with TLS and have already stopped logging it. Section 5.4.1 (2.ii): Effective March 15, 2027, audit logs of verification activities must include: the information validated; the domain name whose control was validated, if different from the domain portion of the Mailbox Address (e.g., the Authorization Domain Name or SMTP FQDN); the validation method used. Together with the time and date that 5.4.1 already requires, this is enough to tell which requirements applied to a validation. Section 1.2.1: Adds revision and compliance date rows. The ballot number and publication date are placeholders. Differences from SC-099 Uses “domain name whose control was validated” instead of “ADN”, because ADN is not defined in the SBR and S/MIME also covers SMTP FQDN validation (3.2.2.3). The method can refer to a section of either the SBR or the TLS BR, because 3.2.2.1 and 3.2.2.3 rely on TLS BR 3.2.2.4.

Network and Certificate System Security Requirements
Version 2.0.5 (Ballot NS-008) - Jul 9, 2025

Edit this page
The Certification Authority Browser Forum (CA/Browser Forum) is a voluntary gathering of Certificate Issuers and suppliers of Internet browser software and other applications that use certificates (Certificate Consumers).