[Openid-specs-digital-credentials-protocols] 2024-10-10 DCP WG call meeting minutes
Oliver Terbu
oliver.terbu at mattr.global
Thu Oct 10 16:08:57 UTC 2024
Dear all,
Meeting minutes of the 2024-10-10 DCP meeting below:
Participants:
- Oliver Terbu
- Joseph Heenan
- Daniel Fett
- Kristina Yasuda
- Bjorn Hjelm
- David Chadwick
- David Waite
- Javier Ruiz
- Juba Saadi
- Michael Jones
- Paul Bastian
- Rajvardhan Deshmukh
- Tim Capelli
IPR Reminder
Introductions:
None
Agenda:
Pre IIW Event:
- The event will be hosted at Microsoft.
- Registration is required and registration link can be found on the mailing list.
DCP WG: Plans for 1.0 Final:
- The EC has extended the timeline, allowing an opportunity to revise the plan.
- The proposed approach is available here:
https://docs.google.com/presentation/d/1MwNwD3DSf_JuKFuudg66Ib9cJemMOGXniySvjJQHjUM/edit#slide=id.g309467ef06d_0_35
- New timelines and approach for a new ID for OID4VP, version 1.0 of OID4VP, and OID4VCI were agreed upon by the WG.
- Whether to issue a new ID for OID4VCI or proceed directly to the final version will be discussed on the next call.
Transaction Data (PR #197):
- Discussion focused on QTSP-centric flow vs. wallet-centric flow and the impact on interoperability.
- It was agreed that QTSP is out of scope for transaction data.
NQL (PR #266):
- Updates made in the PR were presented, including:
- Updated examples
- Removal of all algorithm-related features from the query
Open topics discussed:
- Priorities for credential sets: should these be encoded as an ordered array or using an object for extensibility? The consensus was on using ordered arrays.
- Value matching: whether to keep both `values` and `value` or just use one. Consensus was to use `values`.
- How to encode claims that should be presented if available. Consensus on supporting this feature, but the encoding is still under discussion (?? vs !? etc.).
Key Attestations (PR #389):
- Updates to the PR were presented.
Discussions:
- JWT and attestation flows, with agreement on possible options.
- Whether to keep or replace `x5c` with `key_attestations`. No conclusion reached.
Other PRs not discussed on the call but needing feedback/reviews:
- VCI: Add option to use `credential_configuration_id` in the credential request:
https://github.com/openid/OpenID4VCI/pull/392
- VP: Discontinue ad hoc and inappropriate use of "OAuth URI"s:
https://github.com/openid/OpenID4VP/pull/279
- VP & VCI: Additional IANA considerations. Complete IANA Considerations section.
- VCI: Remove `c_nonce`/`c_nonce_expires` from the credential endpoint response:
https://github.com/openid/OpenID4VCI/pull/404
- VCI: Clarify language around opening the Credential Offer Endpoint:
https://github.com/openid/OpenID4VCI/pull/380
- VCI: Add valid signatures for the `jwt_vc_json` section:
https://github.com/openid/OpenID4VCI/pull/403
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20241010/b396dec2/attachment-0001.html>
More information about the Openid-specs-digital-credentials-protocols
mailing list