<div dir="ltr"><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername"></b> <span dir="ltr"><<a href="mailto:philippe.clement@orange.com">philippe.clement@orange.com</a>></span><br>Date: 2016-06-03 11:03 GMT+02:00<br>Subject: RE: MODRNA WG Call June 1st 2016<br>To: "<a href="mailto:Torsten.Lodderstedt@telekom.de">Torsten.Lodderstedt@telekom.de</a>" <<a href="mailto:Torsten.Lodderstedt@telekom.de">Torsten.Lodderstedt@telekom.de</a>>, "<a href="mailto:openid-specs-mobile-profile@lists.openid.net">openid-specs-mobile-profile@lists.openid.net</a>" <<a href="mailto:openid-specs-mobile-profile@lists.openid.net">openid-specs-mobile-profile@lists.openid.net</a>>, John Bradley <<a href="mailto:jbradley@mac.com">jbradley@mac.com</a>><br>Cc: "<a href="mailto:philippe.clement.ft@gmail.com">philippe.clement.ft@gmail.com</a>" <<a href="mailto:philippe.clement.ft@gmail.com">philippe.clement.ft@gmail.com</a>><br><br><br>
<div>
<font face="Arial" size="2"><span style="font-size:11pt">
<div><font color="#1F497D">Dear all,</font></div>
<div><font color="#1F497D"> </font></div>
<div><font color="#1F497D">Please consider below a new version of the minutes of our call, following some suggestions from Siva, and contribute if you feel you have to.</font></div>
<div><font color="#1F497D">Updates in <i>italics</i></font></div><span class="">
<div><font face="Calibri" color="#1F497D"> </font></div>
<div><font face="Calibri" color="#1F497D"><br>
<font face="Arial"><u>Participants</u></font><font face="Arial">: John, Bjorn, Nat, Philippe, Siva, Jörg</font></font></div>
</span><div><font face="Calibri" color="#1F497D"> <font face="Arial"><u>Agenda</u></font><font face="Arial"> : Progress on GSMA PCR portability, Change to MC Authorisaiton minutes</font></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#222222"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt">Some
discussions happened in CPAS about signing JWT and chain migration from a user to different MNOs</span></font></span></font></div><span class="">
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#500050"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt">John
explains that signing JWT is wishable and not complex for an MNO</span></font></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#500050"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt">An
introspection endpoint is needed on MNO side to attest the signed JWT to the RP. Keys rotating will be taken into account. Special keys for the Use Case ?</span></font></span></font></div>
</span><div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#222222"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt">Discussion
about the PCR and the fact it must be stable in time or different from an MNO to another regarding the same user at the same RP. The generality of the migration process is wishable, so addressing different PCR for the same user at an RP for different MNO is
acceptable. On the other hand, the MNO process to create PCR is not standardized yet, and no vision is available on the delay for all MNO to change their PCR method.</span></font></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#222222"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt"><i>Siva
informed forum members that CPAS members agreed the PCR new format (GUID, version 4, RFC 4112) and all MNOs will migrate to generate in this format, ( few MNOs are already working on this migration). PCR new format and migration is being executed as a separate
deployment project for the moment. (De-coupled from current Mobile Connect release).</i></span></font></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#222222"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt">Discussions
about the period while to maintain the migration open for a user at an MNO.</span></font></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#222222"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt"><i>John
explains that if we keep the same PCR for migration, then it will be Mobile Connect specific migration, and it cannot be made as a generic solution from OpenID Connect specifications. (Perhaps specs can come with multiple options/choice).</i></span></font></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#222222"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt">Chain
migration: discussions on the management of the signed JWT and which MNOs the JWTs will be addressed to. Proposal: sent each signed JWT to respective MNOs.</span></font></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#222222"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt"><i>Siva
informed forum members of changing the wording in the minutes regarding MC Authorisation since it is creating much confusion for R2 activities. Also informed that MC Authorisation is just a marketing term w.r.t. Mobile Connect, whereas it is “Contextual Authentication”
with additional features, which is well aligned with OIDC protocol and fit for purpose in R2. Joerg informed that there would not be a problem to change the minutes.</i></span></font></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#222222"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt"><i>If
agreed/required all Mobile Connect improvements/discussions apply to Mobile Connect future releases only.</i></span></font></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:38.25pt"><font size="3" color="#500050"><span style="font-size:12pt"><font face="Symbol">·</font><font face="Times New Roman" size="1"><span style="font-size:7pt"> </span></font><font size="2" color="#1F497D"><span style="font-size:11pt">Discussions
in CPAS to be led by Siva</span></font></span></font></div>
<div><font face="Calibri" color="#1F497D"> </font></div>
<div><font color="#1F497D">Best regards,</font></div>
<div><font color="#1F497D">Philippe</font></div>
<div><font face="Calibri" color="#1F497D"> </font></div>
<div><font face="Tahoma" size="2"><span style="font-size:10pt">_____________________________________________<br>
<b>De :</b> CLEMENT Philippe IMT TECHNO <br>
<b>Envoyé :</b> jeudi 2 juin 2016 09:41<br>
<b>À :</b> <a href="mailto:Torsten.Lodderstedt@telekom.de" target="_blank">Torsten.Lodderstedt@telekom.de</a>; <a href="mailto:openid-specs-mobile-profile@lists.openid.net" target="_blank">openid-specs-mobile-profile@lists.openid.net</a>; John Bradley<br>
<b>Cc :</b> <a href="mailto:philippe.clement.ft@gmail.com" target="_blank">philippe.clement.ft@gmail.com</a><br>
<b>Objet :</b> MODRNA WG Call June 1st 2016</span></font></div><div><div class="h5">
<div><font face="Calibri"> </font></div>
<div><font face="Calibri"> </font></div>
<div><font color="#1F497D">Dear all,</font></div>
<div><font color="#1F497D"> </font></div>
<div><font color="#1F497D">Please find below the preliminary notes of the meeting</font></div>
<div><font color="#1F497D">Any error or adjustment needed, please let me know</font></div>
<div><font color="#1F497D"> </font></div>
<div><font color="#1F497D"><u>Participants</u>: John, Bjorn, Nat, Philippe, Siva, Jörg</font></div>
<div><font color="#1F497D"> </font></div>
<div><font color="#1F497D"><u>Agenda</u> : Progress on GSMA PCR portability</font></div>
<div><font face="Calibri" color="#1F497D"> </font></div>
<div><font color="#1F497D">Some discussions happened in CPAS about signing JWT and chain migration from a user to different MNOs</font></div>
<div><font color="#1F497D">John explains that signing JWT is wishable and not complex for an MNO</font></div>
<div><font color="#1F497D">An introspection endpoint is needed on MNO side to attest the signed JWT to the RP. Keys rotating will be taken into account. Special keys for the Use Case ?</font></div>
<div><font color="#1F497D"> </font></div>
<div><font color="#1F497D">Discussion about the PCR and the fact it must be stable in time or different from an MNO to another regrding the same user at the same RP. The genericity of the migration process is wishable, so addressing different PCR for the same
user at an RP for different MNO is acceptable. On the other hand, the MNO process to create PCR is not standardized yet, and no vision is available on the delay for all MNO to change their PCR method.</font></div>
<div><font color="#1F497D">Discussions about the period while to maintain the migration open for a user at an MNO.</font></div>
<div><font color="#1F497D">Chain migration: discussions on the management of the signed JWT and which MNOs the JWTs will be addressed to. Proposal: sent each signed JWT to respective MNOs.</font></div>
<div><font color="#1F497D"> </font></div>
<ul style="margin:0;padding-left:36pt">
<font color="#1F497D">
<li>Discussions in CPAS to be led by Siva </li></font>
</ul>
<div><font face="Calibri" color="#1F497D"> </font></div>
<div><font color="#1F497D">Kind regards,</font></div>
<div><font color="#1F497D">Philippe</font></div>
<div><font color="#1F497D"> </font></div>
<div><font face="Tahoma" size="2"><span style="font-size:10pt">-----Rendez-vous d'origine-----<br>
<b>De :</b> <a href="mailto:Torsten.Lodderstedt@telekom.de" target="_blank"><font color="blue"><u>Torsten.Lodderstedt@telekom.de</u></font></a> [<a href="mailto:Torsten.Lodderstedt@telekom.de" target="_blank"><font color="blue"><u>mailto:Torsten.Lodderstedt@telekom.de</u></font></a>]
<br>
<b>Envoyé :</b> lundi 30 mai 2016 13:55<br>
<b>À :</b> <a href="mailto:Torsten.Lodderstedt@telekom.de" target="_blank"><font color="blue"><u>Torsten.Lodderstedt@telekom.de</u></font></a>; <a href="mailto:openid-specs-mobile-profile@lists.openid.net" target="_blank"><font color="blue"><u>openid-specs-mobile-profile@lists.openid.net</u></font></a><br>
<b>Objet :</b> [Openid-specs-mobile-profile] MODRNA WG Call<br>
<b>Date :</b> mercredi 1 juin 2016 16:00-17:00 (UTC+01:00) Amsterdam, Berlin, Berne, Rome, Stockholm, Vienne.<br>
<b>Où :</b> <a href="https://global.gotomeeting.com/join/927253461" target="_blank"><font color="blue"><u>https://global.gotomeeting.com/join/927253461</u></font></a></span></font></div>
<div><font face="Calibri"> </font></div>
<div><font face="Calibri"> </font></div>
<div><font face="Calibri"> </font></div>
<div><font face="Calibri"> </font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt">Zeit: Mittwoch, 1. Juni 2016 16:00-17:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt">Ort: <a href="https://global.gotomeeting.com/join/927253461" target="_blank"><font color="blue"><u>https://global.gotomeeting.com/join/927253461</u></font></a></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt">Hinweis: Die oben angegebene Abweichung von GMT berücksichtigt keine Anpassungen für Sommerzeit.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt">*~*~*~*~*~*~*~*~*~*</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt">Hi all,</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt">the objective of this call is to discuss the tasks we came up with during the technical workshop. Please take a look onto the respective issues in our tracker in advance: <a href="https://bitbucket.org/openid/mobile/issues?milestone=TWS_DA_05_2016" target="_blank"><font color="blue"><u>https://bitbucket.org/openid/mobile/issues?milestone=TWS_DA_05_2016</u></font></a></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt">best regards,</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt">Torsten.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:10pt"> << Fichier: ATT00001.txt >> </span></font></div>
<div><font face="Calibri"> </font></div>
</div></div></span></font><div><div class="h5">
<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></div></div></div>
</div><br></div>