CA/Browser Forum posts
2025-07-17 Minutes of the Forum
July 17, 2025 by CA/B Forum Teleconference - 2025-07-17Meeting Title: CA/Browser Forum Date: 17 July 2025 Chair: Dean Coclin Minutes Taken By: Scott Rea 1. Roll Call and Housekeeping Meeting called to order by Dean Coclin with support from Tim Callan; recording in process. 2. Note-well Note-well has already been read in previous session. 3. Review Agenda Agenda anticipated as posted. 4. Approval of Minutes None to approve on today’s call April 10th - still pending (Dean to re-send link to Aaron Poulsen) F2F minutes requires 1 more item from Martijn 5. Server Certificate Working Group update SCWG (Wayne) Wayne indicated earlier meeting was first in some time since F2F (2 meetings skipped). For the prior meeting SC085 (Require DNSSEC for CAA and DCV Lookups) passed so now IPR review period in progress. Validation Subcommittee (Wayne from Corey’s minutes) Last meeting had 2 major talking points discussed: SC088 persistent DCV ballot. Doug raised some questions which were worked through in the meeting. Henry provided some options and the approach was agreed as being solid. Validation Summit proposal. Send a survey for identifying which methods CAs are using – decided probably not going to do this, but rather use CCADB Report instead. Decided to focus on 2 aspects the validation methods: i) the security of the method; ii) the agility of the method. Chrome proposed new draft ballot to deprecate all methods that use email and phone as a methos of contacting applicants. So maybe there will be impact to Validation Summit based on the discussion. 6. Code Signing Certificate Working Group update Martijn not available so Dean called for any updates from those attending. Karina: Microsoft working on ballot for reduction of validity - looking for additional endorser. Also cleanup ballot for alignment with TLS BRs discussions are on-going. 7. S/MIME Certificate Working Group update (Stephen) SMC012 (automation of mailbox control using ACME) is out of IPR Review and now adopted as of 1 week ago. In voting period for SMC013 (PQC for SMIME) closes in a few days. On-going discuss around pseudonyms for personal certificates is progressing. There will be a Forum level ballot at the end of summer to update the Charter for the Group. 8. NetSec Working Group update (Clint) Main discussion topic was Cloud Services in the context of public CAs. Tobi put together a starter document to facilitate discussion. NS008 (Updates to CA Infrastructure Scope, Trusted Roles, Systems’ Applicability, and various other improvements) came out of IPR, and effective date is scheduled for later this year. Clint mentioned he is having some GitHub issues getting NS008 finalized. 9. Definitions and Glossary Working Group (Tim & Tim) Not a lot of feedback on Definitions thus far so next steps is take one more pass, produce document and then proceed with a ballot. The document is expected that it will be a policy document - it is not a requirements document. Wendy indicated she did not see the definitions circulated, so they will be re-posted to the list. 10. Forum Infrastructure Subcommittee update (Ben) Wayne had some comments around on-going saga to fix permissions on mailing list, and how to approach that. It is a WIP. 11. Intellectual Property Rights Subcommittee (Ben) Forum-036 Ballot - Adopt Invited Experts Policy has passed. Next meeting scheduled for next Tuesday to begin addressing remaining items. 12. Bylaws Changes (Ben) Ben planning to progress forum bylaws change ballot once summer is over e.g. September timeline. 13. Entrust Status in CABF (Bruce) Entrust does not, or soon will not issue TLS certificates anymore after key(s) transfer to Sectigo, however they are still doing some Code Sign certificates currently. The goal is that by 1st week of September, Sectigo will have control of all keys (including CS). So after that point, Entrust will not qualify under current membership category (Certificate Issuer), but may be looking to transition to Interested Party type member at that point. Bruce will provide update after actions are complete. Tim H indicated that the qualifying event is not necessary the key transfer but rather “trusted by Root Programs” criteria. Tim C indicated that Entrust is still a trusted CA for CS purposes, so in this instance it’s a voluntary withdrawal when it happens. Wayne lead the appreciation for all the effort contributions Bruce & Co have made to the CABF. 14. Any Other Business Registration for Warsaw is open – please indicate attendance for planning purposes. Note that Trusted Economy Forum is also being held adjacent to this meeting. List of future F2F meetings schedule was reviewed: 2025 1. Oct 15-17: Warsaw, Poland (Certum) – REGISTRATION OPEN 2026 2. Houston, TX, US Spring 2026 SSL.com New York, NY,US Summer 2026 Google Trust Services Thessaloniki, GR Fall 2026 HARICA 2027 5. Scottsdale, AZ Spring 2027 Sectigo Switzerland June 2027 SwissSign Austin, TX, USA Fall 2027 IdenTrust 2028 8. Shanghai, China Spring 2028 TrustAsia (tentative) 15. Adjourn Next call: July 31, 2025
July 17, 2025 by CA/B Forum Teleconference - 2025-07-17Meeting Title: CA/Browser Forum Date: 17 July 2025 Chair: Dean Coclin Minutes Taken By: Scott Rea 1. Roll Call and Housekeeping Meeting called to order by Dean Coclin with support from Tim Callan; recording in process. 2. Note-well Note-well has already been read in previous session. 3. Review Agenda Agenda anticipated as posted. 4. Approval of Minutes None to approve on today’s call April 10th - still pending (Dean to re-send link to Aaron Poulsen) F2F minutes requires 1 more item from Martijn 5. Server Certificate Working Group update SCWG (Wayne) Wayne indicated earlier meeting was first in some time since F2F (2 meetings skipped). For the prior meeting SC085 (Require DNSSEC for CAA and DCV Lookups) passed so now IPR review period in progress. Validation Subcommittee (Wayne from Corey’s minutes) Last meeting had 2 major talking points discussed: SC088 persistent DCV ballot. Doug raised some questions which were worked through in the meeting. Henry provided some options and the approach was agreed as being solid. Validation Summit proposal. Send a survey for identifying which methods CAs are using – decided probably not going to do this, but rather use CCADB Report instead. Decided to focus on 2 aspects the validation methods: i) the security of the method; ii) the agility of the method. Chrome proposed new draft ballot to deprecate all methods that use email and phone as a methos of contacting applicants. So maybe there will be impact to Validation Summit based on the discussion. 6. Code Signing Certificate Working Group update Martijn not available so Dean called for any updates from those attending. Karina: Microsoft working on ballot for reduction of validity - looking for additional endorser. Also cleanup ballot for alignment with TLS BRs discussions are on-going. 7. S/MIME Certificate Working Group update (Stephen) SMC012 (automation of mailbox control using ACME) is out of IPR Review and now adopted as of 1 week ago. In voting period for SMC013 (PQC for SMIME) closes in a few days. On-going discuss around pseudonyms for personal certificates is progressing. There will be a Forum level ballot at the end of summer to update the Charter for the Group. 8. NetSec Working Group update (Clint) Main discussion topic was Cloud Services in the context of public CAs. Tobi put together a starter document to facilitate discussion. NS008 (Updates to CA Infrastructure Scope, Trusted Roles, Systems’ Applicability, and various other improvements) came out of IPR, and effective date is scheduled for later this year. Clint mentioned he is having some GitHub issues getting NS008 finalized. 9. Definitions and Glossary Working Group (Tim & Tim) Not a lot of feedback on Definitions thus far so next steps is take one more pass, produce document and then proceed with a ballot. The document is expected that it will be a policy document - it is not a requirements document. Wendy indicated she did not see the definitions circulated, so they will be re-posted to the list. 10. Forum Infrastructure Subcommittee update (Ben) Wayne had some comments around on-going saga to fix permissions on mailing list, and how to approach that. It is a WIP. 11. Intellectual Property Rights Subcommittee (Ben) Forum-036 Ballot - Adopt Invited Experts Policy has passed. Next meeting scheduled for next Tuesday to begin addressing remaining items. 12. Bylaws Changes (Ben) Ben planning to progress forum bylaws change ballot once summer is over e.g. September timeline. 13. Entrust Status in CABF (Bruce) Entrust does not, or soon will not issue TLS certificates anymore after key(s) transfer to Sectigo, however they are still doing some Code Sign certificates currently. The goal is that by 1st week of September, Sectigo will have control of all keys (including CS). So after that point, Entrust will not qualify under current membership category (Certificate Issuer), but may be looking to transition to Interested Party type member at that point. Bruce will provide update after actions are complete. Tim H indicated that the qualifying event is not necessary the key transfer but rather “trusted by Root Programs” criteria. Tim C indicated that Entrust is still a trusted CA for CS purposes, so in this instance it’s a voluntary withdrawal when it happens. Wayne lead the appreciation for all the effort contributions Bruce & Co have made to the CABF. 14. Any Other Business Registration for Warsaw is open – please indicate attendance for planning purposes. Note that Trusted Economy Forum is also being held adjacent to this meeting. List of future F2F meetings schedule was reviewed: 2025 1. Oct 15-17: Warsaw, Poland (Certum) – REGISTRATION OPEN 2026 2. Houston, TX, US Spring 2026 SSL.com New York, NY,US Summer 2026 Google Trust Services Thessaloniki, GR Fall 2026 HARICA 2027 5. Scottsdale, AZ Spring 2027 Sectigo Switzerland June 2027 SwissSign Austin, TX, USA Fall 2027 IdenTrust 2028 8. Shanghai, China Spring 2028 TrustAsia (tentative) 15. Adjourn Next call: July 31, 2025
2025-07-17 Minutes of the Server Certificate Working Group
July 17, 2025 by Wayne ThayerMeeting Title: CA/Browser Forum Server Certificate Working GroupDate: 17 July 2025 Meeting Ran By: Wayne Thayer Minutes Taken By: Scott Rea 1. Roll Call and Housekeeping Meeting called to order by Wayne Thayer.
July 17, 2025 by Wayne ThayerMeeting Title: CA/Browser Forum Server Certificate Working GroupDate: 17 July 2025 Meeting Ran By: Wayne Thayer Minutes Taken By: Scott Rea 1. Roll Call and Housekeeping Meeting called to order by Wayne Thayer.
2025-07-16 Minutes of the S/MIME Certificate Working Group
July 16, 2025 by Minutes of SMCWG July 16, 2025 These are the Minutes of the meeting described in the subject of this message. Corrections and clarifications where needed are encouraged by reply.
July 16, 2025 by Minutes of SMCWG July 16, 2025 These are the Minutes of the meeting described in the subject of this message. Corrections and clarifications where needed are encouraged by reply.
2025-07-10 Minutes of the Code Signing Certificate Working Group
July 10, 2025 by Code Signing Certificate Working Group Meeting Minutes – July 10th, 2025Note Well The Note Well was read.
July 10, 2025 by Code Signing Certificate Working Group Meeting Minutes – July 10th, 2025Note Well The Note Well was read.
Ballot FORUM-036 – Adopt Invited Experts Policy
July 9, 2025 by Ben WilsonBallot FORUM-036 – Adopt Invited Experts Policy The voting period for Forum-036 Adopt Invited Experts Policy has completed. The ballot has: PASSED
July 9, 2025 by Ben WilsonBallot FORUM-036 – Adopt Invited Experts Policy The voting period for Forum-036 Adopt Invited Experts Policy has completed. The ballot has: PASSED
2025-07-02 Minutes of the S/MIME Certificate Working Group
July 2, 2025 by Minutes of SMCWG July 2, 2025 These are the Minutes of the meeting described in the subject of this message. Corrections and clarifications where needed are encouraged by reply.
July 2, 2025 by Minutes of SMCWG July 2, 2025 These are the Minutes of the meeting described in the subject of this message. Corrections and clarifications where needed are encouraged by reply.
Ballot SMC013: Enable PQC Algorithms for S/MIME
July 2, 2025 by Stephen DavidsoonThe Intellectual Property Review (IPR) period for Ballot SMC013 (Enable PQC Algorithms for S/MIME) has completed. No IPR Exclusion Notices were filed, and the ballot is adopted as of August 22, 2025. The new S/MIME BR v.1.0.11 have been published to the CABF public website in accordance with the Bylaws: https://cabforum.org/uploads/CA-Browser-Forum-SMIMEBR-1.0.11.pdf IPR Review of Ballot SMC013: Enable PQC Algorithms for S/MIME This Review Notice is sent pursuant to Section 4.1 of the CA/Browser Forum’s Intellectual Property Rights Policy (v1.3). This Review Period of 30 days is for one Final Maintenance Guidelines. The complete Draft Maintenance Guideline that is the subject of this Review Notice is attached to this email, and may be found at: https://cabforum.org/uploads/CA-Browser-Forum-SMIMEBR-1.0.11-Redline.pdf
July 2, 2025 by Stephen DavidsoonThe Intellectual Property Review (IPR) period for Ballot SMC013 (Enable PQC Algorithms for S/MIME) has completed. No IPR Exclusion Notices were filed, and the ballot is adopted as of August 22, 2025. The new S/MIME BR v.1.0.11 have been published to the CABF public website in accordance with the Bylaws: https://cabforum.org/uploads/CA-Browser-Forum-SMIMEBR-1.0.11.pdf IPR Review of Ballot SMC013: Enable PQC Algorithms for S/MIME This Review Notice is sent pursuant to Section 4.1 of the CA/Browser Forum’s Intellectual Property Rights Policy (v1.3). This Review Period of 30 days is for one Final Maintenance Guidelines. The complete Draft Maintenance Guideline that is the subject of this Review Notice is attached to this email, and may be found at: https://cabforum.org/uploads/CA-Browser-Forum-SMIMEBR-1.0.11-Redline.pdf
2025-06-26 Minutes of the Code Signing Certificate Working Group
June 26, 2025 by Certificate Signing Certificate Working Group (CSCWG) – Meeting MinutesDate: June 26, 2025 Note Well The Note Well was read.
June 26, 2025 by Certificate Signing Certificate Working Group (CSCWG) – Meeting MinutesDate: June 26, 2025 Note Well The Note Well was read.
Ballot SC-085v2: Require Validation of DNSSEC (when present) for CAA and DCV Lookups
June 18, 2025 by Wayne ThayerVoting Results Certificate Issuers 25 votes in total:
June 18, 2025 by Wayne ThayerVoting Results Certificate Issuers 25 votes in total:
2025-06-12 Minutes of the Code Signing Certificate Working Group
June 12, 2025 by These are the Final Minutes of the CSCWG F2F Meeting as prepared by Brianca Martin. Martijn read the Antitrust statement. Adopted agenda as presented. Discussion topics Discussion Topic: Migration to a single profile Microsoft introduced this topic 1 year ago. Are there specific items that we want to bring to a single profile? Karina from Microsoft: Need to understand where the line is we want to draw. Goal is to keep them closer to EV, uplevel all code signing certificates to keep as much identify/information as we can. Suggestion from Martijn to go through section to indentify each section that needs to be removed. Karina suggested we have an offline discussion to review the fields. Martijn suggested to use GitHub. Send Karina an email if you want to participate in this discussion. Brianca asked what the end goal is or if there is a timeline driving this requirement. Karina - Goal is that every certificate is EV. Bruce from Entrust expressed that EV may not support all subscribers. May have to change the EV rules. Rather than having all EV characteristics they have the Org ID which provides third party information about the subscriber. Consider using another number in the Org ID Karina would like data to understand how many subscribers OV doesn’t work for and why. The average consumer should be able to see who signed the code. Bruce stated that the Non-EV side allows “”, EV does not. Consider eliminating OV for individuals. Document signing required face to face verification, code signing does not. Code signing certificates most to sign malware. Martijn shared a recent example about a reason to include face to face verification. Karina emphasized that she is open to carve outs. Corey shared a DV-style for code signing that may be useful for certificates without an organization. Martijn Corey shared that publicly trusted certificates use “”, we may be able to use that for code signing. Martijn will start a branch on GitHub to start the process. Discussion Topic: Reduction of maximum certificate validity *No updates from Microsoft
June 12, 2025 by These are the Final Minutes of the CSCWG F2F Meeting as prepared by Brianca Martin. Martijn read the Antitrust statement. Adopted agenda as presented. Discussion topics Discussion Topic: Migration to a single profile Microsoft introduced this topic 1 year ago. Are there specific items that we want to bring to a single profile? Karina from Microsoft: Need to understand where the line is we want to draw. Goal is to keep them closer to EV, uplevel all code signing certificates to keep as much identify/information as we can. Suggestion from Martijn to go through section to indentify each section that needs to be removed. Karina suggested we have an offline discussion to review the fields. Martijn suggested to use GitHub. Send Karina an email if you want to participate in this discussion. Brianca asked what the end goal is or if there is a timeline driving this requirement. Karina - Goal is that every certificate is EV. Bruce from Entrust expressed that EV may not support all subscribers. May have to change the EV rules. Rather than having all EV characteristics they have the Org ID which provides third party information about the subscriber. Consider using another number in the Org ID Karina would like data to understand how many subscribers OV doesn’t work for and why. The average consumer should be able to see who signed the code. Bruce stated that the Non-EV side allows “”, EV does not. Consider eliminating OV for individuals. Document signing required face to face verification, code signing does not. Code signing certificates most to sign malware. Martijn shared a recent example about a reason to include face to face verification. Karina emphasized that she is open to carve outs. Corey shared a DV-style for code signing that may be useful for certificates without an organization. Martijn Corey shared that publicly trusted certificates use “”, we may be able to use that for code signing. Martijn will start a branch on GitHub to start the process. Discussion Topic: Reduction of maximum certificate validity *No updates from Microsoft