<div dir="ltr"><div>This email from Miguel got held up in the mailer - <br></div><div><br>
</div><div>Meeting of 04-January-2022</div><div><br></div><div>Minute Taker - Miguel Sanchez<br></div><div><br></div><div>-Antitrust Statement ready by Clint Wilson</div><div><br></div><div>-Roll
Call: Adam Jones, Clint Wilson, Corey Rasmussen, Daniel Jefferey, David
Kluge, Kati Davids, Miguel Sanchez, Prachi Jain, Quan Nham<br><div><br></div><div>-Agenda Items:</div><div><ul><li>Catch up on Risk Assessment</li><li>Switching over to NetSec Working Group</li><li>NetSec Working Group</li><li>Comments on the ballot (Prachi) </li><li>Head’s up - will be starting discussion Period SC52 probably this Thursday </li></ul><div>-Risk Assessment</div></div><div><ul><li>Expecting carve out this week for it (Daniel Jeffery)</li><ul><li>No major strides </li><li>No major concerns. Still on everyone’s radar</li></ul><li>Dan sat down to review aspects with Ben Wilson (Mozilla) and Trev (AWS)</li><ul><li>Made progress and was helpful </li><li>If anyone wants to jump in on tomorrow’s (Wednesday’s) morning session ppl are more than welcome to </li><li>Might be better to wait until it comes into shape before sending out to everyone else</li></ul></ul><div>-NetSec Working Group</div></div><div><ul><li>Subcommittee
working as is until membership in WG gets completed - Subcommittee will
continue meeting probably one more time (hopefully last one) and then
transition to WG</li><li>To join Netsec WG</li><ul><li>Email <a href="mailto:questions@cabforum.org" target="_blank">questions@cabforum.org</a></li><li>Intention (company)</li><li>Certificate issuer or consumer</li><li>ID designated representatives (voting or not) </li></ul><li>Clint can’t for now but hoping to join before first actual meeting</li><li>Question from Prachi on whether we’ve decided on what to do with the Cloud NetSec Subcommittee? </li><ul><li>Haven’t
decided yet but imagine that Cloud and Threat Modeling might become
subcommittees but haven’t decided yet and will need to have a discussion
about this</li><li>Need to decide this in the Working Group </li><li>Probably will be some overlap - having official subcommittee might help flesh this out </li></ul></ul><div>-Comments on change (<a href="https://cabf.webex.com/cabf-en/url.php?frompanel=false&gourl=https%3A%2F%2Fgithub.com%2Fcabforum%2Fservercert%2Fpull%2F329" style="text-decoration-line:none" target="_blank"><span style="font-size:10.5pt;font-family:Arial;color:rgb(4,159,217);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">https://github.com/cabforum/servercert/pull/329</span></a>)</div></div><div><ul><li>Prachi is clarifying the Certificate Management system vs. PKI System </li><ul><li>Perhaps having Certificate Management system and Certificate system should encompass PKI system</li></ul><li>Anyone else have thoughts around this?</li><ul><li>Prachi will take a stab at writing definitions for PKI system and will post on the BR and take it from there </li><li>Though might add to the confusion but if overarching term to include all systems then it should be fine</li><li>Dan J: might require looking at the BRs and see where PKI System is being used </li><ul><li>Clint:
Not defined in the BRs and PKI System is only used once. It’s never
used in the NSR but we are concerned with how it’s being used in the BR
and NSRs</li><li>Clint: Original intent was to remove PKI System with
existing terms but need to ask CAs how they defined PKI system
internally before removing PKI system or defining that term to be
comprehensive</li><li>Dan J: agreed with Prachi on replacing undefined
term (PKI System) with defined term (Certificate Management System,
Certificate System, etc.) </li><li>Prachi to send a reminder </li></ul></ul><li>This discussion will remain with the Server Certificate Working group and will not move over to NetSec WG </li></ul></div><div>-Planning to meet as NetSec WG in the next couple of weeks. Still keeping Subcommittee meeting on the calendar for now</div><br>-Will meet again in two weeks as either subcommittee or WG</div>
</div>