<div dir="ltr">Spec Call Notes 2023-11-02<br><br>Bjorn Hjelm<br>Brian Campbell<br>Daniel Fett<br>David Chadwick<br>Giuseppe De Marco<br>Jonathan Rayback<br>Joseph Heenan<br>Judith Kahrer<br>Kristina Yasuda<br>Lukasz Jaromin<br>Mathew Miller<br>Michael Jones<br>Paul Bastian<br>Pedro Felix<br>Sudesh Shetty<br><br><br>Introductions<br> Jonathan Rayback<br><br>Events<br> IETF 118 Prague next week - <a href="https://www.ietf.org/how/meetings/118/" target="_blank">https://www.ietf.org/how/meetings/118/</a><br> OpenID Summit Tokyo 2024 - <a href="https://www.openid.or.jp/summit/2024/en/" target="_blank">https://www.openid.or.jp/summit/2024/en/</a><br><br>Informations<br>
Kristina: anyone interested in using the new browser/native wallet
selection APIs for Chrome and Android can reach out to Lee Campbell or
Samuel Goto from Google on the OpenID slack.<br><br>Pull Requests<br> The following PRs were merged:<br> <a href="https://github.com/openid/OpenID4VCI/pull/65" target="_blank">https://github.com/openid/OpenID4VCI/pull/65</a> (add identifiers for issuing credential of the same type, different content).<br> <a href="https://github.com/openid/OpenID4VCI/pull/64" target="_blank">https://github.com/openid/OpenID4VCI/pull/64</a> (clarify credential error response can be authorization or credential request error).<br><br> <a href="https://github.com/openid/OpenID4VCI/pull/66" target="_blank">https://github.com/openid/OpenID4VCI/pull/66</a> (add data integrity verifiable presentation as proof of possession).<br> Is almost good to be merged, with some changes required by Kristina.<br><br> <a href="https://github.com/openid/OpenID4VCI/pull/70" target="_blank">https://github.com/openid/OpenID4VCI/pull/70</a> (Wallet notifying the Issuer of acceptance/rejection of issued credential).<br> Needs more reviews.<br><br> <a href="https://github.com/openid/OpenID4VCI/pull/78" target="_blank">https://github.com/openid/OpenID4VCI/pull/78</a> (make authorization_servers credential issuer metadata parameter an array).<br> Pedro will also take a look at it. Will be merged if nothing major is found within a week.<br><br> <a href="https://github.com/openid/OpenID4VCI/pull/86" target="_blank">https://github.com/openid/OpenID4VCI/pull/86</a> (credentials Credentials Offer parameter values identifying credentials_supported object(s) in the issuer's metadata).<br> Pedro will review it.<br><br> <a href="https://github.com/openid/OpenID4VCI/pull/95" target="_blank">https://github.com/openid/OpenID4VCI/pull/95</a> (add user_pin_length and user_pin_description to Credential Offer).<br> Pedro will review it.<br><br>Issues<br> <a href="https://github.com/openid/OpenID4VCI/issues/97" target="_blank">https://github.com/openid/OpenID4VCI/issues/97</a> (Uniform usage of "JSON String" vs. "String" (/Object/Array/...) ).<br> Mostly editorial. The goal is to avoid the "JSON" prefix when not needed.<br> Daniel to create PR.<br><br> <a href="https://github.com/openid/OpenID4VCI/issues/91" target="_blank">https://github.com/openid/OpenID4VCI/issues/91</a> (Naming of credential_supported / credential / credential_instance)<br> Paul and Daniel presented the reasoning behind it.<br> Issue to be discussed next week, probably in front of a whiteboard at IETF 118.<br><br> <a href="https://github.com/openid/OpenID4VCI/issues/96" target="_blank">https://github.com/openid/OpenID4VCI/issues/96</a> (User PIN is not a PIN)<br> Common agreement that PIN (Personal Identification Number) is not a good fit.<br> Leave it open until next week ("bikeshedding for a week").<br><br> <a href="https://github.com/openid/OpenID4VCI/issues/93" target="_blank">https://github.com/openid/OpenID4VCI/issues/93</a> (How are credential copies issued?)<br>
It seems the main question in this issue is how to determine how
many "copies" of a credential should be issued. Is that determined by
the wallet or by the issuer.<br> Related to <a href="https://github.com/openid/OpenID4VCI/issues/91" target="_blank">https://github.com/openid/OpenID4VCI/issues/91</a><br><br>We agreed to cancel next week's DCP WG meeting due to IETF 118.</div>