+1.
I don’t think IETF should be chasing around widely used TLDs and
trying to block them, it will be a never ending chase.
We are trying to mitigate against unknowns and perhaps the best solution
is to have the TOR folks apply for .ONION on the next round of TLD
application and get a fully qualified delegation.
Basically saying: If you need a globally unique identifier in the DNS,
you must register it with the competent entity. If noy, you run the risk
of having your users leak their queries and possibly connect to the
wrong service. This should make a better proposal for standard,
basically reinforcing the one DNS one Internet message, and not the
“Make sure you are leaking enough queries so that the IETF can then
reserve the name for you”.
Who are we trying to protect with this remedy? TOR users? have they
shown any interest in being protected?
—
Francisco Obispo
Uniregistry Inc.
On 15 Jul 2015, at 12:24, Rubens Kuhl wrote:
Em 15/07/2015, à(s) 16:21:000, hellekin <helle...@gnu.org> escreveu:
On 07/15/2015 03:46 PM, Edward Lewis wrote:
What if I copied the onion draft, changed all of the uses of onion
to
carrot, and then threw in some supporting documents to describe some
other system that used carrot as it's base identifier? On the heels
of onion's admission to the Special Use Domain Names registry, could
I expect to have carrot admitted too?
Do you have running code for carrot?
The ToR source code, with all occurrences of onion replaced by carrot.
Rubens
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
