The Google announcement of this new OpenID service has now been formally posted at<br><div style="margin-left: 40px;"><a href="http://googlecode.blogspot.com/2009/07/google-apps-openid-identity-hub-for.html" target="_blank">http://googlecode.blogspot.com/2009/07/google-apps-openid-identity-hub-for.html</a><br>
</div><br><div class="gmail_quote">On Fri, Jul 10, 2009 at 11:13 AM, Breno de Medeiros <span dir="ltr"><<a href="mailto:breno@google.com">breno@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>There is a proposal for a webfinger protocol based on standards (the IETF LRDD proposal and either (optionally signed) XRDS or the newly proposed (optionally signed) XRD format) that would allow users to type</div><div>
<br></div><div>'<a href="http://google.com" target="_blank">google.com</a>'</div><div><br></div><div>or their email address,</div><div><br></div><div>and it would just work. It would also work for users of Google Apps for Your Domain, that have email addresses that are not @<a href="http://gmail.com" target="_blank">gmail.com</a> or @<a href="http://googlemail.com" target="_blank">googlemail.com</a>. These users comprise a significant portion of our user base.</div>
<div><br></div><div>Hopefully the community will be excited about these possibilities and will embrace a new vision for discovery that supports all users. We at Google have NOT been working on this behind the scenes. For instance, see John Panzer's blog post on webfinger at <a href="http://www.abstractioneer.org/" target="_blank">http://www.abstractioneer.org/</a>, our involvement in the XRI TC (see the markmail links in Eric's message), and many emails that we have exchanged in the various openid mailing lists about discovery in the past several months. We have also added our names to a proposal for an OpenID discovery WG <a href="http://wiki.openid.net/OpenID-Discovery" target="_blank">http://wiki.openid.net/OpenID-Discovery</a></div>
<div><br></div><div>We invite all that are excited about possibilities with a new discovery mechanism (supporting email and xmpp addresses as OpenID identifiers, improving security of discovery, making it more flexible to work with hosted applications, etc.) to </div>
<div>contribute with momentum to move this forward.</div><div><div></div><div class="h5"><br><div class="gmail_quote">On Thu, Jul 9, 2009 at 10:14 AM, Eric Sachs <span dir="ltr"><<a href="mailto:esachs@google.com" target="_blank">esachs@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>>> <span style="border-collapse: collapse;">I haven't heard anything about this except from this one article.</span><div>
<span style="border-collapse: collapse;"><br>
</span></div></div><div>In terms of more background on the evolving discovery standards, the best information is actually on a blog run by Eran Hammer-Lahav at Yahoo who has led a lot of the work in this space. Here is a hyperlink which will show you all the blog posts he has done about "discovery" and he has done a good job of trying to provide background.</div>
<blockquote style="border: medium none ; margin: 0pt 0pt 0pt 40px; padding: 0px;"><a href="http://www.hueniverse.com/hueniverse/discovery/" target="_blank">http://www.hueniverse.com/hueniverse/discovery/</a></blockquote>
<div>Note though that this work is not specific to OpenID, but instead is to try to provide a generic discovery mechanism that can be used my multiple protocols.</div><div><br></div><div>If you want to join some of the discussions, here are links to a few threads:</div>
<blockquote style="border: medium none ; margin: 0pt 0pt 0pt 40px; padding: 0px;"><span style="border-collapse: collapse;"><a href="http://lists.oasis-open.org/archives/xri/200905/msg00025.html" style="color: rgb(0, 0, 204);" target="_blank">http://lists.oasis-open.org/archives/xri/200905/msg00025.html</a></span><br>
<span style="border-collapse: collapse;"><a href="http://markmail.org/message/rup4ikec43bk4wkg" style="color: rgb(0, 0, 204);" target="_blank">http://markmail.org/message/rup4ikec43bk4wkg</a></span><br>
<span style="border-collapse: collapse;"><a href="http://markmail.org/message/5ckiqdzjguipa3qf" style="color: rgb(0, 0, 204);" target="_blank">http://markmail.org/message/5ckiqdzjguipa3qf</a></span></blockquote>
<div>We do still want more community discussions about discovery, and its application to OpenID. W<span style="font-family: Arial; font-size: 12px;">hile these standards are being refined, we are providing a proof-of-concept implementation of a next-generation OpenID discovery protocol. While some of the details of this proof-of-concept-implementation are different from what the eventual standards are likely to look like (e.g., we're using XRDS instead of XRD for discovery documents, and are using temporary namespaces), we believe all the necessary pieces are there. For nitty gritty details, see <span style="font-family: arial; font-size: 13px;"><a href="http://sites.google.com/site/oauthgoog/fedlogininterp/openiddiscovery" target="_blank">http://sites.google.com/site/oauthgoog/fedlogininterp/openiddiscovery</a></span></span></div>
<div><br></div><div><br></div><br><div class="gmail_quote"><div><div></div><div>On Thu, Jul 9, 2009 at 9:59 AM, Andrew Arnott <span dir="ltr"><<a href="mailto:andrewarnott@gmail.com" target="_blank">andrewarnott@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div>Oops.... I sent my email to the wrong list. See below.<br>
<br clear="all">
--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre<br>
<br><br><div class="gmail_quote">On Thu, Jul 9, 2009 at 9:58 AM, Andrew Arnott <span dir="ltr"><<a href="mailto:andrewarnott@gmail.com" target="_blank">andrewarnott@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>From <a href="http://www.readwriteweb.com/archives/google_to_announce_major_identity_initiative_for_1.php" target="_blank">http://www.readwriteweb.com/archives/google_to_announce_major_identity_initiative_for_1.php</a><br>
<br><div style="margin-left: 40px;">
OpenID relying parties will need to be redirected from the domain provided at
user login over to Google's OpenID service. In order for this redirect to
happen, all relying parties will need to start looking for a new OpenID
extension that Google has developed and implemented in conjunction with one
relying party technology, <a href="http://www.janrain.com/" target="_blank">JanRain's RPX</a>.</div><br>Is this just FUD about Google? I haven't heard anything about this except from this one article. And Google's own <a href="http://code.google.com/intl/ja/apis/accounts/docs/OpenID.html" target="_blank">OpenID for Google Apps</a> page says nothing about a special extension.<br>
<font color="#888888">
<br><br clear="all">--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre<br>
</font></blockquote></div><br>
<br></div></div><div>_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
<br></div></blockquote></div><br>
<br>_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
<br></blockquote></div><br><br clear="all"><br></div></div><font color="#888888">-- <br>--Breno<br><br>+1 (650) 214-1007 desk<br>+1 (408) 212-0135 (Grand Central)<br>MTV-41-3 : 383-A <br>PST (GMT-8) / PDT(GMT-7)<br>
</font></blockquote></div><br>