<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=Windows-1252">
<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:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="en-BE" link="blue" vlink="purple" style="word-wrap:break-word;line-break:after-white-space">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US">Hi Joseph and other members,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US">Regarding
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US">></span><span lang="EN-US">
</span>Two people asked about how to return multiple credentials fulfilling the same single requirement; that hadn’t come up before and we probably need a way to express if the verifier wants all the matches or just one - new issue to be opened for that.<span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I just want to qualify my question further.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I was thinking more of the case where a single presentation is answering multiple credentials requests.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Specifically W3C VCDM enables presentation of multiple credentials, bound to the same identifier, in a single presentation object. In contrast, to my knowledge, SD-JWT VC does not have
this.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">For the example, let’s conceptually represent this as jwt_vp_json_a = [jwt_vc_json_1, jwt_vc_json_2], where jwt_vc_json_1 answers my_cred_1 and jwt_vc_json_2 answers my_cred_2.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Does the solution envisaged then repeat the presentation object and figure out in the submission how to reference the correct credential<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">{<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"> “my_cred_1”: “jwt_vp_json_a”,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"> “my_cred_2”: “jwt_vp_json_a”<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">}<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Or, do we require multiple presentation object, each one replying to exactly one of the request<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">jwt_vp_json_b = [jwt_vc_json_1]<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">jwt_vp_json_c = [jwt_vc_json_2]<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">{<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"> “my_cred_1”: “jwt_vp_json_b”,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"> “my_cred_2”: “jwt_vp_json_c”<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">}<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Or, do we allow more flexibility, but increasing complexity in response structure.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">[<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"> {<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"> “request”: [“my_cred_1”, “my_cred_1”],<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"> “response”: “jwt_vp_json_a”<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"> }<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">]<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Jan</span><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="color:black">From:
</span></b><span style="color:black">Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols-bounces@lists.openid.net> on behalf of Joseph Heenan via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols@lists.openid.net><br>
<b>Date: </b>Thursday, 16 May 2024 at 18:34<br>
<b>To: </b>Digital Credentials Protocols List <openid-specs-digital-credentials-protocols@lists.openid.net><br>
<b>Cc: </b>Joseph Heenan <joseph@authlete.com><br>
<b>Subject: </b>[Openid-specs-digital-credentials-protocols] Minutes from 16th May 2024 DCP WG call<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Participants:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Joseph Heenan<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Kristina Yasuda<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Daniel Fett<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Andreea Prian<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Arjen van Veen<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Bjorn Hjelm<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Brian Campbell<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">gabe<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Jan Vereecken<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Jin Wen<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Juba Saadi<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Michael Jones<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Oliver Terbu<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Pedro Felix<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Rajvardhan Deshmukh<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Ryan Galluzzo<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Sebastian Birckerle<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Sebastian Bahloul<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Sudesh Shetty<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Lukasz Jaromin<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><b>Events:</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">There will be a hybrid meeting with in-person participation for those at Identiverse; if you would like to attend in person please register on eventbrite:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://www.eventbrite.com/e/openid-foundation-dcp-wg-hybrid-meeting-at-identiverse-tickets-902324616217">https://www.eventbrite.com/e/openid-foundation-dcp-wg-hybrid-meeting-at-identiverse-tickets-902324616217</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It was proposed to cancel the normal working group meetings during Identiverse & EIC and no one objected.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><b>VP Query Language Proposal:</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Daniel shared the latest thoughts on the query language, presenting an evolution of the proposal created during IIW that meets the various requirements that were agreed by the working group, that includes some feedback from implementers
that looked at the previous proposal: <a href="https://hackmd.io/1siVhjzOTWOE9ppdF_t57A?view">
https://hackmd.io/1siVhjzOTWOE9ppdF_t57A?view</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">There was some discussion over the how the logic of “and/or” requests is expressed; Daniel said the current proposal is the simplest they could come up with.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Two people asked about how to return multiple credentials fulfilling the same single requirement; that hadn’t come up before and we probably need a way to express if the verifier wants all the matches or just one - new issue to be opened
for that.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jan asked where both ‘format’ and the name of the format specific parameters object (e.g. “vc+sd-jwt”) are required. Daniel said that ‘format' is necessary so there is a clear place for the verifier to figure out if it supports the requested
format, and then there’s also a desire to collect the format specific keys into a sub-object.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jan asked about implementations. There aren’t any yet that we’re aware of.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kristina asked if we wanted to proceed with a new query language format and if this proposal was a good way to proceed.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jan, Arjen, Brian, Michael J, Oliver, Gabe agreed it was a useful starting point. No one raised objections to using it as a starting point. Oliver wasn’t sure about the advances syntax features in example 7.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Next step is to open an issue.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><b>VP Transaction Data:</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kristina has opened 4 new issues for 4 specific points that need discussion, all tagged with the ’transaction data’ label.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Issue 173: The verifier needs an easy way to check the wallet is approve what it’s requested; given the difficulties of comparing json objects having the transaction request base64url encoded in the request & response seems like the best
solution right now.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><b>VP PRs:</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">#175 Add text/diagram for siopv2 conditional cred req flow<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://github.com/openid/OpenID4VP/pull/175">https://github.com/openid/OpenID4VP/pull/175</a> to solve <a href="https://github.com/openid/OpenID4VP/issues/86">https://github.com/openid/OpenID4VP/issues/86</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Please read and give feedback.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><b>VCI PRs/issues:</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://github.com/openid/OpenID4VCI/pull/314">https://github.com/openid/OpenID4VCI/pull/314</a> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Removed authorization_pending as discussed in previous meetings and notified to mailing list. No objections raised.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://github.com/openid/OpenID4VCI/pull/319">https://github.com/openid/OpenID4VCI/pull/319</a> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As per previous working group discussions, clarify how encryption works on batch endpoint - please review.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://github.com/openid/OpenID4VCI/pull/321">https://github.com/openid/OpenID4VCI/pull/321</a> - adds a new error code to credential endpoint for the issuer to indicate it’s denying the request - please review.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
<a href="https://github.com/openid/OpenID4VP/issues/171">https://github.com/openid/OpenID4VP/issues/171</a> - “nonce” handling should be more explicit.<o:p></o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
<o:p> </o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
Kristina pointed out that SD-JWT & W3C LDP sections do contain wording; Oliver will review it and raise a PR if it can be improved.<o:p></o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
<o:p> </o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
<o:p> </o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
<o:p> </o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
<a href="https://github.com/openid/OpenID4VP/issues/124">https://github.com/openid/OpenID4VP/issues/124</a> - client_id_scheme security considerations<o:p></o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
<o:p> </o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
We need to come to a decision on this. The feeling when discussed at OSW seemed to be folding the client_id_scheme into the client_id in some way so the existing iss/aud fields in JWTs can be used etc. To be discussed on next week’s WG calls.<o:p></o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
<o:p> </o:p></p>
<p style="margin:0cm;font-variant-caps:normal;font-stretch:normal;font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal">
<o:p> </o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>