<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;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.gmailsignatureprefix
{mso-style-name:gmail_signature_prefix;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">I suggest that we start the new call schedule the week of December 16<sup>th</sup>. This would drop the Monday, December 16<sup>th</sup> 3pm call and add a Thursday, December 19<sup>th</sup> 7am call (all
times Pacific).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Thanks Nat,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Openid-specs-ab <openid-specs-ab-bounces@lists.openid.net>
<b>On Behalf Of </b>Nat Sakimura via Openid-specs-ab<br>
<b>Sent:</b> Monday, December 2, 2024 4:49 PM<br>
<b>To:</b> openid-specs-ab@lists.openid.net Ab <openid-specs-ab@lists.openid.net><br>
<b>Cc:</b> Nat Sakimura <sakimura@gmail.com><br>
<b>Subject:</b> [Openid-specs-ab] OpenID Connect Working Group Meeting Notes (2024-12-02)<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"># OpenID Connect Working Group Meeting Notes<br>
<br>
**Date:** 2024-12-02 15:00<br>
<br>
## Attendees<br>
- Michael Jones<br>
- Nat Sakimura<br>
- Brian Campbell<br>
- Tom Jones<br>
- Adam Bradley (Mastercard)<br>
<br>
## Key Discussion Points<br>
<br>
### 1. Introduction of New Participant<br>
- Adam Bradley from Mastercard introduced himself<br>
- Expressed interest in payments standards convergence, particularly around FAPI and VCs<br>
- Looking to increase Mastercard's participation in standards development<br>
- Currently involved with Open Banking, FIDO, and W3C<br>
<br>
### 2. FAPI and Payments Standards Discussion<br>
- Nat explained that FAPI focuses on security aspects of APIs, not specific to banking<br>
- Brian Campbell noted:<br>
- Transaction data functionality is currently a basic placeholder<br>
- FAPI may not be ideal for individual payments despite regulatory requirements<br>
- Limited convergence between different payment standards currently<br>
- Noted ongoing work in browser space regarding transaction data and verifiable presentations<br>
<br>
### 3. Related Payment Standards Work<br>
- W3C Web Payments working group developing Secure Payment Confirmation extension to WebAuthn<br>
- DCP working group has transaction confirmation capabilities<br>
- Limited direct involvement from Connect working group in payment specifications<br>
<br>
### 4. Meeting Schedule Changes<br>
- Proposal to change meeting frequency:<br>
- Make Atlantic-friendly call (Thursday 7 AM PT) weekly<br>
- Reduce Pacific-friendly call to every other week<br>
- Change proposed to accommodate European participants working on Federation<br>
- General agreement from attendees, though some noted they may not attend 7 AM calls regularly<br>
- Suggestion to publish agendas in advance<br>
<br>
### 5. Federation Wallet Issues<br>
- Reviewed several GitHub issues: (<a href="https://github.com/openid/federation-wallet/issues/">https://github.com/openid/federation-wallet/issues/</a>)<br>
- Issue #22: Discussion of metadata parameters and DCP working group coordination<br>
- Issue #20: Related to ephemeral parameters (tabled for further clarification)<br>
- Issue #44: New issue regarding wallet discovery of federation support<br>
- Discussion of how wallets can discover if an OpenID4VCI issuer uses federation<br>
- Suggestion to use well-known endpoint discovery approach<br>
<br>
### 6. Federation Status<br>
- Multiple pull requests pending<br>
- New draft with fixes expected soon<br>
<br>
## Action Items<br>
1. Begin transitioning to new meeting schedule (Atlantic weekly, Pacific bi-weekly)<br>
2. Review Federation wallet issues, particularly #22<br>
3. Implement agenda publishing for future meetings<br>
<br>
**Next Meeting:** TBD based on new schedule<br>
<br>
*Note: All times mentioned are in Pacific Time (PT)*<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span class="gmailsignatureprefix">-- </span><o:p></o:p></p>
<div>
<p class="MsoNormal">Nat Sakimura (=nat)<o:p></o:p></p>
<div>
<p class="MsoNormal">Chairman, OpenID Foundation<br>
<a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>