<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:291516714;
mso-list-type:hybrid;
mso-list-template-ids:-521622224 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Apologies…with attachment.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Jordan, Marie <br>
<b>Sent:</b> Thursday, June 29, 2023 1:06 PM<br>
<b>To:</b> board@openid.net<br>
<b>Subject:</b> May 4, 2023 Executive Committee Call Minutes<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>May 4, 2023 Executive Committee Call Minutes<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Present:<o:p></o:p></b></p>
<p class="MsoNormal">Gail Hodges – Executive Director<o:p></o:p></p>
<p class="MsoNormal">Don Thibeau – Non-Executive Director<o:p></o:p></p>
<p class="MsoNormal">Mike Jones – Non-Executive Director<o:p></o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">Bjorn Hjelm<o:p></o:p></p>
<p class="MsoNormal">George Fletcher<o:p></o:p></p>
<p class="MsoNormal">Nancy Cam-Winget<o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Absent:<o:p></o:p></b></p>
<p class="MsoNormal">(The Secretary position is currently vacant)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Visitors:<o:p></o:p></b></p>
<p class="MsoNormal">Mike Leszcz<o:p></o:p></p>
<p class="MsoNormal">Mark Haine<o:p></o:p></p>
<p class="MsoNormal">John Bradley<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.25in;mso-add-space:auto;text-indent:-.25in;line-height:normal;mso-list:l0 level1 lfo2">
<![if !supportLists]><b><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></b><![endif]><b>New News<o:p></o:p></b></p>
<p class="MsoNormal">Two board members have expressed interest in the Secretary position. Dima Postnikov and Marie Jordan have expressed initial interest and still be to confirmed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The services agreement for Mike Jones was approved and he is now on board.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Gail has briefed the White House three times in the last month regarding open data/open finance/identity. Shared the CFPB brief and there has been interest in recent OIDF whitepapers.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OpenID4VP test development started this week. Joseph started work this week after consulting with the special topic team. This work will continue at EIC in Berlin next week.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">NIST NCCoE reference application work on mDL. Call scheduled to discuss how OIDF can support NIST in this work to develop reference apps that will use OIDC4VP.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are working on a liaison with the EC and there will be a meeting in Berlin during EIC. OIDF has also been invited to a number of EUDI workshops starting on Friday, May 5, 2023 in Berlin.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Bjorn is talking with the Linux Foundation CAMARA Project. The CAMARA Project is developing APIs for telcos that are using OpenID Connect including CIBA as a baseline for these APIs.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We will be talking with FDX later this month about possible points of coordination. We will tell them about our new approaches to supporting ecosystems.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">FDX meeting scheduled for May 18, 2023 as a follow-up to Joseph’s conversations at the recent FDX Summit. Revisit how we may how we make work together.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Strategic Task Force will be meeting with HL7 at the next meeting on Thursday, May 18, 2023. HL7 are using GNAP and have been testing interoperability.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">AWS has requested a brief on overall OIDF work with a focused session on Shared Signals which is schedule for June 2023.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.25in;mso-add-space:auto;text-indent:-.25in;line-height:normal;mso-list:l0 level1 lfo2">
<![if !supportLists]><b><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></b><![endif]><b>Block<o:p></o:p></b></p>
<p class="MsoNormal">Block plans to join working groups and to join as a Corporate member. Mark Haine is contracted to help Block evaluate using OpenID Connect for Identity Assurance claims in Verifiable Credentials.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Nat commented, not regarding Block, that we may want to introduce OIDF to the BGIN community at their Plenary in November 2023.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.25in;mso-add-space:auto;text-indent:-.25in;line-height:normal;mso-list:l0 level1 lfo2">
<![if !supportLists]><b><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></b><![endif]><b>OIDF Whitepapers<o:p></o:p></b></p>
<p class="MsoNormal">We published the final version of the Government Issued Identity Credentials & Privacy Landscape paper. Seven organizations signed on as authors. Gail noted that there has been strong interest in this paper.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Government & Identity is on track to publish in mid-May with 5 days for public comment.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are targeting publishing a refreshed version of the GAIN whitepaper on or before May 12, 2023.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The board will review the IoT whitepaper on Monday, May 8, 2023 in Berlin.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.25in;mso-add-space:auto;text-indent:-.25in;line-height:normal;mso-list:l0 level1 lfo2">
<![if !supportLists]><b><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></b><![endif]><b>Refreshed OpenID Website<o:p></o:p></b></p>
<p class="MsoNormal">The review site is at <a href="https://openid.d-f.cc/">https://openid.d-f.cc/</a>. We are focused first on the WordPress site with approximately 85% of content completed. We plan to launch the WordPress site by Identiverse. The Ruby on
Rails membership portal is also being updated (reskinned to be consistent with updated WP site) but will launch sometime after Identiverse. Mike Leszcz has sent the board a link and request for feedback.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">During this update, there was side conversation about assisting the Special Topic group to go through the working group creation process. Nat commented it’s a fairly simple process to get started including drafting a charter and sending
to the Specifications Council for review. He noted that there are logistical tasks to be accomplished once approved. Mike Leszcz commented that it’s well defined in the Process Document that he shared with Torsten and Kristina and offered to support their
efforts. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mike Jones went on to comment that specs should only be transitioned from working group to another once they’ve reached Implementers Drafts because at that point their IP are clean and you could have a different set of committers in the
new working group. Mike note that’s fine for the existing 3 specs because they’re on track as Implementers Drafts but the newer ones (user info & BT low energy) you could abandon and resubmit. John Bradley noted that we don't actually have any criteria for
what an Implementers Draft has to be so they could actually do an early Implementer's Draft and then move it as one of the options.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.25in;mso-add-space:auto;text-indent:-.25in;line-height:normal;mso-list:l0 level1 lfo2">
<![if !supportLists]><b><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></b><![endif]><b>ConnectID Pilot Ask About Bundled Certification<o:p></o:p></b></p>
<p class="MsoNormal">ConnectID wants to do mandatory certification for OPs and RPs in Australia. There are four relevant OP certification profiles and three relevant RP certification profiles. They want the OP bundle to be $5,000 for non-members and $1,000
for members. They want the RP bundle to be $1,000. ConnectID wants the RP price to be low to promote adoption. ConnectID has contributed substantial designated funds towards FAPI2 conformance test development. Mike Jones pointed out that we do bundle prices
for OpenID Connect OPs and RPs per <a href="https://openid.net/certification/fees/">
https://openid.net/certification/fees/</a>. Gail then walked the EC through a couple of revenue models based on ConnectID’s ask (detailed in attached meeting deck).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mike Jones noted that ConnectID is asking to pay the same as FAPI for FAPI plus additional things that we would otherwise separately charge for. He would be more comfortable asking for a bundled price that is higher than the $5K FAPI cert
fee. Nancy agrees to charging something more for multiples than for just FAPI. Nancy noted that the proposed additive requires some additive effort on our side. Gail then walked through a model whereby the ConnectID ecosystem would pay $4K for 1-4 specs in
bundle.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Gail shared that we did create special FAPI recertification pricing for Open Banking Brazil. CAP joined the board and mandated FAPI OP recertifications at $2K for non-members.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">George Fletcher asked about a volume discount. He suggested we could structure it as a volume discount based on quantity of a certification type. George noted that this could be a generic enough model that could be offered to other ecosystems.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Gail will revisit the pricing conversation with Dima/ConnectID at EIC next week in Berlin. She will share the EC’s feedback and discuss two options: Board seat at $50K + $2K/each non-member cert fee and the $4K bundled model.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
<p class="MsoNormal">Marie Jordan<o:p></o:p></p>
<p class="MsoNormal">Secretary, OIDF<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>