[Openid-specs-ab] SIOP call agenda (2023-June-29) - 8AM PST

[Kristina Yasuda]

Hi All,

Below is a proposed agenda.

Please review the draft of the charter for a new WG dedicated to OpenID4VC work: https://docs.google.com/document/d/10pzVIpYF8gWVp2F6l0kinsBC9XVS5xZt4n55TzIcNLg/edit?usp=sharing
Few things to make up your mind on are: the name of the working group (transfer vs transport), and in-scope/out-of-scope items (there are few suggestions). Please also consider adding your name to the proposers 😊
The plan is to send this WG draft charter after the call on Thu, as mentioned during the last week’s call.

Please comment on the issuers, I tried identifying the outstanding ones below. some of them are blockers for the implementations, and we do not have enough time on the calls to cover them all.


- IPR reminder/Recording/Note-taking

- Introductions/re-introductions

- Agenda bashing/adoption

- Events/External orgs

- OID4VC Due Diligence Task Force kicked off at the Open Wallet Foundation<https://openwallet-foundation.github.io/tac/task-forces/OID4VC-due-diligence/> – great group of the implementers!

- OSW coming up (OAuth Security Workshop<https://oauth.secworkshop.events/osw2023>)

- Charter (see the note above)
- PRs https://bitbucket.org/openid/connect/pull-requests/ (please explicitly indicate approval/request for changes 😊)

  *   Want to merge PR 533 (got another question yesterday – really want to merge), 542, 543, 535 (please approve these three – don’t see a reason holding these up)
  *   Please review PRs 524, 520, 360, 536, 515, 487, 434, 468, 455
  *   Purely editorial: 545

- Issues https://bitbucket.org/openid/connect/issues?status=new&status=open&component=SIOP&component=Verifiable%20Presentation&component=Credential%20Issuance

  *   https://bitbucket.org/openid/connect/issues/1920/add-sd-jwt-credential-format-profile-to

     *   Need agreement that this is ready for PR

  *   https://bitbucket.org/openid/connect/issues/1923/oid4vci-enable-issuance-of-the-same

     *   Needs discussion. This is a problem

  *   https://bitbucket.org/openid/connect/issues/1969/wallet-instance-attestation-for-openid4vci
  *   https://bitbucket.org/openid/connect/issues/1964/size-of-a-credential-issuer-metadata

     *   Somewhat a blocker for one implementation

  *   https://bitbucket.org/openid/connect/issues/1965/logo-uri-in-the-credentials_supported
  *   https://bitbucket.org/openid/connect/issues/1960/oid4vci-align-credential-format

     *   Would like clarity if there is consensus to use media types `vc+sd-jwt` as credential format identifiers

  *   https://bitbucket.org/openid/connect/issues/1940/is-the-acceptance-token-one-time-use

     *   Need direction if “Will it be mentioned in the spec that it is one-time use, or is that not important?”

  *   https://bitbucket.org/openid/connect/issues/1922/oid4vci-unique-id-for-each-element-in

     *   Need consensus that we are not following this path (which seems to be the direction, I might be wrong)

  *   https://bitbucket.org/openid/connect/issues/1929/oid4vci-notification-of-acceptance
  *   `kid` in https://bitbucket.org/openid/connect/issues/1932/oid4vci-cwt-proof-requirements
  *   etc
- AOB



Best,

Kristina




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