<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div dir="ltr"></div>
<div dir="ltr">Hello all</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">We are up to 69% passing on the interop results, but very few teams had time to triage issues since 7/16. We extending the pairwise testing through Monday to see if more teams can find the time to rerun their tests. </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Gail </div>
<div dir="ltr"><br>
<blockquote type="cite">On Jul 16, 2025, at 4:42 PM, Gail Hodges via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols@lists.openid.net> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>@font-face { font-family: Wingdings; }
@font-face { font-family: "Cambria Math"; }
@font-face { font-family: Aptos; }
@font-face { font-family: "Times New Roman (Body CS)"; }
@font-face { font-family: "Helvetica Neue"; }
@font-face { font-family: Menlo; }
p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in; font-size: 12pt; font-family: Aptos, sans-serif; }
a:link, span.MsoHyperlink { color: rgb(70, 120, 134); text-decoration: underline; }
span.EmailStyle17 { font-family: Aptos, sans-serif; color: windowtext; font-weight: normal; font-style: normal; }
p.p1, li.p1, div.p1 { margin: 0in; font-size: 10pt; font-family: "Helvetica Neue"; }
p.p2, li.p2, div.p2 { margin: 0in; font-size: 10pt; font-family: "Helvetica Neue"; }
p.li2, li.li2, div.li2 { margin: 0in; font-size: 10pt; font-family: "Helvetica Neue"; }
span.apple-converted-space { }
.MsoChpDefault { }
@page WordSection1 { size: 8.5in 11in; margin: 1in; }
div.WordSection1 { page: WordSection1; }
ol { margin-bottom: 0in; }
ul { margin-bottom: 0in; }</style>
<div class="WordSection1">
<p class="p2">DCP WG <o:p></o:p></p>
<p class="p1"><o:p> </o:p></p>
<p class="p2">We are pleased to share the preliminary results and report for the OpenID4VCI Interop #3, today July 16th, 2025 from 8-945am PT.
<span class="apple-converted-space"> </span><o:p></o:p></p>
<p class="p1"><o:p> </o:p></p>
<p class="p1"><b><u>Preliminary Results <o:p></o:p></u></b></p>
<p class="p2">Of the 39 pairs tested today:<span class="apple-converted-space"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="li2" style="color:#4EA72E;mso-list:l5 level1 lfo1"><b>67% (26 pairs) had a passing result!<span class="apple-converted-space"> </span><o:p></o:p></b></li><li class="li2" style="color:#FFC000;mso-list:l5 level1 lfo1"><b>31% (12 pairs) had a Fail, but with a resolvable issue by the implementers<o:p></o:p></b></li><li class="li2" style="mso-list:l5 level1 lfo1">3% (1 pair) had a Fail with an unknown issue
<span class="apple-converted-space"> </span><o:p></o:p></li></ul>
<p class="p1"><o:p> </o:p></p>
<p class="p1">So far—strong results! <o:p></o:p></p>
<p class="p1"><o:p> </o:p></p>
<p class="p1">Below is a Preliminary Report of the pairwise configurations, participants, and some early insights prior to release of the final results Friday. The data will change as the teams conduct some triage and pairwise asynch tests. This may also surface
issues not identified in today’s session. <o:p></o:p></p>
<p class="p1"><o:p> </o:p></p>
<p class="p1">Fantastic work yet again by:<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="p1" style="mso-list:l4 level1 lfo9">Our many expert implementing teams!
<o:p></o:p></li><li class="p1" style="mso-list:l4 level1 lfo9">By Thomas who led on the OpenID4VCI test suite development<o:p></o:p></li><li class="p1" style="mso-list:l4 level1 lfo9">By Joseph, supporting Thomas behind the scenes and adding to some of the tests himself<o:p></o:p></li><li class="p1" style="mso-list:l4 level1 lfo9">By Gareth, hosting the interop and coordinating with the teams in advance.
<o:p></o:p></li><li class="p1" style="mso-list:l4 level1 lfo9">And of course, the WG itself, whose v16 of the spec is looking good (so far!) as this spec move towards final
<o:p></o:p></li></ul>
<p class="p1"><o:p> </o:p></p>
<p class="p1">Any questions, please let me, Thomas, Joseph and Gareth know.<o:p></o:p></p>
<p class="p1"><o:p> </o:p></p>
<p class="p1">Gail <o:p></o:p></p>
<p class="p1"><o:p> </o:p></p>
<p class="p1"><b><u>Preliminary Report <o:p></o:p></u></b></p>
<p class="p1"><o:p> </o:p></p>
<p class="p1">Participants included a robust group of implementers: <o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="p1" style="mso-list:l0 level1 lfo8">7 issuers: Bundesdruckerei GmbH, Fikua, Multipaz/Open Wallet Foundation, Mattr, Meeco, the OIDF test suite, and one additional issuer without permission to use their name<o:p></o:p></li><li class="p1" style="mso-list:l0 level1 lfo8">6 wallets: Bundesdruckerei GmbH, Multipaz/Open Wallet Foundation, Meeco, MyMahi, and the OIDF test suite<o:p></o:p></li><li class="p1" style="mso-list:l0 level1 lfo8">1 demonstrator: Credman wallet (for DC API, future configuration)<o:p></o:p></li></ul>
<p class="p1"><o:p> </o:p></p>
<p class="p2">The pairwise results are based on several configurations of the OpenID4VCI spec as shown below:<span class="apple-converted-space"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="li2" style="mso-list:l8 level1 lfo2">5 pairs tested with OpenID4VCI v16 + SD-JWT + Custom URI Initiated+ HAIP mode where HAIP mode = "wallet attestation-based client authentication (with x5c header)”<o:p></o:p></li><li class="li2" style="mso-list:l8 level1 lfo2">20 pairs tested with OpenID4VCI v16 + SD-JWT + Custom URI Initiated + client assertion with private_key_jwt<span class="apple-converted-space"> </span><o:p></o:p></li><li class="li2" style="mso-list:l8 level1 lfo2">7 pairs tested with OpenID4VCI v16+ SD JWT+ Custom URI initiated + No client attestation<o:p></o:p></li><li class="li2" style="mso-list:l8 level1 lfo2">7 pairs tested with OpenID4VCI v16+ mdoc+ Custom URI initiated + No client attestation<o:p></o:p></li></ul>
<p class="p1"><o:p> </o:p></p>
<p class="p2">Between now and 12pm PT Friday, we expect the teams to continue triaging<span class="apple-converted-space"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="li2" style="mso-list:l3 level1 lfo3">12 pairs that failed with resolvable issues.
<span class="apple-converted-space"> </span><o:p></o:p></li><li class="li2" style="mso-list:l3 level1 lfo3">16 net-new pairs, pairs that were not tested today, but which should be possible for the teams to test offline with light effort (e.g. exchange of configuration information, or testing in timezones not friendly
to some teams today)<o:p></o:p></li><li class="li2" style="mso-list:l3 level1 lfo3"><a href="https://oidf.slack.com/team/U07NKSVNY7R">@Gareth Narinesingh</a> will email the interop team leads to gather as many updated/new results as possible <o:p></o:p></li></ul>
<p class="li2"><b>By end of day Friday, Gail will circulate the final results to the DCP WG.
<o:p></o:p></b></p>
<p class="p1"><o:p> </o:p></p>
<p class="p2">Based on these highly preliminary findings:<span class="apple-converted-space"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="li2" style="mso-list:l7 level1 lfo4"><b><span style="color:#4EA72E">No material, new issues with the OpenID4VCI v16 spec flagged;</span></b> nothing obvious that would merit escalation as part of the public review of v16 now underway.<span class="apple-converted-space"> </span><o:p></o:p></li><li class="li2" style="mso-list:l7 level1 lfo4"><b><span style="color:#4EA72E">No material issues with the OpenID4VCI tests raised</span></b>. Tests “as is” are already adding value for implementers. Enhancements to tests are of interest and could further support
implementers (mdoc credential type added to the test suite, proving out the DC API initiation test option, adding tests for optional features)<o:p></o:p></li></ul>
<p class="p1"><o:p> </o:p></p>
<p class="p2">Initial observations from the group :<span class="apple-converted-space"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="li2" style="mso-list:l9 level1 lfo5">The broad range of configuration options within the OpenID4VCI spec underscores the importance of profiling of the spec.<span class="apple-converted-space"> </span><o:p></o:p></li><ul style="margin-top:0in" type="circle">
<li class="li2" style="mso-list:l9 level2 lfo5">This is a challenge which HAIP seeks to address by default.<span class="apple-converted-space"> </span><o:p></o:p></li><li class="li2" style="mso-list:l9 level2 lfo5">Some of the implementers had not enabled HAIP yet.<o:p></o:p></li></ul>
<li class="li2" style="mso-list:l9 level1 lfo5">Although the pairs with results recorded all had Custom URI initiation, the interop participants discussed the potential for DC API to initiative the transaction, which could come in OpenID4VCI V1.1 of the specification.<span class="apple-converted-space"> </span><o:p></o:p></li><ul style="margin-top:0in" type="circle">
<li class="li2" style="mso-list:l9 level2 lfo5">The Credman team briefly demonstrated their implementation using the DC API to initiate the transaction<o:p></o:p></li><li class="li2" style="mso-list:l9 level2 lfo5">The OIDF certification team confirmed that the test suite now allows for DC API initiated transactions. We hope to have the first implementers passing those tests shortly.<o:p></o:p></li></ul>
<li class="li2" style="mso-list:l9 level1 lfo5">There did not seem to be a material need for a 4th interop for the purpose of proving out the specs, or the OID4VCI test suite.
<o:p></o:p></li><ul style="margin-top:0in" type="circle">
<li class="li2" style="mso-list:l9 level2 lfo5">That said, ad hoc implementer pairwise tests or a future interop may be desirable to bring additional implementers along, refine new tests in the test suite etc.<o:p></o:p></li></ul>
</ul>
<p class="p1"><o:p> </o:p></p>
<p class="p2">Requests for the <b>DCP WG/ Cochairs, after release of the final results
</b>:<span class="apple-converted-space"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="li2" style="mso-list:l2 level1 lfo6">Acknowledge OpenID4VCI v16 final interop results<span class="apple-converted-space"> </span><o:p></o:p></li><li class="li2" style="mso-list:l2 level1 lfo6">Share final results with ISO WG10, WG4 to inform their spec development<span class="apple-converted-space"> </span><o:p></o:p></li><li class="li2" style="mso-list:l2 level1 lfo6">WG triage of issues/PRs raised <span class="apple-converted-space">
</span><o:p></o:p></li><li class="li2" style="mso-list:l2 level1 lfo6">WG feedback on test requirements for handling optional UX requirements in the specifications<span class="apple-converted-space"> </span><o:p></o:p></li><ul style="margin-top:0in" type="circle">
<ul style="margin-top:0in" type="circle">
<li class="li2" style="mso-list:l2 level3 lfo6">these optional requirements could be ignored in the tests (as they are now since they are not required)<o:p></o:p></li><li class="li2" style="mso-list:l2 level3 lfo6">we can add tests to check for optional features, but if we do, we need WG guidance on how to handle optional tests that do not pass (e.g. flag an optional test that does not pass, but overall implementation passes?
Or a failure on an optional test is a failure overall?) There are some governance decisions to consider in this, e.g. UX failures the spec sought to address.<o:p></o:p></li></ul>
</ul>
</ol>
<p class="p2">5. Suggestion for the DCP WG to maintain a reference sheet for ad hoc pairwise testing with restricted access.<span class="apple-converted-space"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="p2" style="mso-list:l6 level1 lfo11">lists of implementers, their configurations (issuer, verifier, wallet, etc), credential types, security configurations etc.<span class="apple-converted-space"> <o:p></o:p></span></li><li class="p2" style="mso-list:l6 level1 lfo11">list of their certificates, endpoints, registration requirements<o:p></o:p></li><li class="p2" style="mso-list:l6 level1 lfo11">contact information (part of reason restricted access is suitable)<o:p></o:p></li><li class="li2" style="mso-list:l6 level1 lfo11">If this turns into a more complex exercise, DCP Cochairs and OIDF staff may want to explore alternatives to maintain this permissioned repository<o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
</div>
<span>-- </span><br>
<span>Openid-specs-digital-credentials-protocols mailing list</span><br>
<span>Openid-specs-digital-credentials-protocols@lists.openid.net</span><br>
<span>https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols</span><br>
</div>
</blockquote>
</body>
</html>