[Openid-specs-digital-credentials-protocols] Documents circulated to ISO SC17 WG10 Re: [agenda] DCP WG + SIOP call

Kristina Yasuda yasudakristina at gmail.com
Fri Jan 17 20:28:01 UTC 2025


Hi All,

Please find attached documents that OIDF liaison circulated to ISO SC17
WG10 in preparation for the virtual ISO SC17 WG10 meeting in the last week
of January:

- pdf of the current version of HAIP specification
- updated status of the requirements from ISO (Google doc version is here:
https://docs.google.com/document/d/1AJDDWuRG_b-MOBrAwhBoQV3dhH3LD31WNEQKzOB36SY/edit?tab=t.0#heading=h.n5zxtfsgzn5s
)
Please let me know if you would like to see anything changed in this
document.

The goal of this virtual ISO SC17 WG10 meeting is to get ISO's feedback on
the  mdoc profile of OID4VP over the Digital Credentials API. Ideally, this
part of HAIP could be considered 80-90% ready after this ISO virtual
meeting - we will see.

Best,
Kristina


On Wed, Jan 15, 2025 at 8:53 PM Kristina Yasuda <yasudakristina at gmail.com>
wrote:

> Hi all,
>
> Below is the suggested agenda for today's DCP WG + SIOP call tomorrow.
> After this call, we plan to submit to ISO a version of OID4VP and HAIP for
> review in preparation for a virtual SC17 WG10 mtg in the last week of
> January.
>
>    1. OIDF Antitrust Policy at www.openid.net/antitrust applies
>    2. IPR reminder/ Note-taking
>    3. Introductions/re-introductions
>    4. Agenda bashing/adoption
>    5. Events/External orgs
>       1. please register to the Hybrid meeting before OSW!
>       https://www.eventbrite.co.uk/e/oidf-dcp-wg-hybrid-meeting-prior-to-osw-2025-tickets-1146184230889
>    6. OID4VP / HAIP: Topics we need to tackle before ISO's virtual
>    meeting in the last week of january (they are labelled ISO_VirtualMeeting):
>       - merged! https://github.com/openid/OpenID4VP/pull/374;
>       https://github.com/openid/oid4vc-haip/pull/146
>       - would be good to merge after Thu WG call:
>       https://github.com/openid/OpenID4VP/pull/338
>       - *highest priority: seems that currently proposed solution is to
>       add origin to the protected header to meet an ISO requirement "Response
>       encryption authentication must be bound to the origin, e.g. RP
>       URL".https://github.com/openid/OpenID4VP/pull/380
>       <https://github.com/openid/OpenID4VP/pull/380>;*
>       *https://github.com/openid/oid4vc-haip/pull/155*
>       <https://github.com/openid/oid4vc-haip/pull/155>
>       - need to come up with a solution for returning multiple
>       credentials for one DCQL query:
>       https://github.com/openid/OpenID4VP/issues/298
>       - Add issuer identifier for mdocs to DCQL
>       https://github.com/openid/OpenID4VP/issues/322
>       - need to agree on apu/apv value and session transcript when
>       multiple client_ids present in the request
>       https://github.com/openid/OpenID4VP/pull/308
>
> Thank you!
> Kristina
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20250117/acd2378c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenID4VC High Assurance Interoperability Profile - draft 01.pdf
Type: application/pdf
Size: 559875 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20250117/acd2378c/attachment-0002.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ISO-OIDF alignment on the mdoc profile of OID4VP over the Browser API_v.2.0.pdf
Type: application/pdf
Size: 237769 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20250117/acd2378c/attachment-0003.pdf>


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