<html 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:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Helvetica;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Please find below the notes from our September 18, 2025 meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Meeting Information<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Date: September 18, 2025<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Time: 8:02 AM PDT<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Working Group: Digital Credential Provider (DCP) Working Group<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Chair: Joseph Heenan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Note Taker: Jin Wen<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Attendees<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Klaus Roehrle (Sony)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Lukasz Jaromin (Raidiam)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Michael Jones<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Patrick Amrein<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Peter Sorotokin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Rajvardhan Deshmukh (Cisco)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Ryan Galluzzo (NIST)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Christian Bormann<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Steve Venema<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Jin Wen<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Joseph Heenan (Chair)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Hicham Lozi<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Brian Campbell<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- David Waite<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Daniel Fett<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Andy Lim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Bjorn Hjelm<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Administrative Items<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Reviewed OpenID Foundation Code of Conduct, Antitrust Policy, and IPR policy<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Reference document:
<a href="https://openid.net/wp-content/uploads/2025/06/OIDF_Groups-Activities-Events-Note-Well_Final_2025-06-12.pdf">
https://openid.net/wp-content/uploads/2025/06/OIDF_Groups-Activities-Events-Note-Well_Final_2025-06-12.pdf</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Key Announcements<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Major Milestone Achievement<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- VCI (Verifiable Credential Issuance) specification 1.0 final has been approved and published. This represents major progress, with announcements distributed and multiple LinkedIn posts
celebrating the achievement. The specification is now ready for reference in the next round of EC (European Commission) Implementing Acts for digital wallets.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Upcoming Events<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Pre-IIW DCP Working Group hybrid meeting:
<a href="https://dcpwg-iiw-20oct25.eventbrite.co.uk/">https://dcpwg-iiw-20oct25.eventbrite.co.uk/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- OIDF workshop:
<a href="https://oidf_workshop_iiw_fall2025.eventbrite.co.uk/">https://oidf_workshop_iiw_fall2025.eventbrite.co.uk/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Location: Both events will be held at Cisco with limited spaces<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- OIDF member discount: 20% discount codes for IIW were distributed by Stephanie last week<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Technical Discussion - HAIP Pull Requests<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">PR #252: Prohibit Self-Signed Certificates for x509_hash<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Link: <a href="https://github.com/openid/OpenID4VC-HAIP/pull/252">
https://github.com/openid/OpenID4VC-HAIP/pull/252</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Joseph Heenan reported on discussions with Stefan from New Zealand regarding their planned use of self-signed certificates due to the absence of a central registry. After extensive
discussion on the morning APAC call (including input from Tobias), Stefan approved the changes after recognizing alternative solutions that don't require self-signed certificates.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Steve Venema noted that Oliver addressed his comment regarding x5c header consistency across the specification, allowing him to approve the PR.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Status: Seven approvals received, open for three weeks, all comments addressed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Decision: Approved for merge.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">PR #266: Separate Schemes for VP/VCI, Make Custom URI Support Ecosystem Decision<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Link: <a href="https://github.com/openid/OpenID4VC-HAIP/pull/266">
https://github.com/openid/OpenID4VC-HAIP/pull/266</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Joseph Heenan explained the rationale for this significant change:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Separate HAIP-VCI and HAIP-VP schemes introduced instead of single scheme<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Custom scheme support changed from mandatory ("MUST") to optional ("MAY")<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Rationale: EU law will reference this specification with third-party test houses testing for compliance. Mandatory features that might not work reliably would be problematic<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Addition of explicit HTTPS claimed HTTPS URIs support as alternative invocation method<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Technical Details:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Different security properties between custom schemes and HTTPS URIs<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - IANA considerations section needs updating (action item for Joseph)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Charles suggested this resolves additional issues<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Status: Open for two days but topic discussed extensively.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Decision: Consensus to merge pending IANA section fix.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">PR #231: What Does High Assurance Mean?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Link: <a href="https://github.com/openid/OpenID4VC-HAIP/pull/231">
https://github.com/openid/OpenID4VC-HAIP/pull/231</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Joseph Heenan reported that Torsten updated the PR following Adrienne's comments, clarifying scope limitations and defining high assurance objectives:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - High assurance defined as: Claims are authentic and holder has been authenticated<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Explicitly states what is out of scope (exact authentication methods)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Non-normative but important for context setting<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Steve Venema volunteered to review and approve.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">PR #229: Clarify Batch Issuance Requirements<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Link: <a href="https://github.com/openid/OpenID4VC-HAIP/pull/229">
https://github.com/openid/OpenID4VC-HAIP/pull/229</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Discussion of language clarification around credentials and datasets. Oliver and Paul made suggestions that Kristina hasn't yet applied.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Proposed language: "If batch issuance is supported, the wallet should use it rather than making consecutive requests for a single credential of the same credential dataset. The issuer
must indicate whether batch issuance is supported by including or omitting the batch credential issuance metadata parameter. The issuer's decision may be influenced by various factors including but not limited to trust framework requirements, regulatory constraints,
applicable laws or internal policies."<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Decision: Consensus achieved. Action: Joseph to request Kristina apply the suggested changes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">PR #214: Require Use of (Most of) FAPI2 with VCI<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Link: <a href="https://github.com/openid/OpenID4VC-HAIP/pull/214">
https://github.com/openid/OpenID4VC-HAIP/pull/214</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Joseph Heenan presented this significant proposal requiring FAPI2 compliance for VCI implementations:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Use FAPI2 as recommended method to comply with OAuth Security BCP<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Constrain to DPoP as sender constraining mechanism (mTLS difficult for wallets)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Carve-out for client authentication (use wallet attestations instead)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Remove redundant PAR requirements (already covered by FAPI2)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Discussion Points:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Daniel Fett supported referencing FAPI2 rather than copying text to avoid complications.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Christian Bormann requested clarification notes for sections not applicable to VCI.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Brian Campbell raised concerns about mTLS guidance, strongly disagreeing with "throwing mTLS on everything" and requesting careful exclusions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Joseph Heenan acknowledged the need for notes excluding:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - OpenID Connect sections<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - mTLS deployment guidance<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Potential exception needed for JWT signing algorithms (ES256, RS256, EDDSA requirements)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Benefits Identified:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Reuse existing FAPI2 conformance tests<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Ensure security compliance<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Prevent insecure implementations in production<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Decision: Consensus to reference FAPI2 with appropriate exclusion notes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Open Issues Discussion<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Issue #211: Allow Use of Other Wallet Attestation Formats<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Link: <a href="https://github.com/openid/OpenID4VC-HAIP/issues/211">
https://github.com/openid/OpenID4VC-HAIP/issues/211</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Joseph Heenan noted ongoing discussion without clear resolution. The debate centers on:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Current approach: VCI wallet attestations provide interoperability<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Concern: Lower privacy and additional implementation burden<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Alternative: Support for hardware-specific attestations<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Status: Pending further discussion between Martin, Torsten, and others.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Issue #112: Consider Adding MTI (Mandatory to Implement) Crypto Suites<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Link: <a href="https://github.com/openid/OpenID4VC-HAIP/issues/112">
https://github.com/openid/OpenID4VC-HAIP/issues/112</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Critical Discussion on Cryptographic Requirements:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Ryan Galluzzo (NIST) provided crucial US regulatory context:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> > "I don't think we want to write anything that excludes existing mDL/mDOC deployments writ large. One thing to note, at least in the US, they need to use NIST approved algorithms
per the TSA Real ID waiver program. So, at least in the US, a smaller set is somewhat specified. This should be framed around the algorithms regardless of the credential type. This should be achievable if framing as a recommendation rather than a hard requirement."<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Key Technical Challenges Identified:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - ISO 18013-5 Permissiveness: Current standard allows wide range of algorithms<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Live Deployment Reality: Multiple jurisdictions (US states, Japan, others) have active mDL deployments<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Unknown Algorithm Usage: Limited visibility into actual cryptographic algorithms in production<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Conformance Testing: ISO 18013-5 conformance requires implementing all algorithms including Brainpool<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Christian Bormann proposed mandatory-to-implement approach focusing on wallet compatibility:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Wallets need MTI algorithms for generic credential acceptance<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Verifiers may have more specific requirements<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Recommendation: 1-2 MTI algorithms for interoperability<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- David Waite clarified standards landscape:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - No standardized way to use Brainpool with JOSE stack<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Different regulatory requirements across jurisdictions<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Hicham Lozi questioned algorithm restrictions by credential format, suggesting consistency across mDoc and SD-JWT.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Two Options Identified:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> 1) Restrictive approach: Exclude existing deployments that don't comply<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> 2) Permissive approach: Allow ISO 18013-5 defined algorithms with recommendations<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Decision: Issue requires further analysis. Action: Joseph to draft proposal incorporating discussion points.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Action Items<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">1) Joseph Heenan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Fix IANA considerations section in PR #266 and merge<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Add exclusion notes to FAPI2 PR for OpenID Connect and mTLS sections<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Contact Kristina to apply batch issuance language changes<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Draft crypto suites proposal incorporating meeting discussion<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">2) Steve Venema<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Review and approve PR #231 (What does high assurance mean?)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">3) Christian Bormann<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Create PR for signing request rationale (editorial)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">4) Oliver<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Arrange ISO small group meeting for intent to retain discussion (scheduled next week)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">5) All Members<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Continue reviewing open pull requests<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Provide input on Issue #112 (crypto suites) and Issue #211 (wallet attestations)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"> - Register for pre-IIW meeting and OIDF workshop<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Resources<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- HAIP GitHub Repository:
<a href="https://github.com/openid/OpenID4VC-HAIP/">https://github.com/openid/OpenID4VC-HAIP/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Pull Requests:
<a href="https://github.com/openid/OpenID4VC-HAIP/pulls">https://github.com/openid/OpenID4VC-HAIP/pulls</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Open Issues for 1.0:
<a href="https://github.com/openid/OpenID4VC-HAIP/issues?q=is%3Aissue+state%3Aopen+-label%3Aafter-wglc+-label%3Ahas-PR+-label%3Aready-for-PR+milestone%3A%221.0+Final%22">
https://github.com/openid/OpenID4VC-HAIP/issues?q=is%3Aissue+state%3Aopen+-label%3Aafter-wglc+-label%3Ahas-PR+-label%3Aready-for-PR+milestone%3A%221.0+Final%22</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">Next Meeting<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:Helvetica">- Next regular DCP Working Group meeting scheduled according to standard cadence. Many attendees expected to participate in Tuesday Americas call.<o:p></o:p></span></p>
</div>
</body>
</html>