+1
The issue not being with ONION per se, but with the .CARROTs and the
.FOOs of the future, having a reserved TLD/namespace with a registry
along with a well defined process on how to do reserve names should be
the way to go.
We also need to close the doors to those who decide to ignore whatever
guidelines we come up with and start using .CARROT and expect the IETF
to reserve it for them.
Regards,
—
Francisco Obispo
Uniregistry Inc.
On 17 Jul 2015, at 12:07, Paul Vixie wrote:
by 6761, .ONION is a valid request and your papers are in order. i
don't
love it and i wish we had a more scalable framework, but by the rules
of
this game, .ONION should be approved.
but we should also improve the rules to something scalable, like a
single exit gateway from the internet namespace into non-internet
namespaces.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
