[Openid-specs-ab] Proposed agenda for 3-Apr-25 Connect WG call

[Michael Jones]

I propose this agenda for tomorrow's OpenID Connect working group call to be held at https://zoom.us/j/97622169761?pwd=ek5kZUg3QnI1cCt6bTE3QzA3ZVlOQT09.


  1.  Introductions
  2.  Antitrust Policy<https://www.openid.net/antitrust> and IPR Agreement<https://openid.net/wg/connect/> reminders
  3.  Events
     *   OpenID Workshop and IIW<https://internetidentityworkshop.com/>, Apr 7-10, Mountain View, California
        *   https://openid.net/attend-the-oidf-workshop-prior-to-iiw-spring-2025-on-7th-april-2025/
     *   OpenID Federation Interop, April 28-30, hosted by SUNET<https://www.sunet.se/> in Stockholm
        *   Sign up in the attendee spreadsheet<https://docs.google.com/spreadsheets/d/1zYl-wdzgyol9u3ho342GZhSsg0hhqqneJHlMXWJSIw0/edit?gid=25633585#gid=25633585>
        *   Run the Federation Certification Tests<https://openid.net/certification/federation_testing/>
  4.  Links to Active Specifications<https://openid.net/wg/connect/specifications/> and Repositories
     *   OpenID Connect Core incorporating errata 3<https://openid.net/specs/openid-connect-core-1_0-36.html> (repository<https://bitbucket.org/openid/connect/>)
     *   OpenID Connect Native SSO for Mobile Apps<https://openid.net/specs/openid-connect-native-sso-1_0.html> (repository<https://bitbucket.org/openid/connect>)
     *   OpenID Federation<https://openid.net/specs/openid-federation-1_0.html> (repository<https://github.com/openid/federation>)
     *   OpenID Federation Extended Subordinate Listing<https://openid.net/specs/openid-federation-extended-listing-1_0.html> (repository<https://github.com/openid/federation-extended-listing>)
     *   OpenID Federation Wallet Architectures<https://openid.net/specs/openid-federation-wallet-1_0.html> (repository<https://github.com/openid/federation-wallet>)
     *   OpenID Connect Relying Party Metadata Choices<https://openid.net/specs/openid-connect-rp-metadata-choices-1_0.html> (repository<https://github.com/openid/rp-metadata-choices>)
     *   OpenID Provider Commands<https://openid.net/specs/openid-provider-commands-1_0.html> (repository<https://github.com/openid/openid-provider-commands>)
  5.  OpenID Provider Commands<https://openid.net/specs/openid-provider-commands-1_0.html>
     *   Misc PR - expected to be non-controversial normative changes
        *   https://github.com/openid/openid-provider-commands/pull/12
     *   client_id / aud values
        *   https://github.com/openid/openid-provider-commands/issues/4
     *   async commands and notifications
        *   https://github.com/openid/openid-provider-commands/issues/5
        *   https://github.com/openid/openid-provider-commands/issues/7
     *   "roles" claim per IPSIE IL3
        *   https://github.com/openid/openid-provider-commands/issues/11
  6.  OpenID Federation<https://openid.net/specs/openid-federation-1_0.html>
     *   Coordination between DCP and Connect WGs on Client ID Values
        *   OpenID4VP's Client IDs<https://openid.net/specs/openid-4-verifiable-presentations-1_0-24.html#name-defined-client-identifier-s> and OpenID Federation's Client IDs<https://openid.net/specs/openid-federation-1_0-42.html#name-automatic-registration> are currently compatible
        *   An OpenID4VP PR<https://github.com/openid/OpenID4VP/pull/401> has proposed prefixing OpenID Federation Client ID values, which would be a breaking change to OpenID Federation
        *   An OpenID4VP PR-on-that-PR<https://github.com/openid/OpenID4VP/pull/468> has proposed making the prefix optional, which would make it a non-breaking change
        *   Joseph Heenan filed an OpenID Federation issue<https://github.com/openid/federation/issues/195> discussing the situation and possible choices
        *   Discussion
     *   <https://github.com/orgs/openid/projects/2/views/1> Other new Federation issues (time permitting)
        *   https://github.com/openid/federation/issues/192 - Trust Chain for Trust Anchor?
        *   https://github.com/openid/federation/issues/193 - Concerns around the practicality of the requirement for an empty json object on present entity type identifiers
        *   https://github.com/openid/federation/issues/194 - Suggest renaming trust_mark_id to better reflect its meaning
  7.  AOB

                                                                -- Mike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20250402/443c7d23/attachment.htm>