<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<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="Arial" size="2"><span style="font-size:10pt;">
<div>Dear all,</div>
<div> </div>
<div>Please find below the preliminary minutes of our call on Jan 8th 2019. In case of errors or misunderstandings, please let me know.</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<ol style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Roll Call<font color="black"> (extract from gotomeeting list of participants)</font></li></span></font>
</ol>
<div style="margin-top:5pt;margin-bottom:5pt;">John Bradley, Nat Sakimura, Philippe Clement (Orange), Bjorn Hjelm (Verizon), Brian Campbell (Ping Identity),<font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font>Petteri (Ubisecure), Dave.Tonge
(Moneyhub), Joseph</div>
<ol start="2" style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Adoption of the Agenda [Bjorn/John]</li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2" color="black"><span style="font-size:10pt;">Agreed</span></font></li><li style="margin-top:5pt;margin-bottom:5pt;"> </li><li style="margin-top:5pt;margin-bottom:5pt;">External Organizations</li></span></font>
</ol>
<ul style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">GSMA [Siva]</li></span></font>
</ul>
<div style="margin-top:5pt;margin-bottom:5pt;">N/A</div>
<ol start="4" style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Working Group Updates</li></span></font>
</ol>
<ul style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">FAPI WG [Dave]</li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2" color="black"><span style="font-size:10pt;">FAPI </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">CIBA </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">profile
</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">being processed</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">. Could have impacts on the MODRNA profile.</span></font></li></span></font>
</ul>
<ol start="5" style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Spec. Status</li></span></font>
</ol>
<ul style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">CIBA  Core/MODRNA Profile [Dave/Brian/Gonzalo/Axel]</li><li style="margin-top:5pt;margin-bottom:5pt;"> </li></span></font>
</ul>
<ul style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">CIBA Core relevant dates:</li></span></font>
</ul>
<ul style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Implementer’s Draft public review period: Friday, December 14, 2018 – Monday, January 28, 2019</li><li style="margin-top:5pt;margin-bottom:5pt;">Implementer’s Draft vote announcement: Monday, January 14, 2019</li><li style="margin-top:5pt;margin-bottom:5pt;">Implementer’s Draft voting period: Monday, January 21, 2019 – Monday, February 4, 2019</li></span></font>
</ul>
<ul style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Discussion on the process for addressing new issues received during the public review period</li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2" color="black"><span style="font-size:10pt;">Few of the</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;"> issues</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">
represent braking changes. Updates </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">will be</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;"> incorporated in the stable </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">version
</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">of the CIBA doc.</span></font></li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2" color="black"><span style="font-size:10pt;">Nat: </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">after </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">reread
the process document</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">, seems not wishable to start</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;"> another review period </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">after
the </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">first one</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">.</span></font></li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2" color="black"><span style="font-size:10pt;">Implementers draft </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">is aimed </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">mostly
</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">at</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;"> providing IPR protection. </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">In
case of </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">n</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">ot normative change</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">,</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">
no IPR impact</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">s</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;"> </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">are</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">
forecast</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">ed</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">.</span></font></li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2" color="black"><span style="font-size:10pt;">Rationale: every change has to be approved by the working group.</span></font></li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2" color="black"><span style="font-size:10pt;">The group decides that changes must be </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">written and </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">sent</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">
to the group</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;"> for acknowledgment</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">. If we need more time, the voting period could be delayed.
</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">(today this period </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">is supposed to begin on </span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">Jan
21</span></font><font face="Arial" size="1" color="black"><span style="font-size:6.65pt;"><sup>s</sup></span></font><font face="Arial" size="1" color="black"><span style="font-size:6.65pt;"><sup>)</sup></span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">.</span></font></li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Arial" size="2" color="black"><span style="font-size:10pt;">The agreed method is to e</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">xchange by mail to</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">
have a clear view for next Monday</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;"> a</span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">nd be sure to be confortable for Jan 21</span></font><font face="Arial" size="1" color="black"><span style="font-size:6.65pt;"><sup>st</sup></span></font><font face="Arial" size="2" color="black"><span style="font-size:10pt;">.</span></font></li></span></font>
</ul>
<ul style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Authentication Profile [Joerg]</li></span></font>
</ul>
<ol start="6" style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Issue Tracker</li></span></font>
</ol>
<ul style="margin:0;">
<font face="Calibri" size="2"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;"><a href="https://bitbucket.org/openid/mobile/issues?status=new&status=open&component=CIBA"><font color="blue"><u>CIBA Core</u></font></a><font color="#1F497D"> [Dave/Brian/Gonzalo/Axel]</font></li></span></font>
</ul>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://bitbucket.org/openid/mobile/issues/146/client_notification_token-seem-redundant"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;">#146:
client_notification_token seem redundant</span></font></a></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;">Brian: 1<font size="1"><span style="font-size:6.65pt;"><sup>st</sup></span></font> Suggestion to remove. Could it be still useful for some architecture ? leaning towards simplifying the spec by removing it. Removing
has implementation benefit. John suggests to not make a change until security review. After that, a simplification could occur. Not a great pressure to change it now.</div>
<div style="margin-top:5pt;margin-bottom:5pt;">General consensus: not make the change. Need more indeep review to find the marginal benefits of simplification.</div>
<ul style="margin:0;padding-left:72pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Brian to close it.</li></ul>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://bitbucket.org/openid/mobile/issues/147/ciba-grant-type-namespace"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;">#147:
CIBA Grant Type namespace</span></font></a></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;">Brian has a proposal and a change to make it more generic <font face="Wingdings">à</font> OK for the group</div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://bitbucket.org/openid/mobile/issues/148/ciba-openid-provider-metadata"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;">#148:
CIBA - OpenID Provider Metadata</span></font></a></span></font></div>
<ul style="margin:0;padding-left:72pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Brian to propose text, editorial change</li></ul>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://bitbucket.org/openid/mobile/issues/145/73-expires_in-and-interval-should-be"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;">#145:
7.3 expires_in and interval should be required to be integers</span></font></a></span></font></div>
<ul style="margin:0;padding-left:72pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Brian: Text will explicitely mention that. OK before the voting period</li></ul>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://bitbucket.org/openid/mobile/issues/149/ciba"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;">#149: CIBA:
login_hint_token_signing_algorithms_supported</span></font></a></span></font></div>
<ul style="margin:0;padding-left:72pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Issue to be closed</li></ul>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://bitbucket.org/openid/mobile/issues/144/clients-may-want-to-influence-lifetime-of"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;background-color:whitesmoke;">#144:
clients may want to influence lifetime of auth_req_id</span></font></a></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;">Some disagreements in seeing the client modify the lifetime. Adding a timeout ? maximum time to live ? </div>
<ul style="margin:0;padding-left:72pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Joseph to propose the text: parameter definition and how to use it, to the list. Before end of week</li></ul>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://bitbucket.org/openid/mobile/issues/135/token-endpoint-response-when-client-polls"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;background-color:whitesmoke;"><u>#135:
token endpoint response when client polls quicker than 'internal' may be unclear</u></span></font></a></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;">We should avoid on the server side to track the auth_request_id, that could be a burden. New error code ? Invalid grant ? Client is misbehaving. Is an explicit error better ?</div>
<ul style="margin:0;padding-left:72pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Joseph to propose text to solve the issue.</li></ul>
<div style="margin-top:5pt;margin-bottom:5pt;"> <a href="https://bitbucket.org/openid/mobile/issues/85/ciba-notifying-the-client-when-a-user"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;">#85: CIBA: Notifying the Client when
a user fails to authenticate</span></font></a></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://bitbucket.org/openid/mobile/issues/143/ciba-error-expired_token-in-the-push-mode"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;">#143:
CIBA: error=expired_token in the push mode</span></font></a></span></font></div>
<ul style="margin:0;padding-left:72pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Bjorn to resume issues and see with Brian and Dave to solve before next week</li></ul>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2"><span style="font-size:11pt;"><a href="https://bitbucket.org/openid/mobile/issues/133/binding_message-uses-possibly-undefined"><font face="Segoe UI" size="2" color="#172B4D"><span style="font-size:10.5pt;">#133:
binding_message uses possibly undefined "plain text" term</span></font></a></span></font></div>
<ul style="margin:0;padding-left:72pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">Dave and Brian To propose some text before the end of the week</li></ul>
<ul style="margin:0;">
<font face="Calibri" size="2"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;"><a href="https://bitbucket.org/openid/mobile/issues?status=new&status=open&component=MODRNA%20Profile%20CIBA"><font color="blue"><u>MODRNA </u></font><font color="blue"><u>CIBA Profile</u></font></a><font color="#1F497D"> 
[Dave/Brian/Gonzalo/Axel]</font></li><li style="margin-top:5pt;margin-bottom:5pt;"><a href="https://bitbucket.org/openid/mobile/issues?status=new&status=open&component=Authentication"><font color="blue"><u>Authentication Profile</u></font></a><font color="#1F497D"> [Joerg]</font></li></span></font>
</ul>
<ol start="7" style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">AOB</li></span></font>
</ol>
<div>We shouldn’t need a call next week, unless further mention on the list</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div>Best regards,</div>
<div>Philippe</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></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>