[Openid-specs-ab] SIOP call agenda (2022-July-7th) - Atlantic call @ 7AM PST

[Kristina Yasuda]

Hi All,

Below is a proposed agenda for the SIOP call.

Latest versions of OpenID for VPs, OpenID for VCI and SIOPv2 have been published to both openid.net and openid.bitbucket.io
There are quite significant changes to the first two drafts so please make sure you review the latest versions with the date June 21st.

Second draft of the "OpenID for Verifiable Credentials" Whitepaper (only editorial updates) has been published during Identiverse2022 - the URL is the same. Thank you everyone who has provided feedback.


- IPR reminder/recording

- Introductions/re-introductions

- Agenda bashing/adoption

- Events/External orgs
o IETF, Philadelphia, July 23-30, 2022
o W3C TPAC, Vancouver, Sept 12-16, 2022
- 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%7C8dda1f644e0b4acc860208da5a6a0270%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637921709384907103%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=9pLaeHNSL0K29lCCgGtm6b55uRjMF5CwVxtr4exbY9o%3D&reserved=0>
*       Discuss - please review (discussion max 15min each)

     *   PR #228 - Issuance restructure: diff too big, HTML for review attached
     *   New PR #229 correction to the OP metadata JSON: credentials_supported is defined as "A JSON object containing a list of key value pairs..." not an array of objects.
     *   Discuss PR#227 - rename from `registration` to `client_metadata` parameter
     *   New PR#226 initiate issuance schema
     *   Hoping to merge PR#225 mid format identifiers
- 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%7C8dda1f644e0b4acc860208da5a6a0270%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637921709384907103%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=u7oRbjhhkSi%2FTLUPa%2FkMjvCQOEYuS%2B1YZQgz09BvFE4%3D&reserved=0>

  *   (Max 15min per issue)

  *   #1500 openid_initiate_issuance is an invalid URI scheme
  *   #1540 [siopv2] `cnf` instead of `sub_jwk`? -> `sub_jwk` or JWK header seems to be sufficient
  *   #1538 Clarify valid response_type values - response_type = vp_token


  *   [some have been addressed] As discussed in the previous SIOP call, editors triaged the issues to identify potential breaking changes in SIOPv2 and OIDC4VP specifications. This is important to be able to refer to these standards in ISO documents.

  *   Breaking

     *   1402: [siopv2] Cross device flow w/ and w/o authorization_endpoint

  *   Non-breaking

     *   1401: [siopv2] Advanced/Better discovery/registration - might be important in light of solving a NASCAR problem
     *   1448: [siopv2] def of cross-device
- AOB



Best,

Kristina




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20220706/2b15253c/attachment.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20220706/2b15253c/attachment-0001.html>