Sorry, but I'm not understanding what you are describing. I suspect you are,
still, conflating otherwise-independent architectural layers and I'm quite sure
you are describing a non-existent capability.
Making current designs attempt to cover unspecified hypothetical extensions is
typically not successful in these efforts.
d/
On 5/10/2010 8:15 PM, SitG Admin wrote:
I think you are confusing the underlying mechanism with the top-level
naming issues. OpenID is the top-level mechanism. Tor is merely
masking the means of getting /to/ the OpenID service.
*DNS* is the top-level mechanism, which OpenID (currently) utilizes as a
first step. A hidden service running through Tor could easily be
inaccessible through the public internet; no DNS entry, no IP address,
not listening on any local port. (That's more than just an OpenID
service whose means of access are "masked": it's an alternative means of
access, period. You can't "find out" the real server behind its Tor
address and use traditional DNS from then on; you can ONLY contact it
through Tor, ever.)
You asked about non-DNS discovery mechanisms, correct? Tor sort of uses
DNS, but certainly isn't the traditional "public" DNS, and there are
"real world" questions there as well. So, what sort of answer it counts
as is up to you.
-Shade
_______________________________________________
specs mailing list
[email protected]
http://lists.openid.net/mailman/listinfo/openid-specs
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
specs mailing list
[email protected]
http://lists.openid.net/mailman/listinfo/openid-specs
