Unfortunately, having multiple resolution systems using the same
namespace and syntax does not provide a signal to denote which
resolution mechanism should be used - clearly .com is "in the DNS" and
.onion isn't -- but this doesn't scale, and simply saying "the DNS is
the only resolution system" doesn't either....
It would have been nice if ToR used onion://drugmart rather than
http://drugmart.onion, but we lost that fight a long time ago.
I have occasionally wondered whether we could define an agreed set of
levels for DNS-ish name semantics, e.g.:
* application data stream (onion)
* resolve to a perhaps nonroutable IP address that can connect to
a data stream (various LAN level proxy hacks)
* resove to an IP address that acts like a real IP address (most DNS
resolution behind a NAT)
* resolve to a real IP address (DNS resolution without a NAT)
These are just examples, please consdider the overall idea, not the color
of the bikeshed.
Regards,
John Levine, [email protected], Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
