Unclear if software makers will support all new top level domain names.
One issue for top level domain name applicants is getting software makers, such as e-mail software companies, to approve their top level domains and make them work with their software.
The second draft guidebook for new TLD applicants provides a lengthy warning about this, stating that applicants “may find themselves expending considerable efforts working with providers to achieve acceptance of their new top-level domain.”
One of my comments to ICANN was asking if it had communicated with any of the larger software providers to ensure they supported new TLDs. ICANN addressed this concern on page 68 of its comment analysis in its “Root Zone Scaling” section:
Some of the comments are also not directly related to number of additional TLDs but to side effects that could be an issue with any number of additions. Some of these concerns, such as the acceptance of a TLD by software, have already been demonstrated in previous rounds of expansion and have proven not to be a threat to the system as a whole.
If they’ve been demonstrated in previous rounds, why include such a lengthy warning to applicants? Perhaps my comment was attributed to the wrong issue, as here ICANN is addressing the issue of root zone scaling.
Even more confusing is that a response on page 79 under “DNS Stability and String Requirements: Interoperability” seems to contradict ICANN’s first response:
While ICANN does have as its core mission statement to make the Internet interoperable, stable, and secure, it is beyond the capability and scope of ICANN to ensure acceptance of any topâ€level domain by all software manufacturers. Indeed, some software manufacturers may choose to disallow certain TLDs for their own reasons. ICANN can and does document and publicize the strings allocated for TLD use; however, software developers are ultimately responsible to ensure their applications work with the changing DNS environment. ICANN will continue to use the tools at its disposal to ensure acceptance of new TLDs by software applications. Those tools include: public relations campaigns, technical papers, and participation in public meetings.
So apparently it’s not an issue, but it is? Or it’s an issue for each individual registry, but not for the DNS as a whole?