<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="Arial" size="2"><span style="font-size:10pt;">
<div>Dear all,</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div>Please find below the preliminary minutes of our call in object. Please let me know of any error or misunderstanding.</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><u>Participants</u> : Bjorn, John, Hubert, Jörg, Petteri, Philippe, Gonzalo, Siva</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><u>Agenda</u></div>
<ol style="margin:0;padding-left:36pt;">
<li>Roll Call</li><li>Adoption of the Agenda [Bjorn/John]</li><li>Meeting schedule – moving to Tuesday</li><li>Liaisons Updates</li></ol>
<ul style="margin:0;padding-left:18pt;">
<li>GSMA </li><li>Age Verification proposal [GSMA]</li><li>login_hint_token usage discussion [Joerg]</li></ul>
<ol start="5" style="margin:0;padding-left:36pt;">
<li>Events [Bjorn/John]</li></ol>
<ul style="margin:0;padding-left:18pt;">
<li>OpenID Foundation Workshop (Oct. 16)</li><li>IIW (Oct. 17-19)</li><li>MODRNA/FAPI Joint F2F WG</li></ul>
<ol start="6" style="margin:0;padding-left:36pt;">
<li>Issue Tracker [All]</li><li>AOB</li></ol>
<ul style="margin:0;padding-left:18pt;">
<li>Next steps for implementers draft towards final specs </li></ul>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><u>Discussion</u></div>
<ol style="margin:0;padding-left:18pt;">
<li>Roll Call</li></ol>
<ul style="margin:0;padding-left:54pt;">
<li>Done</li></ul>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<ol start="2" style="margin:0;padding-left:18pt;">
<li>Adoption of the Agenda [Bjorn/John]</li></ol>
<ul style="margin:0;padding-left:54pt;">
<li>approved and modified</li></ul>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<ol start="3" style="margin:0;padding-left:18pt;">
<li>Meeting schedule – moving to Tuesday</li></ol>
<div>OK for the group to change the schedule, no objection on the proposed slot. Starting on Tuesdays same time in 2 weeks (Oct 3<font size="1"><span style="font-size:6.65pt;"><sup>rd</sup></span></font>) .</div>
<ul style="margin:0;">
<li><font face="Wingdings">à</font> Bjorn to modify the schedule</li></ul>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<ol start="4" style="margin:0;padding-left:18pt;">
<li>Liaisons Updates</li></ol>
<ul style="margin:0;padding-left:54pt;">
<li>GSMA </li><li>login_hint_token usage discussion [Joerg]</li></ul>
<div>Jörg: discussions happened in CPAS to present the benefits of login_hint_token (LHT), well understood. Some underlying questions regarding on what channel the LHT can be used, front, back (device or server initiated), and the fact that the discovery service
is a different entity and could check LHT. The Request Object signed by a RP can also influence the usage of LHT, to adjust with CPAS people.</div>
<div>Siva: a decision on the LHT usage should be taken for Oct 27 in CPAS on how to use it.</div>
<div> Gonzalo mentions a potential overlapping in usage of LHT and encrypted MSISDN. A clear phasing should be presented between the 2 usages.</div>
<ul style="margin:0;padding-left:54pt;">
<li>Age Verification proposal [GSMA]</li></ul>
<div>Siva: age verification proposal (CPAS) depends upon countries and functional approach may be different: matching a number of completed years, requesting age or DoB, use an operator like “equal - less than…”. More than this, data quality is a problem, and
different standards and norms exist across countries. Not yet decided in CPAS, the willing is to combine all features in one product.</div>
<div>John: how to mix claim and metadata ? Siva: a new scope verification is under investigation.</div>
<div>In the IGov group, work with metadata is key. Any input from CPAS is a good starting point to compare and detect what is missing regarding IGov work. Example of Use case: Check the age over 13 to be allowed to create an account. </div>
<ul style="margin:0;padding-left:36pt;">
<li>Bjorn to send a link to the group regarding metadata work from NIST on age verification. </li></ul>
<div>link provided outside the meeting: <a href="https://www.nist.gov/itl/tig/attribute-metadata"><font color="blue"><u>NIST work on attribute metadata</u></font></a> and <a href="https://pages.nist.gov/NISTIR-8112/"><font color="blue"><u>NISTIR-8112</u></font></a>.</div>
<div> </div>
<ol start="5" style="margin:0;padding-left:18pt;">
<li>Events [Bjorn/John]</li></ol>
<ul style="margin:0;padding-left:54pt;">
<li>OpenID Foundation Workshop (Oct. 16)</li></ul>
<ul style="margin:0;padding-left:36pt;">
<li> Gonzalo and Axel to draft a presentation for CIBA. James presentation could be a trail.</li><li>John and Bjorn to work on a common paper</li></ul>
<ul style="margin:0;padding-left:54pt;">
<li>IIW (Oct. 17-19)</li><li>MODRNA/FAPI Joint F2F WG</li></ul>
<div>a date is suggested: nov 7<font size="1"><span style="font-size:6.65pt;"><sup>th</sup></span></font>to have a F2F FAPI meeting with MODRNA.</div>
<ul style="margin:0;padding-left:36pt;">
<li>Bjorn to work on an agenda for this.</li></ul>
<div>Do we want to have a meeting for only MODRNA members on the 6<font size="1"><span style="font-size:6.65pt;"><sup>th</sup></span></font> ? No objection for an additional F2F meeting.</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<ol start="6" style="margin:0;padding-left:18pt;">
<li>Issue Tracker [All]</li></ol>
<ul style="margin:0;padding-left:36pt;">
<li>#1: reassign issue 1 to UQ and close it.</li><li>#31: text proposed, close the issue (Jörg) </li><li>Bjorn to look to the issue tracker for remaining open points.</li></ul>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<ol start="7" style="margin:0;padding-left:18pt;">
<li>Implementer’s draft to final specs</li></ol>
<div>The process is as following (see the reference process in §5 in the <a href="https://openid.net/wordpress-content/uploads/2010/01/OpenID_Process_Document_December_2009_Final_Approved.pdf"><font color="blue"><u>process document</u></font></a>):</div>
<ul style="margin:0;padding-left:36pt;">
<li>The editors prepare a final draft (if not already done) and require comments/suggestions from the group to acquire consensus.</li><li>After consensus, editors and chairman request OIF secretary to start the 60 days review period.</li><li>15 days before the end of the 60 days review, and without any modification to the specs, the notice is sent to OIF members by OIF secretary to vote on the proposed final specs.</li><li>In case of any change, a new 60 days period re-starts.</li></ul>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div>Kind regards,</div>
<div>Philippe</div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Tahoma">-----Rendez-vous d'origine-----<br>
<b>De :</b> Hjelm, Bjorn [<a href="mailto:Bjorn.Hjelm@VerizonWireless.com">mailto:Bjorn.Hjelm@VerizonWireless.com</a>]
<br>
<b>Envoyé :</b> mardi 19 septembre 2017 20:53<br>
<b>À :</b> Hjelm, Bjorn; openid-specs-mobile-profile@lists.openid.net<br>
<b>Objet :</b> [Openid-specs-mobile-profile] Mobile Profile WG Call<br>
<b>Date :</b> mercredi 20 septembre 2017 16:00-17:00 Europe/Berlin.<br>
<b>Où :</b> <a href="https://global.gotomeeting.com/join/927253461">https://global.gotomeeting.com/join/927253461</a></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<a name="BM_BEGIN"></a>
<div>1. Please join my meeting, Sep 20, 2017 at 10:00 AM EDT. <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__global.gotomeeting.com_join_764054389&d=DwMFAw&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=NMZJHCV8pjvGIH2fTx9z6l7g7-V-a2xW7ISf9uHdz0A&m=J0DWk6nkvn-e6OVddI9KQX5pVkDQMAvfFJD1Y9BlqK8&s=qA2qzWR-93JuBQIYWslcOIjh0deNrKP6jFtmZoejQX0&e="><font color="blue"><u>https://global.gotomeeting.com/join/927253461</u></font></a></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div>2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.</div>
<div> </div>
<div> </div>
<div> </div>
<div>United States: +1 (626) 521-0013</div>
<div> </div>
<div>Australia: +61 2 8355 1034</div>
<div> </div>
<div>Austria: +43 (0) 7 2088 1036</div>
<div> </div>
<div>Belgium: +32 (0) 28 08 9460</div>
<div> </div>
<div>Canada: +1 (647) 497-9376</div>
<div> </div>
<div>Denmark: +45 (0) 89 88 03 61</div>
<div> </div>
<div>Finland: +358 (0) 942 45 0382</div>
<div> </div>
<div>France: +33 (0) 170 950 586</div>
<div> </div>
<div>Germany: +49 (0) 811 8899 6931</div>
<div> </div>
<div>Ireland: +353 (0) 15 255 598</div>
<div> </div>
<div>Italy: +39 0 694 80 31 28</div>
<div> </div>
<div>Netherlands: +31 (0) 208 084 055</div>
<div> </div>
<div>New Zealand: +64 (0) 9 887 3469</div>
<div> </div>
<div>Norway: +47 23 96 01 18</div>
<div> </div>
<div>Spain: +34 932 20 0506</div>
<div> </div>
<div>Sweden: +46 (0) 840 839 467</div>
<div> </div>
<div>Switzerland: +41 (0) 435 0824 78</div>
<div> </div>
<div>United Kingdom: +44 (0) 330 221 0098</div>
<div> </div>
<div> </div>
<div> </div>
<div>Access Code: 764-054-389</div>
<div> </div>
<div>Audio PIN: Shown after joining the meeting</div>
<div> </div>
<div> </div>
<div> </div>
<div><font face="Cambria" size="4" color="#365F91"><span style="font-size:14pt;"><b>Meeting ID: 927-253-461<br>
</b></span></font></div>
<div style="text-indent:-18pt;"><font face="Calibri" size="2"><span style="font-size:11pt;">GoToMeeting®<br>
</span></font></div>
<div style="text-indent:-18pt;"><font face="Calibri" size="2"><span style="font-size:11pt;">Online Meetings Made Easy®<br>
</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><br>
</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Not at your computer? Click the link to join this meeting from your iPhone®, iPad®, Android® or Windows Phone® device via the GoToMeeting app.<br>
</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> << Fichier: ATT00001.txt >> </span></font></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>