<HTML>
<HEAD>
<TITLE>OpenID v.Next Discovery Working Group Proposal</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Per the OpenID Foundation IPR policies and procedures, this note formally proposes the formation of a new OpenID working group. The charter and background information for the proposed group are as follows.<BR>
<BR>
<B>(a) <I><U>Charter</U></I>.<BR>
(i)</B> <B>WG name:</B> OpenID v.Next Discovery.<BR>
<B>(ii)</B> <B>Purpose:</B> Produce a discovery specification or family of discovery specifications for OpenID v.Next that address the limitations and drawbacks present in the OpenID 2.0 discovery facilities that limit OpenID’s applicability, adoption, usability, privacy, and security. Specific goals are:<BR>
</SPAN></FONT><SPAN STYLE='font-size:11pt'><FONT FACE="Symbol">· </FONT><FONT FACE="Times New Roman"> </FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">enable discovery for and normalization of OpenID identifiers, including those utilizing e-mail address syntax and those that are URLs,<BR>
<BR>
</FONT><FONT FACE="Symbol">· </FONT><FONT FACE="Times New Roman"> </FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">enable discovery of features supported by OpenID v.Next OpenID Providers and Relying Parties,<BR>
<BR>
</FONT><FONT FACE="Symbol">· </FONT><FONT FACE="Times New Roman"> </FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">enable discovery of attributes about OpenID v.Next OPs and RPs, including, but not limited to visual logos and human-readable site names,<BR>
<BR>
</FONT><FONT FACE="Symbol">· </FONT><FONT FACE="Times New Roman"> </FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">enable discovery supporting a spectrum of clients, including passive clients per current usage, thin active clients, and active clients with OP functionality,<BR>
<BR>
</FONT><FONT FACE="Symbol">· </FONT><FONT FACE="Times New Roman"> </FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">enable discovery supporting authentication to and use of attributes by non-browser applications,<BR>
<BR>
</FONT><FONT FACE="Symbol">· </FONT><FONT FACE="Times New Roman"> </FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">enable discovery of public keys,<BR>
<BR>
</FONT><FONT FACE="Symbol">· </FONT><FONT FACE="Times New Roman"> </FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">enable potential mechanisms for discovering context-relevant OpenID providers,<BR>
<BR>
</FONT><FONT FACE="Symbol">· </FONT><FONT FACE="Times New Roman"> </FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">seamlessly integrate with and complement the other OpenID v.Next specifications.<BR>
<BR>
Compatibility with OpenID 2.0 is an explicit non-goal for this work.<BR>
<B>(iii)</B> <B>Scope:</B> Produce a next generation OpenID discovery specification or specifications, consistent with the purpose statement.<BR>
<B>(iv)</B> <B>Proposed List of Specifications</B>: OpenID v.Next Discovery and possibly related specifications.<BR>
<B>(v)</B> <B>Anticipated audience or users of the work:</B> Implementers of OpenID Providers, Relying Parties, Active Clients, and non-browser applications utilizing OpenID.<BR>
<B>(vi)</B> <B>Language in which the WG will conduct business</B>: English.<BR>
<B>(vii)</B> <B>Method of work: </B>E-mail discussions on the working group mailing list, working group conference calls, and face-to-face meetings at the Internet Identity Workshop and OpenID summits.<BR>
<B>(viii)</B> <B>Basis for determining when the work of the WG is completed:</B> Work will not be deemed to be complete until there is a consensus that the resulting protocol specification or family of specifications fulfills the working group goals. Additional proposed changes beyond that initial consensus will be evaluated on the basis of whether they increase or decrease consensus within the working group. The work will be completed once it is apparent that maximal consensus on the draft has been achieved, consistent with the purpose and scope.<BR>
<B>(b) <I><U>Background Information</U></I>.<BR>
(i)</B> <B>Related work being done in other WGs or organizations</B>: OpenID Authentication 2.0 and related specifications, including Yadis 1.0. OAuth and OAuth 2.0. XRDS, XRD, host-meta, Web Linking, XAuth, LRDD, and WebFinger.<BR>
<B>(ii)</B> <B>Proposers:</B> <BR>
Allen Tom, <FONT COLOR="#0000FF"><U><a href="atom@yahoo-inc.com">atom@yahoo-inc.com</a></U></FONT>, Yahoo! (co-chair)<BR>
Michael B. Jones, <FONT COLOR="#0000FF"><U><a href="mbj@microsoft.com">mbj@microsoft.com</a></U></FONT>, Microsoft (co-chair)<BR>
John Bradley, <FONT COLOR="#0000FF"><U><a href="ve7jtb@ve7jtb.com">ve7jtb@ve7jtb.com</a></U></FONT>, independent<BR>
Dick Hardt, <FONT COLOR="#0000FF"><U><a href="dick.hardt@gmail.com">dick.hardt@gmail.com</a></U></FONT>, independent<BR>
</FONT></SPAN>
</BODY>
</HTML>