<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=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1028800129;
mso-list-type:hybrid;
mso-list-template-ids:-243789138 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Concerning line ~219 </span><span style='font-size:12.0pt;
font-family:"Arial","sans-serif"'><a
href="http://iss.xdi.org/moin.cgi/ForwardingService?action=AttachFile&do=get&target=iss-forwarding-v1.0-wd-03.pdf">http://iss.xdi.org/moin.cgi/ForwardingService?action=AttachFile&do=get&target=iss-forwarding-v1.0-wd-03.pdf</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Is there anywhere I can use an XDI-like service…to try out
its integration with actual openid discovery clients (pbwiki, plaxo, blogspot,
etc)?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Am I right to think that the scheme is saying that if I type in
an HXRI invoking the forwarding service, a 3xx https response may come back –
whose URL form _<i>can</i>_ be another HXRI …calling upon another
XDI-like forwarding network? That pattern of double discovery may be viable for
realty: use an i-broker governed forwarding service to locate a private
forwarding service that is not governed by i-broker vendor associations.
Some Realty MLSs would run their own XRI forwarding service, and others would want
to use the private-label services of Neustar, etc.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Ok less theory, more practice! We have a need to let query-based
openid discovery agents use their rule-rewriting expressions to produce a websso-switch
invocation URL of the form: <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial","sans-serif"'><a
href="http://swmrsso.rapmlsstg.com/sp/startSSO.ping?PartnerIdpId=rapattoni:mlsstgswmichigan:entityId">http://swmrsso.rapmlsstg.com/sp/startSSO.ping?PartnerIdpId=rapattoni:mlsstgswmichigan:entityId</a><o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial","sans-serif"'>If
I was to use i-names as the entity name for the openid entity in PartnerIdpId (</span><span
style='font-size:12.0pt;font-family:"Arial","sans-serif"'>=example/seattle/sightseeing)</span><span
style='font-size:12.0pt;font-family:"Arial","sans-serif"'>, I can see the forwarding
service producing for me, given the input </span><span style='font-size:12.0pt;
font-family:"Arial","sans-serif"'>https://xri.net/=example.personal.nickname/(+forwarding)</span><span
style='font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial","sans-serif"'><a
href="http://swmrsso.rapmlsstg.com/sp/startSSO.ping?PartnerIdpId=%3dexample%2fseattle%2fsightseeing">http://swmrsso.rapmlsstg.com/sp/startSSO.ping?PartnerIdpId=%3dexample%2fseattle%2fsightseeing</a></span><span
style='font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>is there an example forwarding service that is really capable of
this (including the url encoding)?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>(No…I cannot change the required form of the target URL,
its set by the websso-switch vendor).<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><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"'>
general-bounces@openid.net [mailto:general-bounces@openid.net] <b>On Behalf Of </b>Peter
Williams<br>
<b>Sent:</b> Sunday, December 28, 2008 8:18 PM<br>
<b>To:</b> general@openid.net<br>
<b>Subject:</b> [OpenID] XDI cross-references<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Concerning <a
href="http://iss.xdi.org/moin.cgi/ForwardingService?action=AttachFile&do=get&target=iss-forwarding-v1.0-wd-03.pdf">http://iss.xdi.org/moin.cgi/ForwardingService?action=AttachFile&do=get&target=iss-forwarding-v1.0-wd-03.pdf</a><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Do any of the XRI client library process service
elements with the forwarding metadata?<o:p></o:p></p>
<p class=MsoListParagraph><o:p> </o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Anyone ever considered letting the forwarding set
be the set of authorized redirects/forwardings, that may be used in
openid discovery?<o:p></o:p></p>
<p class=MsoListParagraph><o:p> </o:p></p>
<p class=MsoListParagraph>In a simple XRDS file implementation environment, one
can imagine the openid discovery client following the n openid URL 302
redirects, but only rely on the XRDS at the final URL if the chain of redirects
that it has just gone through is supported by the relevant XRD. (Assume that the
XRDS is served over https, that the webserver is also an OCSP responder, that
the signed OCSP response bears proxies the CA’s status statement about
the https cert of the endpoint, and has an extension bearing a mac of the XRDS.<o:p></o:p></p>
<p class=MsoListParagraph><o:p> </o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Can anyone imagine letting openid discovery follow a
chain of XRD-indicated forwardings (much like it follows chains of https 302
redirects?)<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have to assume the forwarding element is already
used in voip-applications of XRD (generated by real QXRI resolvers, obviously)
for secure/authorized call-forwarding etc.<o:p></o:p></p>
<p class=MsoListParagraph><o:p> </o:p></p>
<p class=MsoListParagraph><o:p> </o:p></p>
</div>
</div>
</body>
</html>