<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>We are defining that 'well understood protocol '<div><br></div><div>if you see no value in participating, don't </div><div><br></div><div>Paul</div><br>Anthony Nadalin <tonynad@microsoft.com> wrote:<br>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Bottom line here is that the platform vendors are going to build the brokers and they will expose APIs and as long as they use a understood protocol there is really no need to have this standardized.<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> openid-specs-native-apps-bounces@lists.openid.net [mailto:openid-specs-native-apps-bounces@lists.openid.net]
<b>On Behalf Of </b>Mike Jones<br>
<b>Sent:</b> Thursday, February 27, 2014 7:57 PM<br>
<b>To:</b> Ashish Jain; Sean Ginevan; ErichStuntebeck@air-watch.com; thomas.debenning@onelogin.com; Blake Brannon; Caleb Baker<br>
<b>Cc:</b> openid-specs-native-apps@lists.openid.net<br>
<b>Subject:</b> [Openid-specs-native-apps] Native Apps discussion at RSA<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attendees:<o:p></o:p></p>
<p class="MsoNormal">Ashish Jain<o:p></o:p></p>
<p class="MsoNormal">Sean Ginevan<o:p></o:p></p>
<p class="MsoNormal">Erich Stuntebeck<o:p></o:p></p>
<p class="MsoNormal">Thomas DeBenning<o:p></o:p></p>
<p class="MsoNormal">Blake Brannon<o:p></o:p></p>
<p class="MsoNormal">Caleb Baker<o:p></o:p></p>
<p class="MsoNormal">Mike Jones<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We discussed the status of the specs, goals, interop and adoption.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mike asked questions like:<o:p></o:p></p>
<p class="MsoNormal"> What problem is this trying to solve?<o:p></o:p></p>
<p class="MsoNormal"> Who will deploy this middleware? Platform vendors?<o:p></o:p></p>
<p class="MsoNormal"> What does success look like?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ashish said that building the ecosystem requires the participation of three parties:<o:p></o:p></p>
<p class="MsoNormal"> Identity Providers<o:p></o:p></p>
<p class="MsoNormal"> Enterprise Mobility Management (EMM) Vendors (such as AirWatch, Mobile Island)<o:p></o:p></p>
<p class="MsoNormal"> Application Developers / SAAS Vendors<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We asked why there is the list of applications required in the specs<o:p></o:p></p>
<p class="MsoNormal">The enterprise use cases require federation, which may make them more compelling than consumer use cases, at least at first<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Apparently there is a deck from the most recent CIS that outlines use cases and gives an overview<o:p></o:p></p>
<p class="MsoNormal"> By Ashish, Paul Madsen, Josh<o:p></o:p></p>
<p class="MsoNormal"> Caleb and Mike asked this to be shared<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>