<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="Calibri" size="2"><span style="font-size:11pt;">
<div>Please find below the preliminary notes of the call. </div>
<div>Should you detect any error or misunderstanding, please let me know.</div>
<a name="BM_BEGIN"></a>
<div> </div>
<div><u>Participants</u> : John, Axel, Bjorn, Charles, Torsten, Joerg</div>
<div> </div>
<div><u>Agenda :</u></div>
<div> </div>
<ul style="margin:0;padding-left:36pt;">
<li>Review UQ specs</li><li>Review SIBA specs</li><li>Next workshop</li></ul>
<div> </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"><u>Disc</u><u>ussion :</u></span></font></div>
<div><b>User Questionning</b></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">A new draft has been released by Orange, following questions/remarks from Torsten</span></font></div>
<div><b> </b>Axel and Bjorn volunteer to review the UQ draft specs. </div>
<div>Torsten to send a reminder to the list for reviewing, before entering the implementers draft process.</div>
<div>A proposal is made for OIF to present a status update of UQ work at the next PET GSMA meeting (end of November). Orange will help to draft this presentation. PET chairman to be contacted for insertion into the agenda. </div>
<div> </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"><b>SIBA</b></span></font></div>
<div>Questions about the context parameter that shows up in the specs. Discussions in Paris had only stated a use for the binding message to interlock devices. Recommendation from the call is to remove this parameter. </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">Charles volunteers to post comments on SIBA specs, other comments are awaited from the list.</span></font></div>
<div>Mentionning the Use Cases in SIBA specs is requested to understand some choices in the specs, and will avoid any duplication with User Questionning.</div>
<div> </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">Idea of merging some parts of SIBA and UQ are set on the table, but draft specs should be more mature.</span></font></div>
<div> </div>
<div><b>Next workshop</b></div>
<div>For information, John should be in London January 18 and 19<font size="1"><span style="font-size:7.3pt;"><sup>th</sup></span></font>, to take into consideration.</div>
<div> </div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"><b>AOB: push style</b></span></font></div>
<div>Discussion occurs on OAuth list regarding push style for the device flow.</div>
<div>Some arguments are presented to balance push vs pull approach, for UQ.</div>
<ul style="margin:0;padding-left:36pt;">
<li>Complexity for the RP to implement 2 solutions</li><li>Resource optimization from an OP side</li><li>Number of requests per second</li><li>Delay for the user to answer the question (seconds, minutes ?)</li></ul>
<div>Discussion to be continued on the list through the specs</div>
<div> </div>
<div>Best regards,</div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">Philippe</span></font></div>
<div> </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>