Secure XRD 1.0 will have public key and signature in it. <br>It is currently vigorously drafted. <br><br>TC's been evaluating two types of signature: constrained XML Dsig which is essentially simplified c14n and no q-names (similar to SAML signature), and new type of very simplistic signature, which Base64 the XRD and take RSA-SHA over it (see: <a href="http://wiki.oasis-open.org/xri/XrdOne/SimpleSign">http://wiki.oasis-open.org/xri/XrdOne/SimpleSign</a>) . Majority of the TC is tending towards the former, but some members still feel that the community would feel too complicated and implementation compatibility will be an issue. <br>
<br>The XRI TC/XRD specs team would welcome your input in this regards, although, as usual, technical suggestion made here does not get into the spec because of the IPR contamination issues. <br><br>Regards, <br><br>=nat<br>
<br><br><div class="gmail_quote">On Fri, Jun 5, 2009 at 1:40 PM, Johannes Ernst <span dir="ltr"><jernst+<a href="http://openid.net">openid.net</a>@<a href="http://netmesh.us">netmesh.us</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;">
If I understand you correctly, you are essentially describing LID.<br>
<br>
<a href="http://lid.netmesh.org/wiki/LID_By_Example" target="_blank">http://lid.netmesh.org/wiki/LID_By_Example</a><div><div></div><div class="h5"><br>
<br>
<br>
<br>
On Jun 4, 2009, at 20:36, Andrew Arnott wrote:<br>
<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 class="h5">
I haven't read the XRD spec draft, so I don't know how well this would fit in, but I wonder...<br>
<br>
Could we put a public key in an XRD file, and have the authentication process be that the OP proves it has the private key, and then the public key is the claimed identifier? If we could pull this off we'd totally solve the problem of being able to change the URI or XRI identifier while still maintaining the user account at each RP; and similarly we could abandon a URL without fear of someone else picking it up and stealing the old user's identity.<br>
<br>
Basically, have many of the same benefits of XRIs today, except without the annual fee of owning a top-level i-name, and without being locked down to one XRI service. For example I have a few i-names, each with their own i-number, but these numbers aren't really portable. AFAIK I can't abandon all my i-names, then acquire all new i-names with different services and different numbers of * characters in them, and then hook up my old i-numbers and expect it all to work.<br>
<br>
Is this way off base, or a possibility?<br>
<br>
--<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></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>
</blockquote>
<br>
<br>
<br>
Johannes Ernst<br>
NetMesh Inc.<br>
<br>
<br> <br> <a href="http://netmesh.info/jernst" target="_blank">http://netmesh.info/jernst</a><br>
<br>
<br>
<br>
<br>_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net">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>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br>