<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Gabe Wachob wrote:
<blockquote cite="mid000601c6f892$2f425db0$090a0a0a@AMSOFTWachob"
type="cite">
<pre wrap="">I 100% agree with Pete here.
OpenID is, from an RP's POV, an authentication outsourcing protocol.
</pre>
</blockquote>
Absolutely! The relying party (RP) is relying first of all on this. All
other extensions mentioned and designed are currently optional. This
is, what OpenID is all about: AUTHENTICATION!<br>
<blockquote cite="mid000601c6f892$2f425db0$090a0a0a@AMSOFTWachob"
type="cite">
<pre wrap="">
>From a user's POV, it's an authentication reuse protocol.
But it's definitely NOT an authentication protocol... in fact authentication
is totally optional. And that's a feature! At least for now...
</pre>
</blockquote>
Which is one of the major problems we pointed out...So how can this
part be out of the scope of the OpenID SPECS?<br>
<blockquote cite="mid000601c6f892$2f425db0$090a0a0a@AMSOFTWachob"
type="cite">
<pre wrap="">
-Gabe</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div><font face="Arial" size="2">Regards</font></div>
<div><font face="Arial" size="2"> </font></div>
<div><font face="Arial" size="2">Signer: Eddy Nigg, StartCom Ltd.</font></div>
<div><font face="Arial" size="2">Phone: +1.213.341.0390</font></div>
</div>
</body>
</html>