<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
These are the Final Minutes of the Teleconference described in the
subject of this message.<b><br>
</b>
<div class="moz-text-html" lang="x-western">
<div class="WordSection1">
<h2><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">Attendees (in
alphabetical order)</span></h2>
<p class="MsoNormal">Adam Clark (Visa), Andrea Holland
(SecureTrust), Arno Fiedler (D-TRUST), Ben Wilson (Mozilla),
Bruce Morton (Entrust Datacard), Chris McMillan (Visa), Clint
Wilson (Apple), Corey Bonnell (SecureTrust), Chris Kemmerer
(SSL.com), Curt Spann (Apple), Dean Coclin (Digicert),
Dimitris Zacharopoulos (HARICA), Doug Beattie (GlobalSign),
Dre Aremeda (GoDaddy), Dustin Hollenback (Microsoft), Enrico
Entschew (D-TRUST), Inaba Atsushi (GlobalSign), Janet Hines
(SecureTrust), Jeff Ward (CPA Canada/WebTrust), Jos Purvis
(Cisco Systems), Karina Sirota (Microsoft), Mads Henriksveen
(Buypass AS), Mayur Manchanda (Visa), Michelle Coon (OATI),
Mike Reilly (Microsoft), Niko Carpenter (SecureTrust), Patrick
Nohe (GlobalSign), Pedro Fuentes (OISTE Foundation), Peter
Miskovic (Disig), Rachel McPherson (TrustCor Systems), Rich
Smith (Sectigo), Robin Alden (Sectigo), Ryan Sleevi (Google),
Stephen Davidson (Digicert), Tim Hollebeek (Digicert), Tobias
Josefowitz (Opera Software AS), Wayne Thayer (Mozilla).<span
style="mso-ansi-language:EN-US"><span style="color:black"></span></span><span
style="font-size:12.0pt;mso-ansi-language:EN-US"></span></p>
<h2><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">Minutes </span></h2>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">1. Roll Call</span></h3>
<p class="MsoNormal"><span style="mso-ansi-language:EN-US">The
Chair took attendance. </span></p>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">2. Read Antitrust
Statement</span></h3>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="mso-ansi-language:EN-US">The Antitrust Statement was
read. </span></p>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">3. Review Agenda,
Assign Minute Taker</span></h3>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="mso-ansi-language:EN-US">Tobi volunteered to take the
minutes for July 23rd. No changes to the agenda were noted.<br>
</span></p>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">4. Approval of minutes
from previous teleconference</span></h3>
<p class="MsoNormal"><span style="mso-ansi-language:EN-US">The
minutes were already approved.<br>
</span></p>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">5. Forum
Infrastructure Subcommittee update</span></h3>
<ul>
<li>Excellent meeting on 1 July. </li>
<li>Starting to look at the migration of the mailers. Making
sure timing will not impact ballot voting</li>
<li>Had discussions about email reminders. Looking at IETF
model for how to think about improvements</li>
<li>Take a look at GitHub projects vs. Cello capabilities for
feedback. Ideally we have all the work being done in one
place for 1) familiarity of tools and 2) ease of sharing
between committees and subgroups</li>
<li>Looking at tools for auto publishing</li>
<li>Call out for any other documents we need to produce the
same way with the same tool sets etc.</li>
<li>Next steps will be draft ballots as a result of any of
these plans</li>
<li>There is a spirited discussion on the public list on
listserv password reminder mails. We decided to post info
on the Wiki that will tell folks how to reset passwords. We
will also turn off the reminders and see if there is any
problem form users with not receiving these reminders</li>
<li>Looking to how to solve the redline problem. Looking at
solutions to support pull requests</li>
<li>Ryan 3647 template is out there in GitHub. Tim: thanks
for everyone for getting this template out there. Should we
have separate sections to make it clear as to which docs
have been adopted by ballots and which have not. E.g. a
section with official docs and another with “helpful”
docs. Dimitris also thanked everyone involved in this work
and all the time it will save folks</li>
<li>Dean: Josh, are you able to put changed names on the
mailing list? Josh: He believe he did. He will go back
through his emails to double check for GoDaddy, SecureTrust
and other changes that came int</li>
<li>Dimitris: I believe all archives are public/open except
for the management list. FYI anyone can use “forgot
password” and get their password back</li>
</ul>
<span lang="DE"><a
href="https://lists.cabforum.org/pipermail/infrastructure/2020-May/000240.html"
moz-do-not-send="true"><span style="mso-ansi-language:EN-US"
lang="EN-US"></span></a></span><span
style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language:EN-US"></span>
<ul type="disc">
</ul>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">6. Code Signing
Working Group update</span></h3>
<ul>
<li>Had a meeting out of cycle on 7 July. Most of the meeting
was going through the combined document and cleaning up a
few minor issues that were still a bit confusing. These
will move to the parking lot list for future ballots</li>
<li>Discussion period for the ballot started this morning (9
July)</li>
<li>Another version of the document will be updating the
format</li>
<li>Ultimately, we’ll have a single document that combines CS
and EV CS requirements</li>
</ul>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">7. S/MIME Working
Group update</span></h3>
<ul>
<li>Stephen: public list post announced passing of the
charter and call for membership. Any questions can be sent
in reply or to Steven directly</li>
<li>In order to bootstrap we’ll have a period of soliciting
interest. 22 July at 11am EDT will be the first meeting.
On agenda will be to review the list of startup members and
to vote on it. We’ll need 2/3rds of members to vote for it
to pass. The email sent out on the list has details on how
to declare interest. Certificate Consumer member
definitions are included in these communications as is the
definition of a Certificate issuer member and interested
party member.</li>
<li>Some have sent in declaration of interest. However, we
have some companies that may be interested but are not
aware. Ask of CAs and Certificate Consumers to spread the
word on the WG and to encourage membership</li>
<li>First meeting will discuss goals of the group and next
steps. Many elements of this WG will need to coordinate and
leverage work form other WGs e.g. validation and the like</li>
<li>Dimitris pointed out that with the recent bylaw changes
that new members must declare their official voting
representatives. Steven will make sure to clarify this
requirement. </li>
<li>Double check that there is a way to bootstrap the WG email
list and potential members are not going to the wrong lists
for information or responses</li>
<li>Thanks to the infrastructure group for all the help in
getting this WG set up for a success start!</li>
</ul>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">8. </span><span
style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">Approval of minutes
from F2F 50 </span></h3>
Minutes were approved<span style="mso-ansi-language:EN-US">.</span><br>
<br>
<h3
style="margin-top:1.0pt;margin-right:0cm;margin-bottom:1.0pt;margin-left:0cm"><span
style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">9. </span>Decide
about having F2F 51 virtual or not</h3>
Doug: Given the COVID-19 situation we recommend that we cancel
the f2f portion and go to full virtual meeting. Decision was
made to make this a virtual meeting.<br>
<br>
<h3
style="margin-top:1.0pt;margin-right:0cm;margin-bottom:1.0pt;margin-left:0cm"><span
style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">10. Any Other Business</span></h3>
None<br>
<br>
<h3
style="margin-top:1.0pt;margin-right:0cm;margin-bottom:1.0pt;margin-left:0cm"><span
style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">11. Next call</span></h3>
<p class="MsoNormal"><span style="mso-ansi-language:EN-US">The
next call will take place on July 23, 2020 at 11:30am
Eastern Time.</span></p>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">Adjourned</span></h3>
<h3><span style="mso-fareast-font-family:"Times New
Roman";mso-ansi-language: EN-US">F2F Meeting Schedule:
</span></h3>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo3;tab-stops:list 36.0pt"><span
style="mso-fareast-font-family: "Times New
Roman";mso-ansi-language:EN-US">2020: October 20-22
(Virtual)</span></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo3;tab-stops:list 36.0pt"><span
style="mso-fareast-font-family: "Times New
Roman";mso-ansi-language:EN-US">2021: Feb-March San
Jose, CA (Cisco), June – Poland (Asseco-Certum), October -
Minneapolis (OATI) </span></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo3;tab-stops:list 36.0pt"><span
style="mso-fareast-font-family: "Times New
Roman";mso-ansi-language:EN-US">2022: </span>Mar-April
New Delhi / Bengaluru (e-Mudhra), June - <font
color="#ff0000">[Open]</font>, October - <font
color="#ff0000">[Open]</font></li>
</ul>
</div>
</div>
</body>
</html>