I did actually recently suggest to some Tor devs that they should use onion://domain/ or tor://domain/
instead of http://, as they are indeed not using HTTP and this would be a nice way to indicate anonymous/non-anonymous use. But, again, legacy and usability (users these days don't even see the http://) likely mean that this won't happen, even if technically it would be cleaner. Furthermore, while you can use tor:// to indicate the change in protocol, the combinatorial issue means this won't really solve the issue of the draft, especially as names for GNS and NameCoin are really meant to be usable in any URL with any protocol (telnet://, http://, gnunet://, mailto:, etc.) in the place where there is a domain name in the URL. So it makes sense to write: tor://example.bit/ or http://example.bit/ or tor://example.gnu/ or http://example.gnu/ In fact, even tor://example.gnu/ and onion://example.gnu/ might both make sense, with the 1st using Tor to exit to the A/AAAA IP address specified in GNS, and the 2nd using Tor to go to the hidden service specified in GNS (that's one of those Tor-GNS-integration issues I predict and tried to address with my suggestion to the Tor devs). Summary: W3c approach is good to identify protocol, which may be imperfectly solved in Tor's current design/deployment; but we're discussing name resolution process, not transport protocol. So I'd say you're confusing layers. Best, Christian On 01/07/2015 01:42 AM, Rubens Kuhl wrote: >> What I’m commenting does not directly answer whether the draft fulfills the >> requirements for an application to the special needs registry. At some >> higher level I wonder that even if these names were listed there whether the >> problem of managing the identifiers will be solved. The desire to have name >> spaces besides the DNS name space is definitely legitimate, the technical >> barrier is how to know what space an identifier belongs to if the same >> syntax is shared. > > > Which perhaps suggests an W3C approach instead of an IETF one ? > httpoo://(ToR identifier) (oo for "over onion", although it makes a curious > acronym) > httpob://(name coin address) > > > Rubens > > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
