[Openid-specs-digital-credentials-protocols] A short summary of today's virtual ISO mtg's outcome Re: Documents circulated to ISO SC17 WG10 Re: [agenda] DCP WG + SIOP call

[Kristina Yasuda]

Hi All,

Here is a short summary of today's virtual ISO mtg's outcome:
- there was rough consensus of not defining apv/apu values in the
specification (conditional to some ISO WG members wanting to make sure
there are no security implications of this)
- there was rough consensus on the current session transcript definition
(conditional to how client_id value discussion in multi RP PR goes)
- thumbs up on the overall `accepted_issuers` design. type `aki` works for
ISO.  there were some concerns raised with x509 thumbprint and VICAL URL
type. (https://github.com/openid/OpenID4VP/pull/393)
- thumbs up on multiple docs per doctype design. ISO shared that in 18013-5
rev 2, ISO uses the equivalent of `multiple: true` boolean in the request,
so the simplest would be for DCP WG to do the same (
https://github.com/openid/OpenID4VP/issues/298)
- based on the discussion labelled existing issue on "RP has to specify
exactly which data elements it needs" as relevant to ISO
https://github.com/openid/OpenID4VP/issues/304
- based on the discussion opened a new issues on "same credential
fulfilling multiple credential queries"
https://github.com/openid/OpenID4VP/issues/397
- based on the discussion labelled existing issue on "defining the behavior
when the RP sent a signed request but wallet cannot validate it  - fail or
proceed?: https://github.com/openid/OpenID4VP/issues/395
- OIDF shared current status of the multi RP PR

PRs/issues in OIDF GH repos and google doc have been updated accordingly:
https://docs.google.com/document/d/1AJDDWuRG_b-MOBrAwhBoQV3dhH3LD31WNEQKzOB36SY/edit?tab=t.0#heading=h.n5zxtfsgzn5s

This discussion will continue the first week of March during the next ISO
mtg.
OIDF DCP WG is expected to provide update on the above items two weeks
before that ISO mtg, so around February 18th.

Best,
Kristina


On Fri, Jan 17, 2025 at 9:28 PM Kristina Yasuda <yasudakristina at gmail.com>
wrote:

> 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/20250128/04bee069/attachment.htm>