[Openid-dcp] DCP WG Apac call agenda

Jan Vereecken jan.vereecken at meeco.me
Thu Feb 5 17:10:55 UTC 2026


Hello Everyone,

Please find the minutes of today's meeting below.

Have a good day!

Cheers,
Jan

---

DCP EU-Friendly WG Meeting on 2026/02/05

# Attendees

- Kristina Yasuda
- Gail Hodges
- Joseph Heenan
- Bjorn Hjelm
- Brian Campbell
- Christian Bormann
- Daniel Fett
- Frederik Krogsdal Jacobsen
- George Fletcher
- Klaus Roehrle
- Paul Bastian
- Peter Sorotokin
- Valentine Mazurov
- Brian Campbell
- Andreea Prian


# Agenda

See Joseph's email

# Notes

## General

- Launch of Adhaar App in India with DC API and ISO 18013-5. This should mean that they also use OpenID4VP, but no public information about it. https://blog.google/intl/en-in/company-news/technology/partnering-with-uidai-to-bring-a-secure-digital-first-identity-with-aadhaar-on-google-wallet/ Google announcement related to UIDAI and use of dc api and ZK. https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://uidai.gov.in/images/New_A
- OIDF conformance tests updates to launch in the near future. Testing would be appreciated.

## OpenID4VP

Bunch of issues related to HPKE are ready for PR. Looking for people that can work on it.

## OpenID4VC HAIP

## OpenID4VCI

Add credential identifier (which fixes credential versioning).
https://github.com/openid/OpenID4VCI/pull/472

Paul will review

Rephrase conditions to provide nonce in proof types based on presence of Nonce endpoint
https://github.com/openid/OpenID4VCI/pull/678

Valentine comments that it is not always clear that nonce is required which results in unnecessary pings
Joseph and Christion: The intention is that if the nonce_endpoint is defined in the metadata, you must use it

Christian will review

Add invalid_tx_code error code to pre-authz code flow
https://github.com/openid/OpenID4VCI/pull/686

Discussion on Paul's comment to change a SHOULD to MUST. He's okay with dropping it as this would otherwise result in breaking change and want to include it in 1.1.
Frederik comments that language can be expanded
Discussion on whether this truly is a breaking change.

Paul and Joseph argue that errata should contain something on brute force protection, as this is something that currently seems to be missing.
Jan to create an issue on this

Use expected URL instead of expected origins for IAE flow
https://github.com/openid/OpenID4VCI/pull/695

Christian comments that it could be a bit clearer in terms of expected behaviour

add credential format profile for vcdm 2 with jose
https://github.com/openid/OpenID4VCI/pull/699

Brian thinks this is a bad idea as the example is not good and referenced material does not meet professional quality.

The WG does not yet support adding this as a profile to VCI

Discussion can happen on the existing PR

Stuttgart 3: align example and text on auth_session in the response
https://github.com/openid/OpenID4VCI/issues/690

Discussion on the issue. Ready for PR.

Frederik will create a PR

________________________________
From: Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols-bounces at lists.openid.net> on behalf of Joseph Heenan via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols at lists.openid.net>
Sent: Tuesday, 3 February 2026 22:26
To: Digital Credentials Protocols List <openid-specs-digital-credentials-protocols at lists.openid.net>
Cc: Joseph Heenan <joseph at authlete.com>
Subject: [Openid-dcp] DCP WG Apac call agenda

Hi all

Here’s the proposed agenda for the APAC friendly call in around 10.5 time on the usual zoom, https://zoom.us/j/94085567252?pwd=cHNFMExFalhlM2MrOFhoN3J6eDRuZz09

  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
     *   OSW (27th-29th May) Call for Presentations is open: https://oauth.secworkshop.events/osw2026
     *   IETF China soon
     *   DICE 2026: Copenhagen 22nd-24th June https://dice2026.framer.website/
  6.  Standing topics for general updates
     *   Test requirements document for EU
     *   Updates from Ecosystem CG (Frederik / Dima)
     *   Conformance test updates - https://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/Week-of-Mon-20251117/001035.html https://openid.net/openid-for-verifiable-credential-self-certification-to-launch-feb-2026/
     *   Joint work with ISO - latest meeting was on 3rd Feb, next meeting on 12th Jan (different date then previously, invite will be updated soon)
     *   Server2server special-topic call updates - https://github.com/openid/OpenID4VCI/issues/663 https://github.com/openid/OpenID4VCI/issues/668
  7.  Co-chair vacancy https://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/Week-of-Mon-20260119/001107.html
  8.  VP response encryption with HPKE
     *   HPKE JWE spec is at WGLC: https://mailarchive.ietf.org/arch/msg/jose/pWhoKv9-ENdzqDPcCijBjCMKsDA/
     *   Tweak to VP: https://github.com/openid/OpenID4VP/issues/682
     *   Define a profile in HAIP for interoperability https://github.com/openid/OpenID4VC-HAIP/issues/357
     *   Need to agree how to add this in HAIP, e.g. who would be required to support it, wallet or verifier https://github.com/openid/OpenID4VC-HAIP/issues/356
     *   Other issues already tagged for 1.1: https://github.com/openid/OpenID4VP/milestone/4
     *   Is there anything else we should plan to address before we do WGLC for VP 1.1 / HAIP 1.1?
  9.  IAE issues/PRs
     *   UoStuttgart feedback on IAE: https://github.com/openid/OpenID4VCI/issues?q=is%3Aissue%20state%3Aopen%20label%3Aiae
     *   Suggested timelines for 1.1: https://github.com/openid/OpenID4VCI/issues/687
     *   Priority issues for 1.1: https://github.com/openid/OpenID4VCI/issues?q=is%3Aissue%20state%3Aopen%20label%3Apriority<https://github.com/openid/OpenID4VCI/issues?q=is%3Aissue%20state%3Aopen%20label%3Apriority%20milestone%3A1.1>

If anyone has any specific topics they’d like to cover please reply to this email or ask at the start of the call.


Thanks

Joseph

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20260205/66cbcfbd/attachment-0001.htm>


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