<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Eran,</div><div><br></div>RP's are free to decide what openID's they accept. <div><br></div><div>My concern is getting them to adopt the new XRD discovery. </div><div><br></div><div>I think that user adoption and security concerns will eventually weed out the older and less secure discovery options.</div><div><br></div><div>Some RP's may want to continue supporting rel links forever, however new features available thorough XRD will not be available via that method. I think it will naturally fall out of use.</div><div><br></div><div>I imagine that RPs will start ignoring insecure discovery. As you say there is nothing like a conformance test for openID.</div><div><br></div><div>I just don't see it being officially deprecated in the near future. </div><div><br></div><div>We will have to live with rel, Yadis and XRD discovery in the spec for some time. </div><div><br></div><div>=jbradley</div><div><br><div><div>On 8-Jan-09, at 5:54 PM, Eran Hammer-Lahav wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>On 1/8/09 12:45 PM, "John Bradley" <<a href="mailto:john.bradley@wingaa.com">john.bradley@wingaa.com</a>> wrote:<br><br><blockquote type="cite">I however don't see a move to deprecate the rel tags being acceptable to the<br></blockquote><blockquote type="cite">community at this point.<br></blockquote><br>I would argue that the community that matters, i.e. end users, could not<br>care less. It is dependency on features like this one that make OpenID less<br>secure, harder to implement, less interoperable, and look ultra geeky.<br><br>If I will have any influence on future RP adoption, I will do my best to<br>make them ignore HTML discovery completely. After all, in OpenID, it doesn't<br>seem to matter what the spec says anyway (unfortunately).<br><br>EHL<br><br></div></blockquote></div><br></div></body></html>