[Openid-specs-ab] SIOP call notes (2022-May-26) - Atlantic call @ 7AM PST

[Kristina Yasuda]

Torsten Lodderstedt
Petteri Stenius
Joseph Heenan
Mark Haine
Anthony Nadalin
Giuseppe De Marco
Brian Campbell
Jo Vercammen
David Chadwick
Kristina Yasuda

- PRs https://bitbucket.org/openid/connect/pull-requests/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbitbucket.org%2Fopenid%2Fconnect%2Fpull-requests%2F&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7Ca3e2f5020a0a471a80ac08da2345a7f4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637861080372239747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GiZO9pDDJe49k9n1o%2BBmumfQwlCUTNcNHkKbV34rhUg%3D&reserved=0>

*       Priority PR #145 - [OpenID4CI] Revises the approach to credential metadata publishing. Issue 1466

     *   There are two questions to discuss: 1/ whether an (abstract) credential type (ie `driver_license`) should be used as a key? 2/ and whether a format specific credential type or credential type that spans the format should be used
     *   Kristina proposed to keep a new/abstract credential name while introducing a mapping between format and a credential type

        *   David Chadwick recommended to make an abstract credential name global

     *   Kristina to update a PR
     *   This PR is related to a PR #186, since we want to enable a smooth flow for issuance of a VC during presentation.
*       Priority PR #176 - [OIDC4VP] Base OIDC4VP on OAuth

     *   Decided to break up this PR into two parts - one to base it on OAuth (PR #176) and another one to introduce issuance of a VC using scopes (#186) (Thank you, Torsten for already filing a second PR!)
     *   We want to prioritize merging PR #176 hopefully next week, since there is an agreement in the direction and this is one of the largest remaining breaking changes
*       PR #170 - [OpenID4CI] renaming to OpenID for CI

     *   Agreed to merge once Kristina renames to "OpenID for Verifiable Credentials Issuance" from "OpenID for Credential Issuance"

*       PR #157: Building Trust Between Wallet and Issuer

     *   Agreed that Giuseppe's proposed `signed_jwk` can be discussed in a subsequent PR.
- Issues https://bitbucket.org/openid/connect/issues?status=new&status=open&component=SIOP&component=Verifiable%20Presentation&component=Credential%20Issuance<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbitbucket.org%2Fopenid%2Fconnect%2Fissues%3Fstatus%3Dnew%26status%3Dopen%26component%3DSIOP%26component%3DVerifiable%2520Presentation%26component%3DCredential%2520Issuance&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7Ca3e2f5020a0a471a80ac08da2345a7f4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637861080372239747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Bg9nlSEAZVfFFYM73Fr7%2BXikNdxHamLjRo2dzCymk0U%3D&reserved=0>
*       Priority #1501 a suggestion to leave it to the implementations whether to encode a VP in the credential response or not (OpenID4CI)

     *   Agreed to take out the requirement that the returned credential is base64url encoded, and include a temporary table in OpenID4VP on how each credential format (ie signature scheme) shall be returned in the VP Token, to reduce dependency on external specifications/registries.
o   Kristina to collaborate with Alen on a PR

Best,

Kristina




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20220528/8ce0f6ea/attachment.html>