<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>Dear all,</div>
<div> </div>
<div>Please find below the preliminary notes of our Wednesday call.</div>
<div>In case of any error or missing information, please let me know</div>
<div> </div>
<div><u>Participants :</u></div>
<a name="BM_BEGIN"></a>
<div>Joerg Connotte</div>
<div>John Bradley</div>
<div>Bjorn Helm</div>
<div>Matthieu Verdier</div>
<div>Sebastian Ebling</div>
<div>Roland Edberg</div>
<div>Nat Sakimura</div>
<div> </div>
<div><u>Agenda:</u></div>
<ul style="margin:0;padding-left:30pt;">
<li>Discussion of discovery design (native vs. web – probably using sequence diagrams)</li><li>Status of registration spec (esp. software statement contents)</li><li>Alignment of GSMA work and authentication draft</li></ul>
<div><font color="#1F497D"> </font></div>
<div><u>Discovery specs</u></div>
<ul style="margin:0;padding-left:36pt;">
<li>sequence diagram to be done</li><li>discussions on a Use Case where the requester device is not the authentication device, even if it has Mobile Network support</li><li>Discussions on MSISDN liability when issued from a RP, some RPs will demand that “this” MISDN recorded during customer enrolment under a controlled process MUST be the one used to a 2<font size="1"><span style="font-size:7.3pt;"><sup>nd</sup></span></font>
factor authentication. Some others will only indicate that they have a presumption that “this” MSISDN could be the one to use.</li></ul>
<div> </div>
<div>Joerg mentions that GSMA presents a login page where options are presented to user</div>
<div> </div>
<div>Discussions about the syntax defined for claims value that could help in passing MSISDN, usage could depend upon single or multiple factor authentication</div>
<div> </div>
<div><u>Registration spec</u><u>s</u></div>
<div>Section 3.1 , done in text mode</div>
<div>Access to bitbucket to be posted on the mailing list</div>
<div> </div>
<div><u>Alignment of GSMA work and authentication specs</u></div>
<div>Joerg is discussing with Gautam</div>
<div> </div>
<div><u>Information:</u></div>
<div>JOSE and JWT accepted by IETF</div>
<div> </div>
<div>Best regards,</div>
<div>Philippe</div>
<div> </div>
<div>Zeit: Mittwoch, 20. Mai 2015 16:00-17:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien.</div>
<div>Ort: <a href="https://global.gotomeeting.com/join/764054389"><font color="blue"><u>https://global.gotomeeting.com/join/764054389</u></font></a></div>
<div> </div>
<div>Hinweis: Die oben angegebene Abweichung von GMT berücksichtigt keine Anpassungen für Sommerzeit.</div>
<div> </div>
<div>*~*~*~*~*~*~*~*~*~*</div>
<div> </div>
<div>Hi all,</div>
<div> </div>
<div>I won’t be able to attend but John will moderate the call instead (thanks!).</div>
<div> </div>
<div>I would suggest the following topics:</div>
<ul style="margin:0;padding-left:30pt;">
<li>Discussion of discovery design (native vs. web – probably using sequence diagrams)</li><li>Status of registration spec (esp. software statement contents)</li><li>Alignment of GSMA work and authentication draft</li></ul>
<div> </div>
<div>best regards,</div>
<div>Torsten.</div>
<div> << Fichier: ATT00001.txt >> </div>
<div> </div>
</span></font>
<PRE>_________________________________________________________________________________________________________________________
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.
</PRE></body>
</html>