Isn't this concept already being implemented elsewhere?
We've got two competing .TEL applications, with very different intended structure and use. The other one seems to be pretty much a conventional TLD with normal named registrations, but this one has a different structure entirely. However, the structure seems to parallel the one that's already been established for ENUM, under e164.arpa. The latter seems to be the more logical place for it, given that it's a behind-the-scenes infrastructure database much like the established in-addr.arpa, which provides reverse lookup between IP addresses and DNS records. The ARPA TLD, while originally referring to the defunct ARPAnet, has been retroactively redesignated as the Address and Routing Parameters Area, and is the current logical place for such lookup systems, which don't need short and memorable domain names because they're carried on invisibly to the end user at the back end of software (where the naming structure need only be of interest to developers) rather than being expected to be typed into a browser. Hence, the addition of a new TLD for it is unnecessary, and creating one where an existing system in e164.arpa has already been standardized is unnecessarily duplicative, and likely to retard rather than promote deployment of phone-number-to-DNS mappings, given that people will now have to worry about which of the two contending systems to use. Yes, I know, competition is often a virtue in a free-market situation, but I'm not sure this applies to naming systems where consistency of addressing is useful. If somebody, for whatever reason, wishes to create competitive phone number registries, they are perfectly capable of doing so using subdomains of any existing domain name in an existing TLD. -- == Dan == Dan's Mail Format Site: http://mailformat.dan.info/ Dan's Web Tips: http://webtips.dan.info/ Dan's Domain Site: http://domains.dan.info/ |