This was proposed in the working group. It obviously doesn't work, first because TOR can't come up with that kind of money, but second because TOR doesn't want a TLD (hellekin's erroneous statements notwithstanding). What they want is a special-use name. A domain name does not accomplish the intended purpose, because it has to be resolved by sending a query to a DNS server. A third objection was one Ed raised earlier for an unrelated reason: we can't assume that the TOR project will continue to exist as an entity that can own a delegation. What happens when that stops? Does the Church of Anatman get to buy the domain and start snooping on TOR connections?
Well do they want a TLD but they don’t have the money? or don’t want a TLD? perhaps the problem is in how the TLD program treats them, in which case the answer should be on the ICANN side.
If they are using the string ‘onion’ as a TLD, within the global DNS, then they DO want a TLD, how they use it is similar to what corporates are doing with .BRANDs.
I don’t like setting things in stone forever, I agree with the assessment on “what happens if TOR ceases to exist”, but the answer can’t be, lets put it in an RFC where we run the risk of being black listed in code potentially forever. Quoting Paul Vixie on the 100-year cycle, in 100 years, we’ll have to wait 100 more years for it to be released, that will certainly create more potential problems.
A fourth objection which I don't think was raised is that this doesn't work for .local or any of the other special-use names, and if it doesn't work for them, it doesn't make sense to try to make it work specifically for .onion. Why is .onion special? Should Apple or Microsoft be asked to pay $200k to reserve the .local TLD?
Having this mechanism for reserving special use names, creates two different authorities managing the same namespace, this will require tight coordination as well as clear and transparent guidelines to make it work.
If we are talking about private namespaces, they should be treated as such and we’ll have to come up with another way of dealing with name collisions.
— Francisco Obispo Uniregistry Inc. On 15 Jul 2015, at 12:59, Ted Lemon wrote: _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
