[Openid-dcp] Fwd: APAC DCP WG minutes 11/08/25

[Joseph Heenan]

Hi all, please see the minutes below forwarded on behalf of Philip Halsall who took them (thanks Philip!)

Joseph


> Begin forwarded message:
> 
> 
> Attendees
> 
> Joseph Heenan (Host)
> Martijn
> Lenah Chacha
> Hiroyuki Sano
> Andreas Olave
> Philip Halsall
> 
> 1. Upcoming meeting registration - OIDF DCP WG Mtg prior to IIW - Mon 20 Oct 2025 - Cisco, San Jose, CA
> 
> https://dcpwg-iiw-20oct25.eventbrite.co.uk/
> 
> 2. Updates from Open ID foundation to ISO September/2025
> 
> - Annex D Discussion
> 1. Clarification requested on whether HAIP requires the document to be signed using P256
> 2. Consider whats to do with HPKE, given reported exclusion from HAIP 1.0
> 3. Discuss where (HAIP or Annex D) to address interoperability concerns
> 
> WG discussed the increasing important of HPKE, feedback is that HPKE be recognised as used by the market so it is encouraged to be in included in the 1.1 HAIP. Feedback is that move to HPKE at the same time as post quantum is not soon enough. 
> 
> - Annex B discussion
> Minutes to be shared once issued by ISO WG
> 
> 
> 3. Members are encouraged to vote on https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html
> 
> https://openid.net/foundation/members/polls/376
> 
> Reminder Voting closes 15th September
> 
> 4. OpenID4VCI PR's - https://github.com/openid/OpenID4VCI/pulls 
> 
> Approvals for open PR's would be appreciated
> 
> 5. OpenID4VP PR's - https://github.com/openid/OpenID4VP/pulls
> 
> Discussion around "intent_to_retain" which is currently defined as optional.  
> During ISO OpenId meeting a potential defect in the OpenID4VP spec was identified.  This field has been discussed previously and defined as optional. This may need to be mandatory and/or have a default value to be compatible with ISO mDoc. To resolve this the status of "intent_to_retain" may need to be updated as an Errata. Furthur discussion on "intent_to_retain" to go on agenda for Thursday WG and Tuesday WG calls to obtain clear consensus on how to proceed. See https://github.com/openid/OpenID4VP/issues/669
> 
> 6. OnenID4VC-HAIP PR's - https://github.com/openid/OpenID4VC-HAIP/pulls
> 
> Discussion on #264 some PR comments apear contradictory, agreement that comments and text need to be more explicit. Specifically generic text applied to "MUST" in a spec. Discussion recorded in PR #264
> 
> 
> --
> 
> Philip Halsall
> Sales Engineer
> 
> +852 52031315
> philip.halsall at terminal3.io <mailto:philip.halsall at terminal3.io>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20250911/21088cd3/attachment.htm>