<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><font color="#1F497D">Dear all,</font></div>
<div><font color="#1F497D">Please find below the preliminary notes of our last call</font></div>
<div><font color="#1F497D">Any error or misunderstanding, please let me know</font></div>
<div> </div>
<div><font color="#1F497D">Participants: Torsten, Joerg, Bjorn, Gonzalo, Pam, Matthieu, Philippe</font></div>
<div> </div>
<div><font color="#1F497D"><u>Discovery spec</u></font></div>
<div><font color="#1F497D"><b>Building a list </b><b>of MNO</b>: from the disco service to the RP in case of discovery failure is under questioning. How to limit or filter this list if the disco service doesn’t have enough information to solve the disco feature?.
An alternative could be for the RP, in case of disco error, to redirect the user to the user endpoint.</font></div>
<div><font color="#1F497D"><b>MSISDN transfer:</b> Discussions and decision about the possibility of transfer of the MSISDN from the RP to the disco service. <b>Decision taken to adopt it</b>. Recommendations will be written for the usage of this feature at
the RP.</font></div>
<div><font color="#1F497D"><b>Account Chooser:</b> 2 new attributes are intended to help for Mobile Profile discovery: Token Hint (used by RP), and description (for readability of the user) both created by the MNO. Account chooser will not replace totally the
discovery, but will simplify the user experience. URL of the draft to the group for consultation: <a href="https://bitbucket.org/openid/ac/wiki/Login_Hint_Tokens"><font color="blue"><u>https://bitbucket.org/openid/ac/wiki/Login_Hint_Tokens</u></font></a> .</font></div>
<div><font color="#1F497D"> </font></div>
<a name="BM_BEGIN"></a>
<div><font color="#1F497D"><u>Registration spec</u></font></div>
<div><font color="#1F497D">One more change to do on the spec</font></div>
<div><font color="#1F497D">Bjorn proposes a dedicated session to discuss open issues</font></div>
<div> </div>
<div><font color="#1F497D"><u>Authentication spec</u></font></div>
<div><font color="#1F497D">Discussions going on with Sebastian and about the quality of authentication, 2 factors, one factor and LOA. The RP could notify some orientations for the MNO to conduct the authentication: define a requested authentication mean, a
number of factors… </font></div>
<div><font color="#1F497D">Document to be updated</font></div>
<div><font color="#1F497D"> </font></div>
<div><font color="#1F497D">Kind regards,</font></div>
<div><font color="#1F497D">Philippe</font></div>
<div> </div>
<div>Zeit: Mittwoch, 29. Juli 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 propose the following agenda:</div>
<div> </div>
<ol style="margin:0;padding-left:30pt;">
<li>discovery spec: go through tracker issues</li><li>Status registration spec</li><li>Status/next steps authentication spec</li></ol>
<div> </div>
<div>best regards,</div>
<div>Torsten.</div>
<div> </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>