<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This is a second working group proposal that the specifications
council needs to take action upon. Yariv, have there been any updates to
the charter since this note?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> --
Mike<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<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"'>
specs-bounces@openid.net [mailto:specs-bounces@openid.net] <b>On Behalf Of </b>Yariv
Adan<br>
<b>Sent:</b> Monday, November 03, 2008 6:31 AM<br>
<b>To:</b> specs@openid.net<br>
<b>Subject:</b> Proposal to create the OpenID OAuth Hybrid Working Group<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif"'>In accordance
with the OpenID Foundation IPR policies and procedures<</span><a
href="http://openid.net/foundation/intellectual-property/" target="_blank"><span
style='font-family:"Arial","sans-serif"'>http://openid.net/foundation/intellectual-property/</span></a><span
style='font-family:"Arial","sans-serif"'> > this note proposes the
formation of a new working group chartered to produce an OpenID specification. <br>
As per Section 4.1 of the Policies, the specifics of the proposed working group
are:</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Background Information:<o:p></o:p></p>
</div>
<p class=MsoNormal>OpenID has always been focused on how to enable
user-authentication within the browser. Over the last year, OAuth has
been developed to allow authorization either from within a browser, desktop
software, or mobile devices. Obviously there has been interest in using
OpenID and OAuth together allowing a user to share their identity as well as
grant a Relying Party access to an OAuth protected resource in a single step.
A small group of people have been working on developing an extension to
OpenID which makes this possible in a collaborative fashion within<a
href="http://code.google.com/p/step2/" target="_blank"><span style='color:#0000CC'>http://code.google.com/p/step2/</span></a>.
This small project includes a draft spec and Open Source implementations
which the proposers would like to finalize within the OpenID Foundation.<br>
<br>
<br>
Working Group Name:<br>
OpenID OAuth Hybrid Working Group<br>
<br>
<br>
Purpose:<br>
Produce a standard OpenID extension to the OpenID Authentication protocol that
provides a mechanism to embed an OAuth approval request into an OpenID
authentication request to permit combined user approval. The extension
addresses the use case where the OpenID Provider and OAuth Service Provider are
the same service. To provide good user experience, it is important to present a
combined authentication and authorization screen for the two protocols.<br>
<br>
<br>
Scope:<br>
Standardize the draft Hybrid Protocol (<a
href="http://step2.googlecode.com/svn/spec/openid_oauth_extension/drafts/0/openid_oauth_extension.html"
target="_blank"><span style='color:#0000CC'>http://step2.googlecode.com/svn/spec/openid_oauth_extension/drafts/0/openid_oauth_extension.html</span></a>)
as an official OpenID Extension describing how to combine an OpenID
authentication request with the approval of an OAuth request token.<br>
<br>
<br>
Anticipated Contributions:<br>
Draft specification referenced above and various text contributions as more
developers implement it.<br>
<br>
<br>
Proposed List of Specifications:<br>
OpenID OAuth Extension 1.0. Spec completion by Q4 2008.<br>
<br>
<br>
Anticipated audience or users of the work:<br>
- OpenID Providers and Relying Parties<br>
- OAuth Consumers and Service Providers<br>
- Implementers of OpenID Providers and Relying Parties<br>
<br>
<br>
Language in which the WG will conduct business:<br>
English.<br>
<br>
<br>
Method of work:<br>
E-mail discussions on the working group mailing list and working group
conference calls.<br>
<br>
<br>
Basis for determining when the work of the WG is completed:<br>
The work will be completed once it is apparent that maximal consensus on the
protocol proposal has been achieved within the working group, consistent with
the purpose and scope.<br>
<br>
<br>
Proposers:<br>
- Ben Laurie, <a href="mailto:benl@google.com" target="_blank"><span
style='color:#0000CC'>benl@google.com</span></a>, Google<br>
- Breno de Medeiros, <a href="mailto:breno@google.com"
target="_blank"><span style='color:#0000CC'>breno@google.com</span></a>, Google<br>
- David Recordon, <a href="mailto:drecordon@sixapart.com"
target="_blank"><span style='color:#0000CC'>drecordon@sixapart.com</span></a>,
Six Apart<br>
- Dirk Balfanz, <a href="mailto:balfanz@google.com" target="_blank"><span
style='color:#0000CC'>balfanz@google.com</span></a>, Google<br>
- Joseph Smarr, <a href="mailto:jsmarr@plaxo.com" target="_blank"><span
style='color:#0000CC'>jsmarr@plaxo.com</span></a>, Plaxo<br>
- Yariv Adan, <a href="mailto:yariv@google.com" target="_blank"><span
style='color:#0000CC'>yariv@google.com</span></a>, Google<o:p></o:p></p>
<div>
<p class=MsoNormal> - Allen Tom, <a href="mailto:atom@yahoo-inc.com"
target="_blank">atom@yahoo-inc.com</a> , Yahoo<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> - Josh Hoyt, <a
href="mailto:josh@janrain.com" target="_blank">josh@janrain.com</a> , JanRain<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><br>
<br>
Initial Editors:<br>
- Dirk Balfanz, <a href="mailto:balfanz@google.com" target="_blank"><span
style='color:#0000CC'>balfanz@google.com</span></a>, Google<o:p></o:p></p>
<div>
<p class=MsoNormal> - Breno de Medeiros, <a
href="mailto:breno@google.com" target="_blank"><span style='color:#0000CC'>breno@google.com</span></a>,
Google<br clear=all>
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><br>
-- <br>
Yariv Adan | Product Manager<br>
Google Switzerland GmbH | Identifikationsnummer: CH-020.4.028.116-1<br>
This e-mail is confidential. If you are not the right addressee please do not
forward it, please inform the sender, and please erase this e-mail including
any attachments. Thanks. <o:p></o:p></p>
</div>
</div>
</body>
</html>