<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>Please find below the preliminary notes of our call today. Any error or misunderstanding, please let me know.</div>
<a name="BM_BEGIN"></a>
<div style="margin-top:24pt;"><font face="Cambria" size="4" color="#365F91"><span style="font-size:14pt;"><b>Agenda</b></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Roll Call</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Adoption of the Agenda [Bjorn/John]</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Liaisons Updates</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">GSMA [Siva]</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Working Group Updates</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">FAPI WG</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Issue Tracker</span></font></div>
<div>Authentication profile</div>
<div>AOB</div>
<div><font face="Calibri" size="2" color="#365F91"><span style="font-size:11pt;"> </span></font></div>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>Roll Call</b></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">John, Gonzalo, Hubert, Jörg, MG, Petteri, Philippe, Bjorn,</span></font></div>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>Adoption of the Agenda [Bjorn/John]</b></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Agreed, no addition.</span></font></div>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>Liaisons Updates</b></span></font></div>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>GSMA [Siva]</b></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Siva not on the call.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Hubert mentions Orange, Telefonica and Telstra paper for usage of UQ api. </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">UQ paper pushed to FAPI group, one brief discussion with Dave T before end of year. </span></font></div>
<ul style="margin:0;padding-left:36pt;">
<font face="Calibri" size="2"><span style="font-size:11pt;">
<li>Bjorn to question Nat for the progress on it. </li></span></font>
</ul>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>Working Group Updates</b></span></font></div>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>FAPI WG</b></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">FAPI & OB workshop 2 weeks ago in London</span></font></div>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>Issue Tracker</b><font color="black"><b> (Jörg)</b></font></span></font></div>
<ul style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">#33: modrna – claim: I would vote to not put this into the basic authentication spec. In my opinion the topic here is about authorization of a transaction not about authenticating a user.</li><li style="margin-top:5pt;margin-bottom:5pt;"> </li><li style="margin-top:5pt;margin-bottom:5pt;">#22: is actually about the same thing. So I would vote to merge #32 and #22 an consider an additional document to handle those transactional authorizations.</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;">#38: amr values. Those are not really specific to mobile connect so they should be addressed in RFC 8176.</li><li style="margin-top:5pt;margin-bottom:5pt;">Changing an RFC is not possible, but adding a doc <font color="black">i</font>s, maybe external.</li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Wingdings">à</font><font color="black"> </font>To collect possible amr first</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;">#39: error handling: We really should reserve some time to discuss this during a WG call</li><li style="margin-top:5pt;margin-bottom:5pt;">Some people think the RP has to check if the returned info are acceptable and that it should be up to the RP to decide according the returned info. Other ones think that error handling has a benefit.</li><li style="margin-top:5pt;margin-bottom:5pt;"><font color="black">A case is discussed regarding the request of a certain acr by the RP.</font></li><li style="margin-top:5pt;margin-bottom:5pt;">5.5.1.1 of the OIDC spec specifies <font color="black">how to deal with requested acr claim from the RP, should it be essential or requested by acr_values for the id_token</font>.</li></span></font>
</ul>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;"><font face="Wingdings">à</font> Discussion to be continued on the next call and mailing list.</span></font></div>
<ul style="margin:0;">
<font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">
<li style="margin-top:5pt;margin-bottom:5pt;">#40: loa4 handling: We could take the approach from the current mobile connect profile here. (And pull it down to the MODRNA spec)</li><li style="margin-top:5pt;margin-bottom:5pt;">No possible implementation of mobile connect to make that. Try to be more specific on what is behind LOA4. </li><li style="margin-top:5pt;margin-bottom:5pt;">Wait for IGov WG conclusions, according to a LOA4 profile. IGov document covering highest level assurance.</li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Wingdings">à</font><font color="black"> </font>Keep it open for now </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;">#42: pcr as login hint: I would vote to close this issue. In the next version Mobile Connect Profile will support MODRNA login_hint_token.</li><li style="margin-top:5pt;margin-bottom:5pt;">Pcr, a concept of MC (personal customer reference). No more needed since MC supports the LHT.</li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Wingdings">à</font> To be closed</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;">#43: phishing: I am really no expert on phishing. John should take a look at it.</li><li style="margin-top:5pt;margin-bottom:5pt;">Session highjacking is more appropriate.</li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Wingdings">à</font> Issue assigned to John for comment</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;">#61: OpenAPI respresentation: Still waiting for Nat’s reply here.</li><li style="margin-top:5pt;margin-bottom:5pt;"><font face="Wingdings">à</font> Bjorn to ping Nat on this.</li></span></font>
</ul>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>Authentication Profile</b></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">For the next call</span></font></div>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>Other</b></span></font></div>
<div style="margin-top:10pt;"><font face="Cambria" size="3" color="#4F81BD"><span style="font-size:13pt;"><b>AOB</b></span></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>
<div>Best regards,</div>
<div>Philippe</div>
<div> </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>