[Openid-specs-digital-credentials-protocols] [agenda] DCP WG + SIOP call

[torsten at lodderstedt.net]

Hi all,

here are the minutes of this call.

Attendees
Jin Wen (Nok Nok Labs)
Daniel Fett
Torsten Lodderstedt
Oliver Terbu
Kristina Yasuda (OIDF)
Martijn Haring
nemanja.patrnogic
Paul Bastian
Steve Venema
Joseph Heenan (OIDF & Authlete)
Brian Campbell
Pamela Dingle
George Fletcher
Michael Jones
Nat Sakimura
Giuseppe
Judith Kahrer
Christian Bormann
Hicham Lozi [Apple]
Bjorn Hjelm
Tom Jones
Pedro Felix
Juba Saadi | Lissi GmbH
Michael Jones
Rajvardhan Deshmukh

Agenda
1. IPR reminder/ Note-taking
2. Introductions/re-introductions
3. Agenda bashing/adoption
4. Events/External orgs
5. recap on the client_id_scheme security discussion from Tuesday ( https://github.com/openid/OpenID4VP/issues/124 )
6. Transaction Data PR ( https://github.com/openid/OpenID4VP/pull/197/files )
7. Wallet authenticating to the Verifier ( https://github.com/openid/OpenID4VP/issues/141 )
8. Issues ready for PRs - who can help please?
9. Other Open PRs/Issues

Wallet Draft presentation in the next Thu WG call.
Chairs will come up with strategy to move specs forward
https://github.com/openid/OpenID4VP/issues/124
de-briefing about the presentation of Oliver in the Tue call
Oliver and Tobias will try to file a PR with a proposal by next Tue, will make it the focus topic of this call then
https://github.com/openid/OpenID4VP/pull/197
discussion on renaming input_descriptor_ids
Paul: concerns to mix transaction data and credential presentation, suggest to use another response type (different sub protocol) or credential format (and/or new response type), sees need for more text to make it complete, mechanism will work for credentials with key binding only. Paul to add his concerns to related issue
Christian: we are overloading existing mechanisms, in previous discussions, we already discussed this will also need policies.
https://github.com/openid/OpenID4VP/issues/141
Paul: option 2 requires definition of the JWT credential format
Christian: option 2 requires different treatment in the wallet UX, what about the DC API?
Paul: add the wallet attestation as top level response parameter


best regards,
Torsten.
Am 22. Aug. 2024, 16:53 +0200 schrieb Kristina Yasuda via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols at lists.openid.net>:
> > Hi All,
> >
> > Below is the suggested agenda for today's DCP WG + SIOP call
> >
> > 1. IPR reminder/ Note-taking
> > 2. Introductions/re-introductions
> > 3. Agenda bashing/adoption
> > 4. Events/External orgs
> > 5. recap on the client_id_scheme security discussion from Tuesday ( https://github.com/openid/OpenID4VP/issues/124 )
> > 6. Transaction Data PR ( https://github.com/openid/OpenID4VP/pull/197/files )
> > 7. Wallet authenticating to the Verifier ( https://github.com/openid/OpenID4VP/issues/141 )
> > 8. Issues ready for PRs - who can help please?
> > 9. Other Open PRs/Issues
> >
> > Thank you!
> > Kristina
> --
> Openid-specs-digital-credentials-protocols mailing list
> Openid-specs-digital-credentials-protocols at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20240822/30964218/attachment.html>