[Openid-specs-mobile-profile] [E] Re: MODRNA WG @ Tue Jan 18, 2022 preliminary minutes
Hjelm, Bjorn
bjorn.hjelm at verizonwireless.com
Thu Jan 20 02:00:58 UTC 2022
Gail,
With the modular approach to (GSMA) Mobile Connect, USSD was one of the
authentication methods included (see
https://www.gsma.com/identity/wp-content/uploads/2016/10/MC_high-security-authentication_Sep-16.pdf).
I don't know the specific details (or assumptions) for Open Banking Nigeria
but it sounds like the MNOs do play a role in the authentication process
which isn't uncommon.
>From the MODRNA working group perspective, we're happy to support the
discussions and share our knowledge.
BR,
Bjorn
On Wed, Jan 19, 2022 at 11:55 AM Gail Hodges <gail.hodges at oidf.org> wrote:
> Hi Bjorn, Nat
>
>
>
> The ask arose during my conversation with Open Banking Nigeria yesterday.
> Open Banking Nigeria and the Nigerian government have a requirement to
> serve users with feature phones, that comprise 40% of their population in
> Nigeria, and of course a large share of all African users. They are keen to
> know if FAPI is extensible to serve this population so they can offer Open
> Banking services to them as well.
>
>
>
> I encouraged Open Banking Nigeria to join the FAPI WG calls, but perhaps
> both FAPI and MODRNA WGs will be relevant to them thanks to your exchange
> below. For noting, the FAPI WG has already raised an issue here on this
> ask:
> https://bitbucket.org/openid/fapi/issues/467/can-fapi-specs-support-ecosystems-where
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__bitbucket.org_openid_fapi_issues_467_can-2Dfapi-2Dspecs-2Dsupport-2Decosystems-2Dwhere&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=sskifA7gbavH_AtT2E9qOlz4s3Xup0QAb9pboXIQh0g&s=ICtYLnrqaeI2K2YtYLVaP-lvGMyBUa7BLq3TZjpwbXU&e=>
> I don’t know if Moderna want to link to same issue or needs their own?
>
>
>
> The next step is to reconvene in 2 weeks with the leadership of Open
> Banking Nigeria, then have an education session with the wider Open Banking
> Nigeria team. I think for the next couple conversations it would be great
> to have a technical volunteer or WG chair from both FAPI and MODRNA who
> could join these sessions. Right now, in their own words, they need to
> “come up the learning curve” still and these conversations will probably be
> necessary before they will join WGs.
>
>
>
> Gail
>
>
>
>
>
>
>
> *From: *Openid-specs-mobile-profile <
> openid-specs-mobile-profile-bounces at lists.openid.net> on behalf of
> "Hjelm, Bjorn via Openid-specs-mobile-profile" <
> openid-specs-mobile-profile at lists.openid.net>
> *Reply-To: *bjorn_hjelm_fwd <bjorn.hjelm at verizonwireless.com>
> *Date: *Wednesday, January 19, 2022 at 6:58 AM
> *To: *nat_fwd <nat at nat.consulting>, Openid-specs-mobile-profile <
> openid-specs-mobile-profile at lists.openid.net>
> *Cc: *Dave Tonge <dave.tonge at moneyhub.com>, Joseph Heenan <
> joseph.heenan at fintechlabs.io>
> *Subject: *Re: [Openid-specs-mobile-profile] [E] Re: MODRNA WG @ Tue Jan
> 18, 2022 preliminary minutes
>
>
>
> Nat,
>
> Yes, USSD is used by MNOs and one of the authentication methods for Mobile
> Connect. We would be happy to include this topic in our discussion if you
> would be able to attend and present the use case.
>
>
> BR,
>
> Bjorn
>
>
>
>
>
> On Wed, Jan 19, 2022 at 5:13 AM Nat Sakimura <nat at nat.consulting> wrote:
>
> Thanks for the update and sorry for missing the call. It starts at
> midnight for me and hopefully you understand.
>
>
>
> This morning I got a request from Africa asking for the support of ussd as
> a substrate protocol. I've been using ussd as part of the payment protocols
> and so forth in Africa but I have very limited knowledge of it from the
> technical point of view. Although the request has come to the FAPI WG, I
> suppose the most expert knowledge resides in Modrna working group.
>
>
>
> Let me know of your gut feeling about the potentials.
>
>
>
> Best regards,
>
>
>
> Nat sakamura
>
>
>
> 2022年1月19日(水) 0:56 <philippe.clement at orange.com>:
>
> Dear all,
>
> Please find below the preliminary minutes of our MODRNA call on Tue Jan
> 18, 2022., and let me know of any error or misunderstanding
>
>
>
> Roll Call
>
> Bjorn Hjelm (Verizon), Philippe Clément, Joseph Heenan (Authlete OIDF),
> Mike Leszcz, Dave Tonge,
>
> Adoption of the Agenda [Bjorn/John]
>
> Agreed.
>
> External Organizations
>
> - GSMA
>
> No update nor feedback, about ZenKey presentation
>
> Events
>
> - RSA
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rsaconference.com_usa&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=Mk8JJdwesFQk7HBX6vtfKcp0mDM_3mRPYzxLaTHr_ts&s=edAAK3MaOKNjugf5UWLEI5yFtl4YWn-2u_hsB3vm46g&e=>,
> Feb. 7-10, 2022 – June 6-9
>
> Specification Status
>
> - MODRNA CIBA Profile
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__xml2rfc.tools.ietf.org_cgi-2Dbin_xml2rfc.cgi-3Furl-3Dhttps-3A__bitbucket.org_openid_mobile_raw_master_openid-2Dconnect-2Dmodrna-2Dclient-2Dinitiated-2Dbackchannel-2Dauthentication-2Dprofile-2D1-5F0.xml-26modeAsFormat-3Dhtml-252Fascii-26type-3Dascii-26Submit-3DSubmit&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=Mk8JJdwesFQk7HBX6vtfKcp0mDM_3mRPYzxLaTHr_ts&s=7J0XeEiYk_N0AyXWxof7EQYTPoDT0SjKShtPxvFmsgs&e=>
>
> Dave posted a draft PR (see issue below).
>
> OpenID Certification
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__openid.net_certification_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=Mk8JJdwesFQk7HBX6vtfKcp0mDM_3mRPYzxLaTHr_ts&s=JGBY0HwDoZ4gTQOlfwyh4TaAE_W7_xPvORIU_ZOAcW8&e=>
> for MODRNA
>
> Joseph, Mike: investigations to see how to start a certification for
> MODRNA. Other tasks scheduled in Q1 on FAPI CIBA.
>
> - Bjorn to reach out to Hubert for Orange position regarding
> certification and questioning API.
> - Bjorn to ask to Mike if ZenKey can participate in the certification
> program
>
> Issue Tracker
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__bitbucket.org_openid_mobile_issues-3Fstatus-3Dnew-26status-3Dopen&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=Mk8JJdwesFQk7HBX6vtfKcp0mDM_3mRPYzxLaTHr_ts&s=dHFZ5BFg-PBN9KrmMcy4LAjDDijJAxCyfAYcjZYgM70&e=>
>
> Dave created a PR (
> https://bitbucket.org/openid/mobile/pull-requests/17/fix-references
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__bitbucket.org_openid_mobile_pull-2Drequests_17_fix-2Dreferences&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=Mk8JJdwesFQk7HBX6vtfKcp0mDM_3mRPYzxLaTHr_ts&s=dnECW9Wi2Gkhxtt58Jiv8MUTcB3Ruv1kSxCua5wgFL4&e=>)
> for following issue:
>
> #207: Normative reference not in specification body
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__bitbucket.org_openid_mobile_issues_207_normative-2Dreference-2Dnot-2Din-2Dspecification&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=Mk8JJdwesFQk7HBX6vtfKcp0mDM_3mRPYzxLaTHr_ts&s=Cd8Cc63y-u_NSm0UtQuS98qGbZTudra10IWYeAaxohc&e=>
>
> We can remove the reference because it is covered in the core spec.
>
> AOB
>
> NOB
>
>
>
>
>
>
>
> 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.
>
> _______________________________________________
> Openid-specs-mobile-profile mailing list
> Openid-specs-mobile-profile at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openid.net_mailman_listinfo_openid-2Dspecs-2Dmobile-2Dprofile&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=Mk8JJdwesFQk7HBX6vtfKcp0mDM_3mRPYzxLaTHr_ts&s=--hxQe7OyUdA3iv71BMVWmiQSEFK4FCf75bHiRPax-k&e=>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-mobile-profile/attachments/20220119/c0b66cf5/attachment-0001.html>
More information about the Openid-specs-mobile-profile
mailing list