<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">
</head>
<body>
<div>
<div style="font-size:11pt; font-family:Calibri,sans-serif">Why, it will be yo to server to understand trust aspects and it will be standard oauth protocols. The platform brokers will be default so what us value of this effort?<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir="ltr">
<hr>
<span style="font-size:11pt; font-family:Calibri,sans-serif; font-weight:bold">From:
</span><span style="font-size:11pt; font-family:Calibri,sans-serif"><a href="mailto:paul.madsen@gmail.com">Paul Madsen</a></span><br>
<span style="font-size:11pt; font-family:Calibri,sans-serif; font-weight:bold">Sent:
</span><span style="font-size:11pt; font-family:Calibri,sans-serif">ý2/ý28/ý2014 9:44 AM</span><br>
<span style="font-size:11pt; font-family:Calibri,sans-serif; font-weight:bold">To:
</span><span style="font-size:11pt; font-family:Calibri,sans-serif"><a href="mailto:tonynad@microsoft.com">Anthony Nadalin</a>;
<a href="mailto:Michael.Jones@microsoft.com">Mike Jones</a>; <a href="mailto:ashishjain@vmware.com">
Ashish Jain</a>; <a href="mailto:sginevan@mobileiron.com">Sean Ginevan</a>; <a href="mailto:erichstuntebeck@air-watch.com">
ErichStuntebeck@air-watch.com</a>; <a href="mailto:thomas.debenning@onelogin.com">
thomas.debenning@onelogin.com</a>; <a href="mailto:blakebrannon@air-watch.com">Blake Brannon</a>;
<a href="mailto:Caleb.Baker@microsoft.com">Caleb Baker</a></span><br>
<span style="font-size:11pt; font-family:Calibri,sans-serif; font-weight:bold">Cc:
</span><span style="font-size:11pt; font-family:Calibri,sans-serif"><a href="mailto:openid-specs-native-apps@lists.openid.net">openid-specs-native-apps@lists.openid.net</a></span><br>
<span style="font-size:11pt; font-family:Calibri,sans-serif; font-weight:bold">Subject:
</span><span style="font-size:11pt; font-family:Calibri,sans-serif">Re: [Openid-specs-native-apps] Native Apps discussion at RSA</span><br>
<br>
</div>
<div>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.</span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D"> </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</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Attendees:</p>
<p class="MsoNormal">Ashish Jain</p>
<p class="MsoNormal">Sean Ginevan</p>
<p class="MsoNormal">Erich Stuntebeck</p>
<p class="MsoNormal">Thomas DeBenning</p>
<p class="MsoNormal">Blake Brannon</p>
<p class="MsoNormal">Caleb Baker</p>
<p class="MsoNormal">Mike Jones</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We discussed the status of the specs, goals, interop and adoption.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Mike asked questions like:</p>
<p class="MsoNormal"> What problem is this trying to solve?</p>
<p class="MsoNormal"> Who will deploy this middleware? Platform vendors?</p>
<p class="MsoNormal"> What does success look like?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Ashish said that building the ecosystem requires the participation of three parties:</p>
<p class="MsoNormal"> Identity Providers</p>
<p class="MsoNormal"> Enterprise Mobility Management (EMM) Vendors (such as AirWatch, Mobile Island)</p>
<p class="MsoNormal"> Application Developers / SAAS Vendors</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We asked why there is the list of applications required in the specs</p>
<p class="MsoNormal">The enterprise use cases require federation, which may make them more compelling than consumer use cases, at least at first</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Apparently there is a deck from the most recent CIS that outlines use cases and gives an overview</p>
<p class="MsoNormal"> By Ashish, Paul Madsen, Josh</p>
<p class="MsoNormal"> Caleb and Mike asked this to be shared</p>
<p class="MsoNormal"> </p>
</div>
</div>
</body>
</html>