[Openid-specs-mobile-profile] MODRNA WG @ Tue Feb 1, 2022 preliminary minutes

[philippe.clement at orange.com]

Dear all,
Please find below the preliminary minutes of our call on Tue Feb 1, 2022, and let me know of any error or misunderstanding.


 Roll Call
Bjorn Hjelm (Verizon), Philippe Clement, Joseph Heenan (Authlete / OIDF), Martin Drewes (enabled World), Gail Hodges (OIDF)

Adoption of the Agenda [Bjorn/John]
agreed

External Organizations
o       GSMA

          No update. Trying to establish a liaison. Other possible trail is to collaborate in other working groups
o       ETSI

          OIDC could be an actor in the EU wallet. A template for a liaison agreement is on the table.

Events
o       OIX 2022 Trust Framework Launch<https://openidentityexchange.org/networks/87/events.html?id=4724>, Feb. 3, 2022
o       OpenID Foundation Workshop Spring, Mountain View, CA, Apr. 25, 2022
o       IIW Spring, Mountain View, CA, Apr. 26-28, 2022
o       OAuth Security Workshop<https://oauth.secworkshop.events/>, Trondheim, Norway, May 4-6, 2022
o       European Identity and Cloud Conference (EIC)<https://www.kuppingercole.com/events/eic2022>, Berlin, Germany, May 10-13, 2022
o       RSA<https://www.rsaconference.com/usa>, San Francisco, CA, Jun. 6-9, 2022
o       Identiverse<https://identiverse.com/>, Dencer, CO, Jun. 20-23, 2022

Specification Status
o       MODRNA CIBA Profile<https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?url=https://bitbucket.org/openid/mobile/raw/master/openid-connect-modrna-client-initiated-backchannel-authentication-profile-1_0.xml&modeAsFormat=html%2Fascii&type=ascii&Submit=Submit>

OpenID Certification<https://openid.net/certification/> for MODRNA
Contribution from MODRNA to the certification working group under investigation.

==>     Philippe: Question Hubert on available resources for moving forward certification of User Questioning API.

Issue Tracker<https://bitbucket.org/openid/mobile/issues?status=new&status=open>
o       FAPI Issue #466<https://bitbucket.org/openid/fapi/issues/466/proposal-for-fapi-dcr-dcm-dynamic-client> (DCR), #467<https://bitbucket.org/openid/fapi/issues/467/can-fapi-specs-support-ecosystems-where> (USSD)

          #466: Proposal for FAPI DCR/DCM (Dynamic Client Registration/Management) profile<https://bitbucket.org/openid/fapi/issues/466/proposal-for-fapi-dcr-dcm-dynamic-client>
          Using a software statement for client registration is envisioned by different groups. Revocation of software Statement is also under questioning. A collaboration must be envisioned for this topic

          #467: Can FAPI specs support ecosystems where smart phones aren't common, e.g. by using USSD<https://bitbucket.org/openid/fapi/issues/467/can-fapi-specs-support-ecosystems-where>
          Some Mobile operators use this protocol for different use cases, for example validate payments.
==>     Bjorn to start a discussion by email.


AOB
Martin joined the group regarding USSD usage, especially in Africa and security concerns.
==>     Bjorn to start a conversation by mail with Orange people.

Gail presented different options of liaison/collaboration with other bodies like GSMA, ETSI to scale adoption of OIDF standards to serve "mobile network linked" use cases. Social inclusion is also at stake regarding emerging markets using USSD.

Best regards,
Philippe

Orange Restricted


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-mobile-profile/attachments/20220201/e32b7d0f/attachment.html>