[Openid-specs-mobile-profile] MODRNA WG Call on March 6th 2018 preliminary notes

philippe.clement at orange.com philippe.clement at orange.com
Tue Mar 6 16:53:54 UTC 2018


Dear all,
Please find the preliminary notes of our call on March 6th 2018.
In any case of error or misunderstanding, let me know first.

Agenda
1.      Roll Call
2.      Adoption of the Agenda [Bjorn/John]
3.      Liaisons Updates
a.      GSMA [Siva]
4.      Working Group Updates
a.      FAPI WG [John]
5.      Issue Tracker
a.      Authentication Profile [Jörg]
b.      CIBA [Gonzalo/Axel]
6.      Other
7.      AOB

Discussion
1.      Roll Call

 John Bradley, Celestin Bitjonck,  Dave Tonge,  Petteri Stenius (Ubisecure), Philippe Clement (Orange), Gonzalo (Telefonica),  Bjorn Hjelm (Verizon),  Jörg (DT)
2.      Adoption of the Agenda [Bjorn/John]

agreed
3.      Liaisons Updates
a.      GSMA [Siva]

Not adressed
4.      Working Group Updates
a.      FAPI WG [John]

Dave: following a last presentation, some issues arose. Likely some questions around to come and to address.
5.      Issue Tracker
a.      Authentication Profile [Jörg]
b.      CIBA [Gonzalo/Axel]

         No feedback currently following Gonzalo diffusion on the mailing list.
c.      Issue 52:

            GSMA approach is to not use CIBA with polling and let MC use pairwise identifiers. The choice inside Telefonica is to use pushing notifications in CIBA, and use JWK as URI as a sector identifier. With polling , using pairwise identifier is possible under the condition that client has registered JWK. The question appears to capture the future use of CIBA polling during the client registration phase, a kind of check to do. We need a separate doc, located in the CIBA spec. At the registration, the client would have to mention if he will use CIBA, to avoid some client registered with code flow use later on CIBA polling.  Question about a new grant type regarding CIBA. Do we let the possibility for a client to use polling but not pairwise identifier ? MNO use pairwise identifiers for all clients. The reason to use pairwise identifiers is to prevent the correlation of identifiers, instead of omnidirectional identifiers.

         --> Gonzalo to send a proposal of text modification, and collect feedback for the next meeting. In parallel, talks with the GSMA about this issue.
d.      Issue 54

         Discussion about Man In The Middle attacks. Dave suggests to send to the FAPI WG for comments.
         --> Gonzalo to send the modified text to the group
Best regards,
Philippe


_________________________________________________________________________________________________________________________

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/20180306/47891d36/attachment.html>


More information about the Openid-specs-mobile-profile mailing list