[Openid-dcp] EU call agenda 09 Jul 2026
Brent Zundel
brent.zundel at yubico.com
Wed Jul 8 22:23:17 UTC 2026
Agenda topic for 09 Jul 2026 EU DCP WG 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
2.
Note-taking
3.
Introductions
4.
Agenda bashing
5.
Events
1.
REPORT Hybrid meeting - Monday, 22nd June, before DICE.
2.
REPORT DICE https://diceidentity.org/
3.
IETF meeting Vienna, July
4.
Solar eclipse
https://en.wikipedia.org/wiki/Solar_eclipse_of_August_12,_2026 in
Europe.
5.
GDC Geneva in September - do register as there may be limited
tickets: https://globaldigitalcollaboration.org/
6.
Standing topics for general updates
1.
Test requirements document for the EU
2.
Conformance test updates -
1.
Feedback being applied
2.
ISO interop for VP
1.
Verifier
2.
Wallet
3.
Over the next 2 weeks, a new user interface for the test suite
will be deployed.
4.
DCP chairs: can you try to get to consensus on some of the
certification issues please?
1.
https://github.com/openid/OpenID4VCI/issues?q=is%3Aissue%20state%3Aopen%20author%3Ajogu%20label%3Acertification
1.
https://github.com/openid/OpenID4VP/issues/718
2.
https://github.com/openid/OpenID4VC-HAIP/issues/364
3.
https://github.com/openid/OpenID4VCI/issues/744 is probably
the biggest one as we're seeing real interoperability
issues from that.
4.
Don't need PRs, but need a clear statement from the WG on
the direction they want to go so we can make sure that
is aligned with the
tests.
3.
Joint work with ISO:
DCHP WG in OIDF - set up now.
1.
Looking for a DCHP GitHub repo, Slack channel, and a mailing list.
2.
Martijn made an initial contribution.
3.
GO: Likely discussion points being raised as issues.
7.
Presentation
1.
Review open PRs/issues.
1.
https://github.com/openid/OpenID4VP/pull/719 Co-chairs, is it
ready to be merged?
2.
https://github.com/openid/OpenID4VP/pull/744
1.
GO to review requested changes.
2.
MH: Should matching be checked by conformance test? If it is
true, should the SD-JWT-VC spec be changed? It is more of
business logic
than security control.
3.
https://github.com/openid/OpenID4VP/pull/750
1.
MH to comment on the PR
4.
https://github.com/openid/OpenID4VP/pull/748
1.
To be discussed in a larger call.
5.
https://github.com/openid/OpenID4VP/pull/745 Oliver TODO
6.
https://github.com/openid/OpenID4VP/pull/647 to be closed. CB to
create a new PR
7.
Other PRS - waiting for changes.
2.
Other issues already tagged for 1.1:
https://github.com/openid/OpenID4VP/milestone/4
1.
https://github.com/openid/OpenID4VP/issues/741 GO to write a text
2.
https://github.com/openid/OpenID4VP/issues/634 Should remove from
1.1 or close until DC API issue is resolved.
3.
https://github.com/openid/OpenID4VP/issues/680 Waiting for a PR
4.
PRs in progress
1.
https://github.com/openid/OpenID4VP/issues/723
2.
https://github.com/openid/OpenID4VP/issues/647
3.
https://github.com/openid/OpenID4VP/pull/745 Reviewed. Everyone is to
review the PR and leave comments. CB, FK, GO.
4.
https://github.com/openid/OpenID4VP/pull/726 FK to Jan.
5.
Is there anything else we should plan to address before we do WGLC
for VP 1.1 / HAIP 1.1?
6.
1.2 Proposed Features
1.
Harmonisation protocol
2.
?
8.
Issuance
1.
IAE / Building Interactive Authorization on top of first-party apps
draft #736 https://github.com/openid/OpenID4VCI/pull/736
1.
TODO: More reviews desired.
1.
TC volunteers to review.
2.
CB needs more time.
2.
First, let’s merge the main PR, then resolve the remaining PRs.
1.
https://github.com/openid/OpenID4VCI/pull/695
2.
https://github.com/openid/OpenID4VCI/issues/595
2.
Server2server issuance special-topic call updates -
https://github.com/openid/OpenID4VCI/issues/663
https://github.com/openid/OpenID4VCI/issues/668
1.
Draft PR: https://github.com/openid/OpenID4VCI/pull/753
3.
Review open PRs
1.
https://github.com/openid/OpenID4VCI/pull/759 PB created a new PR to
replace the old PR https://github.com/openid/OpenID4VCI/pull/723.
2.
https://github.com/openid/OpenID4VCI/pull/472 OT diagram discussed.
3.
https://github.com/openid/OpenID4VCI/pull/678 JH to re-review?
4.
https://github.com/openid/OpenID4VCI/pull/759/
1.
Do we need this at all, or can it be a part of the main text?
2.
To be discussed in a larger call.
4.
Issues https://github.com/openid/OpenID4VCI/issues
1.
Credential metadata bundle - ideally all together
1.
https://github.com/openid/OpenID4VCI/issues/735 1.2?
2.
https://github.com/openid/OpenID4VCI/issues/737 1.2?
3.
https://github.com/openid/OpenID4VCI/issues/738 1.2?
4.
https://github.com/openid/OpenID4VCI/issues/739 1.2?
2.
5.
Triage UoStuttgart feedback & other issues on IAE:
https://github.com/openid/OpenID4VCI/issues?q=is%3Aissue%20state%3Aopen%20label%3Aiae
6.
Suggested timelines for 1.1:
https://github.com/openid/OpenID4VCI/issues/687
7.
Priority issues for 1.1:
https://github.com/openid/OpenID4VCI/issues?q=is%3Aissue%20state%3Aopen%20label%3Apriority
1.
IA
2.
?
8.
Priority issues for 1.2:
1.
S2S
2.
Credential metadata ?
9.
Display metadata: https://github.com/openid/OpenID4VCI/issues/421
10.
Deferred mandatory or not.
11.
FIDO trust registry?
--
Brent Zundel
Standards Architect | Yubico <http://www.yubico.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20260708/af6fd27c/attachment-0001.htm>
More information about the Openid-specs-digital-credentials-protocols
mailing list