[Openid-dcp] DCP WG APAC 28th August 2025 Meeting Notes

[Stefan Charsley]

DCP WG APAC 28th August 2025
Attendees

Martijn Haring

Kenichi Nakamura

Hiroyuki Sano

Matt McInnes

Andres Olave

Joseph Heenan

Stefan Charsley


Updates:

   -

   IIW end of october, DCP WG meeting monday morning prior at CISCO, OIDF
   general workshop on the evening, second meeting on the friday after
   location TBD
   -

   Upcoming ISO mDL meeting in a couple of weeks
   -

   VCI draft 17 published, voting announcement sent, voting starts next
   week, WG needs to make formal decision next week to start voting
   -

   IAE removed from VCI as not enough time to get sorted, look at adding it
   in 1.1
   -

   Working through issues for HAIP then can start public review, at least 2
   more weeks before WGLC



Discussing OpenID4VCI:

Make language in split-architecture more specific #639
<https://github.com/openid/OpenID4VCI/pull/639>

   -

   Needs more reviews


align holder binding terminology to VP #621
<https://github.com/openid/OpenID4VCI/pull/621>

   -

   Once updated needs review



Discussing HAIP

refactor OID4VC sections to include ISO mdocs #228
<https://github.com/openid/OpenID4VC-HAIP/pull/228>

   -

   Martijn: second bullet point change in the flows to implement makes it
   unclear what presentation flows must be supported, related
   https://github.com/openid/OpenID4VC-HAIP/issues/193
   -

   Joseph: intention is not to require both redirect flow and DC API flow
   -

   Martijn to make a comment on the PR



Are we sure we want the redirect_uri in cross device scenarios, too? #98
<https://github.com/openid/OpenID4VC-HAIP/issues/98>

   -

   Stefan: does this wording prohibit implementations from supporting
   non-DC API cross device flows?


   -

   Stefan: prohibiting implementations from supporting non-DCAPI
   cross-device is too extreme and will rule out many use cases


Require use of (most of) FAPI2 with VCI #214
<https://github.com/openid/OpenID4VC-HAIP/pull/214>

   -

   Joseph: need to check paul is happy with answers, then can be merged
   -

   Martijn: can mTLS still be used?
   -

   Joseph: Wallet Attestation client authentication must be used


Changes to additional SD-JWT VC requirements #165
<https://github.com/openid/OpenID4VC-HAIP/pull/165>

   -

   Martijn: why does iss have to be an HTTPS url?
   -

   Joseph: there doesn’t seem to be an obvious reason, made note in
   https://github.com/openid/OpenID4VC-HAIP/issues/247


clarify batch issuance requirements #229
<https://github.com/openid/OpenID4VC-HAIP/pull/229>

   -

   Ongoing discussion, please comment if you feel


prevent trust anchor certs to be included in x5c header #238
<https://github.com/openid/OpenID4VC-HAIP/pull/238>

   -

   Enough reviews, merging


dpop nonce requirements should be explicit #245
<https://github.com/openid/OpenID4VC-HAIP/pull/245>

   -

   Enough reviews
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20250828/6de12d01/attachment-0001.htm>