<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Hi Torsten,</div>
<div><br>
</div>
<div>
<div>Sorry for the delay in the response. What I see is that time is going on and the only raised solution in the GSMA WG is to use the OneAPI Exchange to validate the client credentials, thus the vendors are going to implement this solution and then will be
more difficult to change. </div>
<div><br>
</div>
<div>I think that this topic should be in the Agenda of the GSMA WG every week or every two weeks because in that way the operators would be aware that we need to implement dynamic registration, I guess that no one is thinking about it. Maybe we can put this
topic in the agenda of our sync calls and circulate the results of the work that we can do here related to this topic.</div>
</div>
<div><br>
</div>
<div>Best,</div>
<div>Gonza.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">De: </span>Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>><br>
<span style="font-weight:bold">Fecha: </span>miércoles 1 de julio de 2015 14:21<br>
<span style="font-weight:bold">Para: </span>Gonzalo Fernandez Rodriguez <<a href="mailto:gonzalo.fernandezrodriguez@telefonica.com">gonzalo.fernandezrodriguez@telefonica.com</a>><br>
<span style="font-weight:bold">CC: </span>"<a href="mailto:t.lodderstedt@telekom.de">t.lodderstedt@telekom.de</a>" <<a href="mailto:t.lodderstedt@telekom.de">t.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>><br>
<span style="font-weight:bold">Asunto: </span>Re: [Openid-specs-mobile-profile] MODRNA WG Call<br>
</div>
<div><br>
</div>
<div>
<div dir="auto">
<div>Hi Gonzalo,</div>
<div><br>
</div>
<div>thanks for this information.</div>
<div><br>
</div>
<div>What is your proposal? How shall we proceed as a working group?</div>
<div><br>
</div>
<div>best regards,</div>
<div>Torsten.<br>
<br>
<br>
</div>
<div><br>
Am 01.07.2015 um 13:17 schrieb GONZALO FERNANDEZ RODRIGUEZ <<a href="mailto:gonzalo.fernandezrodriguez@telefonica.com">gonzalo.fernandezrodriguez@telefonica.com</a>>:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>Hi guys,</div>
<div><br>
</div>
<div>I will be travelling this afternoon to Barcelona. However I would like to remind you that the last week in the CPAS call I raised the importance to open a thread to work on the JWT statement (Jörg is aware) to be able to implement the dynamic registration
in Mobile Connect. The idea would be to work on this topic very close to the OIDF and to define how and where (OneAPIExchange, etc…) generate the JWT, my feeling is that this topic is stucked in the GSMA side and opening an specific threat there would help
to enforce the Dynamic registration feature in Mobile Connect.</div>
<div><br>
</div>
<div>Best,</div>
<div>Gonza.</div>
<div><br>
</div>
<div>
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">De: </span><a href="mailto:t.lodderstedt@telekom.de">t.lodderstedt@telekom.de</a><br>
<span style="font-weight:bold">Cuándo: </span>16:00 - 17:00 1 de julio de 2015 <br>
<span style="font-weight:bold">Asunto: </span>[Openid-specs-mobile-profile] MODRNA WG Call<br>
<span style="font-weight:bold">Ubicación: </span><a href="https://global.gotomeeting.com/join/764054389">https://global.gotomeeting.com/join/764054389</a><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">
<div>Zeit: Mittwoch, 1. 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">https://global.gotomeeting.com/join/764054389</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>please post your topic proposals to the list.</div>
<div></div>
<div>best regards,</div>
<div>Torsten.</div>
<div></div>
<div></div>
</span></font></div>
</div>
_______________________________________________ Openid-specs-mobile-profile mailing list
<a href="mailto:Openid-specs-mobile-profile@lists.openid.net">Openid-specs-mobile-profile@lists.openid.net</a><a href="http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile">http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile</a></div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la
lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.<br>
<br>
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a
leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição<br>
</font></div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Openid-specs-mobile-profile mailing list</span><br>
<span><a href="mailto:Openid-specs-mobile-profile@lists.openid.net">Openid-specs-mobile-profile@lists.openid.net</a></span><br>
<span><a href="http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile">http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile</a></span><br>
</div>
</blockquote>
</div>
</div>
</span><br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la
lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.<br>
<br>
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a
leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição<br>
</font>
</body>
</html>