To: Specs Council <div><br></div><div>Please review the attached WG Charter proposal. </div><div><br></div><div>The review period ends on June 19 PDT. </div><div><br></div><div>Best, </div><div><br></div><div>Nat<br><br><div class="gmail_quote">
On Wed, Jun 6, 2012 at 4:50 AM, Keegstra, Greg <span dir="ltr"><<a href="mailto:greg@janrain.com" target="_blank">greg@janrain.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">















<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#222222">This is a formal request to the OpenID</span><span style="font-size:10.0pt;font-family:Arial;color:#222222"> Specs Council</span><span style="font-size:10.0pt;font-family:Arial;color:#222222">
to review the charter proposal for creating a Backplane Protocol working group.
 </span></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#222222"> </span></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;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></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#222222"> </span></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#222222">If there is a positive response from the
Specifications</span><span style="font-size:10.0pt;font-family:Arial;color:#222222"> Council, we would like to work with the
OIDF to schedule time at the 2012 </span><span style="font-size:10.0pt;font-family:Arial;color:#222222">CIS event in July to</span><span style="font-size:10.0pt;font-family:Arial;color:#222222">
</span><span style="font-size:10.0pt;font-family:Arial;color:#222222">have more discussions on this topic and to seek additional
workgroup members</span><span style="font-size:10.0pt;font-family:Arial;color:#222222">.</span></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#222222"> </span></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#222222">I look forward to your review of this charter
proposal and welcome feedback you may have on its scope and purpose.</span></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#222222"> </span></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#222222">Regards,</span></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#222222">Greg</span><span style="font-size:10.0pt;font-family:Times"></span></p>

<p class="MsoNormal"><span style="font-size:10.0pt"> </span></p>

<p class="MsoNormal"><b><span style="font-size:10pt;font-family:Arial"><br></span></b></p><p class="MsoNormal"><b><span style="font-size:10pt;font-family:Arial">Charter submission for the Backplane Protocol Working
Group</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">There is an interest in creating an OpenID workgroup to
broaden collaboration in the development of the Backplane Protocol
specification. </span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">Charter Proposal</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">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.</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">I. Name</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">Backplane Protocol Working Group</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">II. Statement of Purpose</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">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.  </span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">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.</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">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.</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">This workgroup intends to solidify the current proposed
protocol  by ensuring the specifications, reference and production
implementations </span><span style="font-size:10pt;font-family:Arial"></span></p>

<ul style="margin-top:0in" type="disc">
 <li class="MsoNormal" style="margin-top:0.1pt;margin-bottom:0.1pt;vertical-align:baseline"><span style="font-size:10.0pt;font-family:Arial">adhere to best practices in
     online security as it pertains to broadcasting of user identity between
     multiple applications on a website</span></li>
 <li class="MsoNormal" style="margin-top:0.1pt;margin-bottom:0.1pt;vertical-align:baseline"><span style="font-size:10.0pt;font-family:Arial">are extensible to support
     other application scenarios or message types to broaden the scope of
     inter-widget communications beyond identity messages</span></li>
</ul>

<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial"><br>
</span><b><span style="font-size:10pt;font-family:Arial">III. Background</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">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.  </span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">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.</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">IV. Scope</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">The initial scope of effort by the working group is to ensure
that the protocol</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span></p>

<ul style="margin-top:0in" type="disc">
 <li class="MsoNormal" style="margin-top:0.1pt;margin-bottom:0.1pt;vertical-align:baseline"><span style="font-size:10.0pt;font-family:Arial">adheres to best practices in
     online security as it pertains to broadcasting of user identity between
     multiple applications on a website</span></li>
 <li class="MsoNormal" style="margin-top:0.1pt;margin-bottom:0.1pt;vertical-align:baseline"><span style="font-size:10.0pt;font-family:Arial">is extensible to support
     other application scenarios or message types to broaden the scope of inter-widget
     communications beyond identity messages</span></li>
</ul>

<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial"><br>
</span><span style="font-size:10pt;font-family:Arial">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.</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">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.</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">V. Specifications</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">The core Backplane Exchange protocol specifications can be
found at the URLs below:</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">Version 2.0 (Latest Work)</span><span style="font-size:10pt;font-family:Arial"><br>
</span><span style="font-size:10pt;font-family:Arial"><span style="color:rgb(17,85,204)"><a href="https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0" target="_blank">Backplane Exchange Specification 2.0</a></span></span><span style="font-size:10pt;font-family:Arial">  (draft 13, June 2012, HTML)</span></p>

<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial"><a href="http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf" target="_blank">Backplane Exchange
Specification 2.0</a></span><span style="font-size:10pt;font-family:Arial">  (draft 12, May 2012, HTML)</span><span style="font-size:10pt;font-family:Arial"><br>
<a href="http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf" target="_blank">Backplane Exchange Specification 2.0</a></span><span style="font-size:10pt;font-family:Arial">
 (draft 10, March 2012, HTML)</span><span style="font-size:10pt;font-family:Arial"><br>
<a href="http://backplanex.com/documentation/backplane-specification-2-0/" target="_blank">Backplane Exchange Specification 2.0</a></span><span style="font-size:10pt;font-family:Arial">
 (draft 07, January 2012, HTML)</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">Version 1.0 (Currently in Production)</span><span style="font-size:10pt;font-family:Arial"><br>
<a href="http://backplanex.com/documentation/backplane-specification-1-2/" target="_blank">Backplane Exchange Specification 1.2</a></span><span style="font-size:10pt;font-family:Arial">
(June 2011, HTML)</span><span style="font-size:10pt;font-family:Arial"><br>
<a href="http://backplanex.com/documentation/backplane-specification-1-1/" target="_blank">Backplane Exchange Specification 1.1</a></span><span style="font-size:10pt;font-family:Arial">
(June 2011, HTML)</span><span style="font-size:10pt;font-family:Arial"><br>
<a href="http://backplanex.com/documentation/backplane-specification-1-0" target="_blank">Backplane Exchange Specification 1.0</a></span><span style="font-size:10pt;font-family:Arial">
(November 2010, HTML)</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">VI. Anticipated Audience</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">Interested parties would include:</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span></p>

<p class="MsoNormal" style="margin-top:.1pt;margin-right:0in;margin-bottom:.1pt;margin-left:53.1pt;vertical-align:baseline"><span style="font-size:10pt;font-family:Symbol">·<span style="font-family:'Times New Roman';font-size:7pt">       </span></span><span style="font-size:10pt;font-family:Arial">Website
Operators that need to use third-party applications on their sites and want to
improve usability and interoperability.</span><span style="font-size:10pt;font-family:Arial"></span></p>

<p class="MsoNormal" style="margin-top:.1pt;margin-right:0in;margin-bottom:.1pt;margin-left:53.1pt;vertical-align:baseline"><span style="font-size:10pt;font-family:Symbol">·<span style="font-family:'Times New Roman';font-size:7pt">       </span></span><span style="font-size:10pt;font-family:Arial">Relying
Parties that are looking to distribute personalized services on other portals
versus their own websites.</span><span style="font-size:10pt;font-family:Arial"></span></p>

<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial"><br>
</span><span style="font-size:10pt;font-family:Arial">A number of participating websites and vendors interested in
Backplane Protocol and the advancement of the specifications are listed </span><span style="font-size:10pt;font-family:Arial"><a href="http://backplanex.com/showcase/" target="_blank">here.</a><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">VII. Language of business</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">English.</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">VIII. Method of work</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">Mailing list discussion.  Posting of intermediate
drafts at </span><span style="font-size:10pt;font-family:Arial"><a href="http://backplanex.com/" target="_blank">http://backplanex.com</a></span><span style="font-size:10pt;font-family:Arial">
or the OpenID Wiki.  Virtual conferencing on an ad-hoc basis.</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">IX. Basis for completion of the activity</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">When all items set forth in Section IV Scope have been
addressed and agreed upon by members of the working group.</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">X. Initial Membership</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">Johnny Bufu, Janrain</span><span style="font-size:10pt;font-family:Arial"><br>
</span><span style="font-size:10pt;font-family:Arial">Greg Keegstra, Janrain</span><span style="font-size:10pt;font-family:Arial"><br>
</span><span style="font-size:10pt;font-family:Arial">Vidya Shivkumar, Janrain</span><span style="font-size:10pt;font-family:Arial"><br>
</span><span style="font-size:10pt;font-family:Arial">Tom Raney, Janrain</span><span style="font-size:10pt;font-family:Arial"><br>
</span><span style="font-size:10pt;font-family:Arial">Vlad Skvortsov, Echo</span></p><p class="MsoNormal"><font face="Arial">Yuri Lukyanov, Echo</font></p><p class="MsoNormal"><font face="Arial">Alexander Zhuravlev, Echo<br>

</font>
<span style="font-size:10pt;font-family:Arial">Chris Saad, Echo</span><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><b><span style="font-size:10pt;font-family:Arial">XI. Expected contribution</span></b><span style="font-size:10pt;font-family:Arial"><br>
<br>
</span><span style="font-size:10pt;font-family:Arial">Draft: </span><span style="font-size:10pt;font-family:Arial"><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><span style="font-size:10.0pt;font-family:Arial"></span></p>



<p class="MsoNormal"><span style="font-size:10.0pt"> </span></p>

<div> </div><br>
<br>_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net">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><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Nat Sakimura (=nat)<div>Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>@_nat_en</div><br>

</div>