Hugo, et al, I think the experience is exactly the opposite, i.e. these names will *always* show up in the DNS. As a consequence, I would argue that names being used for any of these purposes should not be delegated into the DNS root unless it’s for the same purpose. Thus, if the village of Elba in the state of New York, USA, which calls itself the Onion Capital of the World applied to ICANN for .onion in some future round of gTLD applications, I would hope ICANN would turn down the application on the basis that the name is already in use. I should note that not all of my colleagues agree with me. When I was chair of ICANN’s Security and Stability Advisory Committee (SSAC) we noted that .belkin was one of the undelegated names that shows up quite frequently at the root. If .belkin were delegated in the root, it would instantly change the responses those queries are currently receiving, thus raising some questions about security and/or stability for those end systems that have been generating bogus .belkin queries to root for many years.
I haven’t looked to see how often .onion and .alt show up at the root. Others on this list can or already have done so. Steve On Jul 19, 2015, at 3:26 AM, Hugo Maxwell Connery <h...@env.dtu.dk> wrote: > Hi, > > My reflections on this interesting discussion: > > Software using names under *.alt (or whatever it will be) do not use DNS, by > definition. > > Thus, there can never be a DNS name collision. It will be up to the > alternate name > resolution software, and its users, to deal with the name collision problem, > until IETF > decides to take on name management for this/these non-DNS name resolution > systems. > > So, we dont have to solve this problem. I dont believe that a registry is > required at all. > > If we do offer one, that registry should be for dual entries (name, name > resolution mechanism) > as (sex.alt, tor hidden service) and (sex.alt, GNUnet) are different things > using different > mechanisms, but the same label. > > Regards, Hugo > _______________________________________________ > 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
