<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.balloontextchar0
{mso-style-name:balloontextchar;
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Thanks Pádraic,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>My question was in reference to
the suggestion in the specification to use an XRI proxy and how it might relate
to Relaying Party not implementing any XRI or Yadis support. The spec requires
HTML discovery but not the other two, but users are expected to try their XRI
identities not knowing what the RP will support.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>In other words, does the spec
(or this group) support the idea of using an XRI proxy to convert an XRI to an
HTML page via redirection to the XRI default page (XRI Resolution 2.0 section
7.6)? If the RP does not implement XRI (assuming the language of section 7.3.3
remains unchanged), should the spec recommend at least using an XRI proxy to
fetch the default HTML page?<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>EHL<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Ps. You don’t have to use Accept:
application/xrds+xml if you use query parameter _rds_r=application/xrds+xml<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> Pádraic Brady
[mailto:padraic.brady@yahoo.com] <br>
<b>Sent:</b> Saturday, July 28, 2007 7:53 PM<br>
<b>To:</b> Eran Hammer-Lahav<br>
<b>Cc:</b> specs@openid.net<br>
<b>Subject:</b> Re: Using XRI Proxy Resolvers in OpenID discovery<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'>Hi Eran,<br>
<br>
Not sure I follow what the question is?<br>
<br>
Should one use a proxy? Yes. Since it's unlikely any platform will support XRI
resolution natively. Should the proxy be used to grab an XRDS document? Yes, if
possible, and don't forget about the "Accept: application/xrds+xml"
header which a server may use to serve up such a document immediately. Parsing
such a document is not necessarily complex though - I found after implementing
it in PHP using SimpleXML that it's a lot less complex than the specification
would suggest.<br>
<br>
I think it's a good idea to grab ALL the XRDS, and not just look for an OpenID
1.1/1.0 sub-element. In the case of failure to locate OpenID 1.1, you then have
the full document to see if it's only offering 2.0 (signon/server).<br>
<br>
Given you need a full parsing ability, the first option seems to make the most
sense. Get as much as possible upfront to avoid any second/third HTTP requests
to the User/OP. It's more efficient this way I think - if you are using
caching, XRDS lookups shouldn't occur on each and every OpenID authentication
process anyway.<br>
<br>
Regards,<br>
Pádraic<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p>
</div>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#0000BF'>Pádraic
Brady<br>
<i><a href="http://blog.astrumfutura.com" target="_blank">http://blog.astrumfutura.com</a><br>
<a href="http://www.patternsforphp.com" target="_blank">http://www.patternsforphp.com</a></i></span><o:p></o:p></p>
</div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
</body>
</html>