[Openid-dcp] Meeting notes for DCP EU WG call agenda (Aug-6-2026)

Paul Bastian paul.bastian at posteo.de
Thu Aug 6 15:59:46 UTC 2026


Attendees:
- Brent Zundel
- Paul Bastian
- Frederik Krogsdal Jacobsen
- Filip Skokan
- Gareth Oliver
- Martjin Haring
- Ashmita Chakraborty
- Oliver Terbu
- Gail Hodges
- David Zeuthen
- Rajvardhan Deshmukh
- Klaus Roehrle

Notes:
- pre-GDC meeting for DCP group meeting & DCHP group meeting
- tickets for eventbrite are available again
- Server-to-Server issuance

Remove any terminating / from the Credential Issuer Identifier when 
forming the Credential Issuer Metadata URL - #775
- technically breaking change, but in fact not, because libraries are 
usually already doing this
- problems while creating the well-known path
- proposal to not allow terminating slashes in Credential Issuer Identifier
- Filip is in favor of RFC8414 language and do not add language about 
Credential Issuer Identifier
- Filip says that there are AS/RS with terminating slashes in the wild
- Gareth thinks SHOULD is fine
- Filip says that terminating slash does not oppose URL rules and is 
legitimate
- if no further feedback is received, Paul will remove the SHOULD 
language on the Credential Issuer Identifier

Gail wants to catch up on where WG is on formally accepting the 
Stuttgart feedback on VCI 1.1, and there being a stable version of the 
spec ready for Stuttgart to progress their analysis to the model 
revision and Proof stages. They cannot continue until WG completes these 
two actions.

add redirect_uri to Credential Offer - #759
- ready for merge with 3 approvals
- Joseph had a request for changes, Brent will reach out again to Joseph
- otherwise we merge next week

Add credential dataset version - #472
- Paul explains the updated PR, implementing both an identifier and a 
version
- Martjin vouches for wallet requirements to have a MUST, otherwise the 
feature becomes less valuable
- Gareth thinks a MUST is difficult with backwards-compatibility, unless 
Issuer knows the VCI version
- Martjin agrees
- we are lacking feature negotiation
- Oliver says issuer could announce support in issuer metadata and 
wallet could send the feature capability in Credential Request
- Gareth says we need to be careful to have permutations of 
capabilities, which makes maintenance harder
- Paul thinks even with SHOULD it's a massive improvement over VCI 1.0
- capability negotiation should be a separate issue and then we may 
change the SHOULD into MUST

Add security guidance for platform-specific Origins and DC API. - #761
- Martjin prefers to remove the last of the platform requirements

Clarify an empty object in a VP Token cannot be used to signify an error 
response - #745
- Joseph re-reviewed
- Oliver incorporated all suggestions with one exception
- back to Joseph


On 8/6/26 16:54, Kristina Yasuda via 
Openid-specs-digital-credentials-protocols wrote:
>
> Proposed agenda for today's call:
>
>
> 1.
>
>     Code of conduct / Antitrust policy / IPR
>     policy:https://openid.net/wp-content/uploads/2025/06/OIDF_Groups-Activities-Events-Note-Well_Final_2025-06-12.pdf
>     <https://openid.net/wp-content/uploads/2025/06/OIDF_Groups-Activities-Events-Note-Well_Final_2025-06-12.pdf>
>
> 2.
>
>     Note-taking
>
> 3.
>
>     Introductions
>
> 4.
>
>     Agenda bashing
>
> 5.
>
>     Events
>
> 6.
>
>     Issuance
>
>  *
>
>     Server2server draft adopted.
>     https://github.com/openid/OpenID4VCI/pull/753 merged
>
>  *
>
>     IAE / Building Interactive Authorisation on top of first-party
>     apps draft.
>
>  *
>
>     Review other open PRs: https://github.com/openid/OpenID4VCI/pulls
>     <https://github.com/openid/OpenID4VCI/pulls>
>
>  *
>
>     Review open Issues https://github.com/openid/OpenID4VCI/issues
>     <https://github.com/openid/OpenID4VCI/issues>
>
>     7. Presentation
>
>     1.
>
>         plan is to publish an errata
>
>     2.
>
>         WG is asking for implementation experience of implementing
>         jose-hpke based presentation response encryption to decide if
>         to do implementer's draft before publishing OpenID4VP 1.1
>
>     3.
>
>         Review open PRs https://github.com/openid/OpenID4VP/pulls
>         <https://github.com/openid/OpenID4VP/pulls>
>
>     4.
>
>         Review open issues https://github.com/openid/OpenID4VP/issues
>         <https://github.com/openid/OpenID4VP/issues>
>
>
>         8. AOB
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20260806/b18f5f2e/attachment-0001.htm>


More information about the Openid-specs-digital-credentials-protocols mailing list