[Openid-specs-digital-credentials-protocols] SIOP/DCP WG call notes Oct-26-2023

[Kristina Yasuda]

Huge thank you to Sudesha for taking notes! (sending on his behalf while we figure out why he has not been able to post to the ML)

  *   New member in the call: Alexander Shcherbakov from Data Storage Research
  *   Agenda Today
     *   3 PRs on issuance that we really need to get through the finish line.
     *   Events: IETF is coming in 2 weeks, Topics to be discussed: OAuth attestation draft, SD-JWT, SD-JWT VC, Status List & SPICE
     *   Budget
        *   Making sure enough budget for conformance suite tasks for VC stack
        *   Thinking of asking budget to organize atleast one interop events digitally between different implementers.
     *   Michael Jones made an announcement about JAPAN open ID summit https://www.openid.or.jp/summit/2024/en/
Website currently only talks about Friday, but missing companion events on Thursdays & Mondays( may be they are private events )

  *   PRs Discussed
     *   OpenID4VCI/pull/64<https://github.com/openid/OpenID4VCI/pull/64> - "clarify credential error response can be authorization or credential request error"
        *   Discussed on proposal to move make credential request error & authorization errors to one level higher.
           *   outcome: "agreed to move line #889 under #891."
        *   No need to put request changes for capitalization of terms - to save time
     *   OpenID4VCI/pull/65 <https://github.com/openid/OpenID4VCI/pull/65> "add identifiers for issuing credential of the same type, different content"
        *   suggestion to merge existing PR & create issue for outstanding discussion items in https://github.com/openid/OpenID4VCI/pull/65#pullrequestreview-1699358644
        *   discussed on "c_instance_identifier" name, suggestions for "credential_identifier"
        *   Paul will open issue with outstanding items & this PR will be approved
     *   OpenID4VCI/pull/86<https://github.com/openid/OpenID4VCI/pull/86> - "credentials Credentials Offer parameter values identifying credentials_supported object(s) in the issuer's metadata."
        *   on track for approval
        *   Discussed suggestion: using "credential_supported Identifier" as a key and making "credentials_supported" an object. Suggestion accepted since making it map will make it more cleaner.
        *   it is a breaking change to existing implementations - but it is an improvement
        *   discussed on how to handle issuer metadata breaking changes
           *   There is no implementation draft yet.
           *   Excercise caution before implementing before ID1 release.
        *   suggestion for issuer metadata data model versioning discussed - suggestion to create new issue to discuss this
        *   discussed about cutoff date for VCI spec
     *   Draft PR#78<https://github.com/openid/OpenID4VCI/pull/78> for issue OpenID4VCI/issues/72<https://github.com/openid/OpenID4VCI/issues/72> : "Credential Issuer using multiple authorization servers"
        *   Discussed declaring authorization servers as Array in server metadata for issuance and using hint inside credential offer for wallet to decide which authorization server to use.
Issues Discussed

     *   OpenID4VCI/issues/80<https://github.com/openid/OpenID4VCI/issues/80> : discussed "Binding Issuer to a service provider that the Issuer is using to host Issuer Metadata"
Cheers,
Kristina

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20231026/708512a3/attachment.html>