Well that is the motivation. Unfortunately there is more.<div><br></div><div>If we could map an email like identifier "<a href="mailto:acct%3Ajoe@example.com">acct:joe@example.com</a>" to</div><div><br></div><div>
<a href="http://example.com/?subject=joe@example.com">http://example.com/?subject=joe@example.com</a></div><div><br></div><div>and resolve this into an XRD, then there is no problem. Because the acct: scheme is piggy backing on the http(s) scheme.</div>
<div><br></div><div>Unfortunately when you want to legitimize a new scheme, which is actually dependent on another scheme (http(s)), by subverting the definition of related specs like the XRD spec and host-meta spec, you have a very serious problem in your hands.</div>
<div><br><div class="gmail_quote">On Mon, Nov 2, 2009 at 7:01 AM, Hannes Tschofenig <span dir="ltr"><<a href="mailto:Hannes.Tschofenig@gmx.net">Hannes.Tschofenig@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all,<br>
<br>
I read throught the Webfinger description and I was trying to figure out<br>
what the problem statement is.<br>
<br>
I really saw only one aspect discussed in more detail, namely that URIs (as<br>
used in OpenID) are difficult for users to understand. The usage of email<br>
alike addresses (namely those identifiers using username@domain) would be<br>
better.<br>
<br>
Sounds reasonable to me.<br>
<br>
Is this the motivation or is there more?<br>
<br>
Ciao<br>
Hannes<br>
<br>
PS: I noticed the statements about the privacy and spam problems and I<br>
recall similar concerns when the Dynamic Delegation Discovery System (DDDS),<br>
see <a href="http://www.ietf.org/rfc/rfc3401.txt" target="_blank">http://www.ietf.org/rfc/rfc3401.txt</a>, was developed. It allows all sorts<br>
of information being stored with an identity in the DNS (with RFC 2916 the<br>
goal was to associate other services to an E.164 number, such as SIP URIs,<br>
email addresses, etc.). When others are able to find out how to contact me<br>
easily then they can obviously use the obtained information to send unwanted<br>
traffic.<br>
<br>
_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@lists.openid.net">general@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-general" target="_blank">http://lists.openid.net/mailman/listinfo/openid-general</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><a href="http://hi.im/santosh">http://hi.im/santosh</a><br><br><br>
</div>