[Openid-specs-mobile-profile] minutes of MODRNA WG Call Nov 16th 2016

Fri Nov 18 14:28:34 UTC 2016

Hi Philippe,

re peer review: Yes, I have specific features in mind:
- error/status indication in response
- response parameters (header vs body)
- dynamic vs. static endpoints for polling

I already wrote an e-Mail to the authors and described my concerns.

best regard,
Torsten.

Am 18.11.2016 um 23:01 schrieb philippe.clement at orange.com:
>
> Hi Torsten,
>
> _“Peer review”_: Will add this to the minutes.
>
> However, we only had on this call attendance from UQ people, so we 
> only noticed a commitment from orange to have a review on SIBA.
>
> __
>
> _“Currently these specs solve the same problem differently”_: I’m not 
> sure, because we only have Use Cases from UQ and comparing is more 
> than difficult. On the other hand, we stated clearly in Paris the 
> perimeter of User Questionning, different of server side 
> authentication. But maybe you have in mind a specific feature in the 2 
> specs ?
>
> __
>
> _“Send a note to the OpenId Connect list”: _will add this to the minutes
>
> __
>
> _“Ask this WG to review UQ”:_already mentioned in the minutes
>
> _“we agreed I would ask Gautam whether we would give a presentation on 
> our joined work”_
>
> Correct.  Will update the minutes. Due to the fact that putting an 
> item in the agenda is in the hand of PET chairman, will propose in a 
> subsequent mail to ask to the PET chairman to insert this item in the 
> agenda.
>
> Kind regards,
>
> Philippe
>
> *De :*Torsten.Lodderstedt at telekom.de 
> [mailto:Torsten.Lodderstedt at telekom.de]
> *Envoyé :* vendredi 18 novembre 2016 12:06
> *À :* CLEMENT Philippe IMT TECHNO
> *Cc :* openid-specs-mobile-profile at lists.openid.net
> *Objet :* AW: minutes of MODRNA WG Call Nov 16th 2016
>
> Hi Philippe,
>
> I proposed the authors of SIBA and UQ should conduct a peer review of 
> the respective other spec in order to align on use of certain 
> patterns. Currently these specs solve the same problem differently. I 
> promised to get in contact with the authors. The call attendees agreed.
>
> We also agreed to send a note to the OpenId Connect list and ask this 
> WG to review UQ.
>
> Re PET meeting: we agreed I would ask Gautam whether we would give a 
> presentation on our joined work. I cannot remember we mentioned the 
> PET chairman.
>
> best regards,
>
> Torsten.
>
> *Von:*philippe.clement at orange.com <mailto:philippe.clement at orange.com> 
> [mailto:philippe.clement at orange.com]
> *Gesendet:* Donnerstag, 17. November 2016 02:07
> *An:* Lodderstedt, Torsten; 
> openid-specs-mobile-profile at lists.openid.net 
> <mailto:openid-specs-mobile-profile at lists.openid.net>
> *Betreff:* minutes of MODRNA WG Call Nov 16th 2016
>
> Please find below the preliminary notes of the call.
>
> Should you detect any error or misunderstanding, please let me know.
>
> _Participants_ : John, Axel, Bjorn, Charles, Torsten, Joerg
>
> _Agenda :_
>
> ·Review UQ specs
>
> ·Review SIBA specs
>
> ·Next workshop
>
> _Discussion :_
>
> *User Questionning*
>
> A new draft has been released by Orange, following questions/remarks 
> from Torsten
>
> Axel and Bjorn volunteer to review the UQ draft specs.
>
> Torsten to send a reminder to the list for reviewing, before entering 
> the implementers draft process.
>
> 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.
>
> *SIBA*
>
> 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.
>
> Charles volunteers to post comments on SIBA specs, other comments are 
> awaited from the list.
>
> Mentionning the Use Cases in SIBA specs is requested to understand 
> some choices in the specs, and will avoid any duplication with User 
> Questionning.
>
> Idea of merging some parts of SIBA and UQ are set on the table, but 
> draft specs should be more mature.
>
> *Next workshop*
>
> For information, John should be in London January 18 and 19^th , to 
> take into consideration.
>
> *AOB: push style*
>
> Discussion occurs on OAuth list regarding push style for the device flow.
>
> Some arguments are presented to balance push vs pull approach, for UQ.
>
> ·Complexity for the RP to implement 2 solutions
>
> ·Resource optimization from an OP side
>
> ·Number of requests per second
>
> ·Delay for the user to answer the question (seconds, minutes ?)
>
> Discussion to be continued on the list through the specs
>
> Best regards,
>
> Philippe
>
> _________________________________________________________________________________________________________________________
> 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.
> _________________________________________________________________________________________________________________________
>
> 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.
>
>
> _______________________________________________
> Openid-specs-mobile-profile mailing list
> Openid-specs-mobile-profile at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-mobile-profile/attachments/20161118/23808ab3/attachment-0001.html>