[Openid-specs-digital-credentials-protocols] Fwd: OIDF DCP WG Meeting Minutes for 06.27.2024

[Joseph Heenan]

Forwarding this on behalf of Andy as it seems his original message didn’t reach the list.

(Thanks Andy for doing the minutes!)

From: "Andrew Lim (aclim)" <aclim at cisco.com <mailto:aclim at cisco.com>>
Subject: OIDF DCP WG Meeting Minutes for 06.27.2024
Date: 27 June 2024 at 17:19:49 BST
To: "openid-specs-digital-credentials-protocols at lists.openid.net <mailto:openid-specs-digital-credentials-protocols at lists.openid.net>" <openid-specs-digital-credentials-protocols at lists.openid.net <mailto:openid-specs-digital-credentials-protocols at lists.openid.net>>


Hi Folks,
 
Below are my minutes from today's meeting (06.27.2024).
 
Andy
 


Andy Lim   / Principal Engineer
alim at duosecurity.com <mailto:kdavenport at duosecurity.com>
aclim at cisco.com <mailto:kdavenport at duosecurity.com>
Duo.com <https://duo.com/>	


----------
Duo Security is now part of Cisco <https://duo.com/about/press/releases/cisco-completes-acquisition-of-duo-security>.
 
---------------------------------------------------------------
 
ODIF DCP WG Meeting 06.27.2024
 
Attendees:
Joseph Heenan
Bjorn Hjelm
Brian Campbell
David Chadwick
Juba Saadi
Lee Campbell
Pamela Dingle
Lukasz Jaromin
Nemanja Patrnogic
Oliver Terbu
Rajvardhan Deshmukh
Andy Lim
 
Topics:
 
PR & Issues Review
OID4VP profile for the W3C Digital Credentials API 
PR - https://github.com/openid/OpenID4VP/pull/155
Brian Campbell – seems like there a few unused files (e.g. PlantUML files)
A question came up about how comments would be addressed. Joseph noted that all comments will be addressed even if the reviewer has approved the changes
David Chadwick – approved the PR
Profile implies that all Javascript objects are JSON serializable

make credential_identifiers mandatory for authorization_details flow
https://github.com/openid/OpenID4VCI/pull/346/files
David Chadwick – will look at his comments that were addressed and see if can approve it

Is c_nonce required in proof or not?
https://github.com/openid/OpenID4VCI/issues/331
Discussion around whether the c_nonce should be required, which seems to lean toward make it clearly optional in the specification

Related issue - Remove c_nonce from the token response
https://github.com/openid/OpenID4VCI/issues/39
Joseph requested additional comments on this issue
Seems to be support for removing the c_nonce from the error response
 
Oliver Terbu – will be opening a new ticket to discuss the usage of ath and/or JTI within the scope of OID4VCI.
 
OIDF EU Wallet ARF 1.4 comments from DCP WG are due soon
Oliver Terbu and Lukasz Jaromin will be contributing to these comments
 
 



From: openid-specs-digital-credentials-protocols-request at lists.openid.net <mailto:openid-specs-digital-credentials-protocols-request at lists.openid.net>
Subject: confirm 971219707832908970dab368a93fa4d31536151b
Date: 27 June 2024 at 17:27:04 BST


If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message.  Do this if the message is
spam.  If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list.  The Approved: header can also appear in the first line
of the body of the reply.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20240629/771f19ed/attachment-0001.html>