Mike,<div>Yes, agreed. In process and I will send you a list of the contributors as well as those who have signed the IPR agreements. </div><div><br></div><div>Thanks</div><div>Greg<br><br><div class="gmail_quote">On Sun, Jun 10, 2012 at 11:58 AM, Mike Jones <span dir="ltr"><<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Greg,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Could you please send the board and specs-council a list of the individuals who have contributed to the specs and which of them you have OpenID IPR agreements
from? That would help me (primarily as a board member) better understand where we are on this.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Note: Having this isn’t a requirement for approving creation of the working group. But having the work be IPR-clean is a requirement for eventually publishing
Implementer’s Drafts or Final Specifications.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Best of wishes on moving this forward!<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> -- Mike<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:openid-specs-council-bounces@lists.openid.net" target="_blank">openid-specs-council-bounces@lists.openid.net</a> [mailto:<a href="mailto:openid-specs-council-bounces@lists.openid.net" target="_blank">openid-specs-council-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>Keegstra, Greg<br>
<b>Sent:</b> Friday, June 08, 2012 2:08 PM<br>
<b>To:</b> Allen Tom<br>
<b>Cc:</b> <a href="mailto:openid-specs-council@lists.openid.net" target="_blank">openid-specs-council@lists.openid.net</a>; <a href="mailto:specs@openid.net" target="_blank">specs@openid.net</a>; Johnny Bufu<br>
<b>Subject:</b> Re: [OIDFSC] Backplane Protocol Working Group Charter Submission<u></u><u></u></span></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi Allen,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Appreciate the feedback on the proposal for the Backplane working group. Let me respond to each of your questions below.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal"><span style="color:#000099">>>Does the Backplane community already have signed IPR agreements from all contributors to the existing Backplane specs?</span><u></u><u></u></p>
<div>
<p class="MsoNormal">In progress. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#333399">>>What is the expected output of the working group? Finalized Backplane 2.0 spec(s)? A reference Backplane server implementation?</span><br>
The primary output is a finalized Backplane specification. The reference implementation is just a side effect but it is not the focus.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <br>
<span style="color:#333399">>>Will the OIDF host any services for Backplane? (similar to <a href="http://accountchooser.net/" target="_blank">accountchooser.net</a>)</span><br>
None are planned, unless we want the OIDF to take over the Backplanex.com site.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#333399">>>The WG Proposal says that one of the goals is to create a trust framework. Will there be some sort of certification process to determine if the apps/users/websites are trustworthy?</span><br>
None is planned but interested in your feedback here. The proposed trust framework will be presented primarily for reference purposes. Since the trust framework is between a site and the widgets on the site there is no immediate need for certification across
a "global" trust framework. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:#333399">>>Is the scope limited only to websites and JS widgets that embedded by websites? Does it also include native apps?</span><br>
The scope encompasses both external and internal widgets. The origination of the widget is irrelevant to its utilization of the Backplane. <br>
<br>
Thanks,<br>
Greg<u></u><u></u></p>
<div>
<p class="MsoNormal">On Wed, Jun 6, 2012 at 10:30 AM, Allen Tom <<a href="mailto:allentomdude@gmail.com" target="_blank">allentomdude@gmail.com</a>> wrote:<u></u><u></u></p>
<p class="MsoNormal">Hi Greg,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks for submitting the Backplane WG proposal. A few questions:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<ol start="1" type="1">
<li class="MsoNormal">
Does the Backplane community already have signed IPR agreements from all contributors to the existing Backplane specs?<u></u><u></u></li><li class="MsoNormal">
What is the expected output of the working group? Finalized Backplane 2.0 spec(s)? A reference Backplane server implementation? <u></u><u></u></li><li class="MsoNormal">
Will the OIDF host any services for Backplane? (similar to <a href="http://accountchooser.net" target="_blank">
accountchooser.net</a>)<u></u><u></u></li><li class="MsoNormal">
The WG Proposal says that one of the goals is to create a trust framework. Will there be some sort of certification process to determine if the apps/users/websites are trustworthy?<u></u><u></u></li><li class="MsoNormal">
Is the scope limited only to websites and JS widgets that embedded by websites? Does it also include native apps?<u></u><u></u></li></ol>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Allen<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">On Tue, Jun 5, 2012 at 12:50 PM, Keegstra, Greg <<a href="mailto:greg@janrain.com" target="_blank">greg@janrain.com</a>> wrote:<u></u><u></u></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222">This is a formal request to the OpenID Specs Council to review the charter proposal for creating a
Backplane Protocol working group. </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222">Participation and interest in the development of the protocol has grown out of recent Internet Identity
Workshops. The potential formation of an OpenID work group is an opportunity to provide awareness about the Backplane Protocol globally so that more application vendors and website publishers will have the opportunity to guide its development and collaborate
around use cases.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222">If there is a positive response from the Specifications Council, we would like to work with the OIDF
to schedule time at the 2012 CIS event in July to have more discussions on this topic and to seek additional workgroup members.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222">I look forward to your review of this charter proposal and welcome feedback you may have on its scope
and purpose.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222">Regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222">Greg</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Charter submission for the Backplane Protocol Working Group</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
<br>
There is an interest in creating an OpenID workgroup to broaden collaboration in the development of the Backplane Protocol specification.
<br>
<br>
<b>Charter Proposal</b><br>
<br>
Following the OpenID Foundation’s IPR policies and procedures this note proposes the formation of a new working group chartered to broaden input into the development of a Backplane Protocol specification. The proposed charter is below and may change during
the initial feedback period.<br>
<br>
<b>I. Name</b><br>
<br>
Backplane Protocol Working Group<br>
<br>
<b>II. Statement of Purpose</b><br>
<br>
Facilitate the creation of a trust framework between end users, websites and third-party applications such that all can exchange information with each other in a standardized way. <br>
<br>
While the messages exchanged through the Backplane Protocol are not required to be identity related or reference OpenID-authenticated users, these represent the most interesting use case and have constituted one of the main drivers behind the Backplane efforts
to date.<br>
<br>
If Backplane continues to build momentum and becomes widely adopted for inter-widget/inter-application identity message exchange, it would benefit all parties involved if the development of the protocol continued within the OpenID Foundation.<br>
<br>
This workgroup intends to solidify the current proposed protocol by ensuring the specifications, reference and production implementations
</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-top:.1pt;margin-bottom:.1pt;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">adhere to best practices in online security as it pertains to broadcasting of user identity between multiple applications on a website</span><u></u><u></u></li>
<li class="MsoNormal" style="margin-top:.1pt;margin-bottom:.1pt;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">are extensible to support other application scenarios or message types to broaden the scope of inter-widget communications beyond identity messages</span><u></u><u></u></li>
</ul>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
<b>III. Background</b><br>
<br>
Echo conceived the protocol and designed it as an open standard. They later partnered with Janrain and together have evolved the protocol, incorporating feedback received from interested Relying Parties as well as the community, including the Internet Identity
Workshops in the Spring and Fall of 2011. <br>
<br>
The Backplane Exchange Protocol is currently used today by application vendors including Echo and Janrain and by
<a href="http://backplanex.com/showcase/" target="_blank">website operators</a> including ABC, Discovery Channel, NBC Universal, Sports Illustrated, The Washington Post, Universal Music Group and USA Networks.<br>
<br>
<b>IV. Scope</b><br>
<br>
The initial scope of effort by the working group is to ensure that the protocol</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-top:.1pt;margin-bottom:.1pt;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">adheres to best practices in online security as it pertains to broadcasting of user identity between multiple applications on a website</span><u></u><u></u></li>
<li class="MsoNormal" style="margin-top:.1pt;margin-bottom:.1pt;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">is extensible to support other application scenarios or message types to broaden the scope of inter-widget communications beyond identity messages</span><u></u><u></u></li>
</ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Scope also involves standardizing the definition and nomenclature of constructs that describe various aspects of the protocol e.g. message types or application scenarios, such that it appeals to the technology community at large.<br>
<br>
Scope does not include definition of additional message types (also currently known as application scenarios) or recruiting additional members beyond the initially formed working group.<br>
<br>
<b>V. Specifications</b><br>
<br>
The core Backplane Exchange protocol specifications can be found at the URLs below:<br>
<br>
Version 2.0 (Latest Work)<br>
<span style="color:#1155cc"><a href="https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0" target="_blank">Backplane Exchange Specification 2.0</a></span> (draft
13, June 2012, HTML)</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><a href="http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf" target="_blank">Backplane Exchange
Specification 2.0</a> (draft 12, May 2012, HTML)<br>
<a href="http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf" target="_blank">Backplane Exchange Specification 2.0</a> (draft 10, March 2012, HTML)<br>
<a href="http://backplanex.com/documentation/backplane-specification-2-0/" target="_blank">Backplane Exchange Specification 2.0</a> (draft 07, January 2012, HTML)<br>
<br>
Version 1.0 (Currently in Production)<br>
<a href="http://backplanex.com/documentation/backplane-specification-1-2/" target="_blank">Backplane Exchange Specification 1.2</a> (June 2011, HTML)<br>
<a href="http://backplanex.com/documentation/backplane-specification-1-1/" target="_blank">Backplane Exchange Specification 1.1</a> (June 2011, HTML)<br>
<a href="http://backplanex.com/documentation/backplane-specification-1-0" target="_blank">Backplane Exchange Specification 1.0</a> (November 2010, HTML)<br>
<br>
<b>VI. Anticipated Audience</b><br>
<br>
Interested parties would include:</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:.1pt;margin-left:53.1pt;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Website Operators that need to use third-party applications on their sites and want to improve usability and interoperability.</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:.1pt;margin-left:53.1pt;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Relying Parties that are looking to distribute personalized services on other portals versus their own websites.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
A number of participating websites and vendors interested in Backplane Protocol and the advancement of the specifications are listed
<a href="http://backplanex.com/showcase/" target="_blank">here.</a><br>
<br>
<b>VII. Language of business</b><br>
<br>
English.<br>
<br>
<b>VIII. Method of work</b><br>
<br>
Mailing list discussion. Posting of intermediate drafts at <a href="http://backplanex.com/" target="_blank">
http://backplanex.com</a> or the OpenID Wiki. Virtual conferencing on an ad-hoc basis.<br>
<br>
<b>IX. Basis for completion of the activity</b><br>
<br>
When all items set forth in Section IV Scope have been addressed and agreed upon by members of the working group.<br>
<br>
<b>X. Initial Membership</b><br>
<br>
Johnny Bufu, Janrain<br>
Greg Keegstra, Janrain<br>
Vidya Shivkumar, Janrain<br>
Tom Raney, Janrain<br>
Vlad Skvortsov, Echo</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Yuri Lukyanov, Echo</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Alexander Zhuravlev, Echo<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Chris Saad, Echo<br>
<br>
<b>XI. Expected contribution</b><br>
<br>
Draft: <a href="https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0" target="_blank">
Backplane Exchange Specification 2.0 (draft 13) </a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">-- <br>
<span style="color:#888888">Greg Keegstra, Strategic Alliances Director, Janrain, Inc.<br>
e: <a href="mailto:greg@janrain.com" target="_blank">greg@janrain.com</a> | w: <a href="tel:%28415%29%20317-1142" value="+14153171142" target="_blank">(415) 317-1142</a> | twitter: @keegstra</span>
<u></u><u></u></p>
</div>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><font color="#888888">Greg Keegstra, Strategic Alliances Director, Janrain, Inc.<br>
e: <a href="mailto:greg@janrain.com" target="_blank">greg@janrain.com</a> | w: <a value="+14153171142">(415) 317-1142</a> | twitter: @keegstra</font> <br><br>
</div>