[OpenID] XDI cross-references

[Peter Williams]

Concerning http://iss.xdi.org/moin.cgi/ForwardingService?action=AttachFile&do=get&target=iss-forwarding-v1.0-wd-03.pdf


1.       Do any of the XRI client library process service elements with the  forwarding metadata?



2.       Anyone ever considered letting the forwarding set  be the set of authorized  redirects/forwardings, that may be used in openid discovery?



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.



3.       Can anyone imagine letting openid discovery follow a chain of XRD-indicated forwardings (much like it follows chains of https 302 redirects?)

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.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20081228/6697258c/attachment-0002.htm>