Internet infrastructure company, VeriSign, has rejected a request from ICANN to suspend a service that redirects Internet users who have mistyped domain names.
Instead, the company is forming a committee to assess the issues raised by the new service, called Site Finder, and find ways to address technical issues with the service, according to a VeriSign spokesman, Tom Galvin.
The Internet Corporation for Assigned Names and Numbers (ICANN) requested last Friday that VeriSign suspend the controversial "wildcarding" service, which was introduced last week.
The statement from VeriSign came on the same day that another company, Web domain hosting company, Go Daddy Software, said that it filed a lawsuit against VeriSign in Federal District Court in Arizona over Site Finder, the second such lawsuit in as many weeks.
Like the earlier suit, which was brought by Popular Enterprises, Go Daddy's lawsuit claims that VeriSign is misusing its role as the .com and .net domain registry to muscle out competition.
VeriSign is capitalising on user confusion to direct Web browsers to the sites of VeriSign customers instead of others who might benefit from the mistypes. To counter the Site Finder effect, website owners would be forced to register every misspelled version of their domain name to prevent losing customers to paid links provided by Site Finder, Go Daddy said.
In response to mounting criticism over Site Finder, ICANN released an advisory asking VeriSign to suspend the service pending the outcome of a review from the Security and Stability Advisory Committee and the Internet Architecture Board (IAB).
The IAB report, released last Friday, was critical of the Site Finder service, which it said "interacted poorly" with any program or feature that depended on the traditional "no such name" responses for domains that do not exist.
VeriSign was sensitive to criticisms of Site Finder and was working with the Internet community to resolve technical issues, Galvin said.
However, in a letter to ICANN President and CEO. Paul Twomey. dated September 21, VeriSign executive vice-president, Russell Lewis, said it would be "premature to decide on any course of action until we first have had an opportunity to collect and review the available data."
VeriSign would take appropriate steps regarding Site Finder "after completing an assessment of any operational impact of our wildcard implementation," he said.
The company had already made improvements to Site Finder that addressed some problems with email systems and was planning others, Galvin said.
The Site Finder committee will further guide the company's response.
Although the committee has not been selected, it would be made up of individuals from the Internet community and would address technical issues and other complaints about the service, Galvin said.
VeriSign was pleased with the performance of Site Finder thus far, he said.
The site has received more than 20 million unique visitors since the service was introduced last week, averaging between 4 million and seven million per day.
Many of those users took advantage of the site's suggested links, which were grouped under the heading "Did you mean?" Galvin said.
A lesser number used the site's Search the Web and Search Popular Categories features, which include "sponsored" links paid for by VeriSign customers.
Asked about VeriSign's refusal to take down the service, ICANN spokeswoman, Mary Hewitt, said that the organisation stood by its request.
ICANN attorneys were currently reviewing the .com and .net contracts VeriSign signed with ICANN to see if Site Finder violated any provisions of those agreements, Hewitt said.
ICANN could not comment on the status of those reviews or on what steps ICANN might take if VeriSign refused to abide by the organisation's request, Hewitt said.
"It's kind of uncharted waters," she said.
A Cisco Systems fellow and IETF (Internet Engineering Task Force) chair, Harald Alvestrand, was less circumspect in his comments about Site Finder.
"VeriSign is taking choice away from users, and this is especially acute in the non-English (speakers') context," he said. "If you had error messages that were coming up in Korean or Thai and are now in English, that's not something you'd be happy with."
Alvestrand, who helped put together the IAB report on domain wildcarding, said the organisation missed an opportunity to speak out against the use of wildcards before Site Finder was announced.
Currently about 10 different top-level domains use wildcard systems similar to Site Finder, but most were low-profile country codes, he said.
The IAB didn't issue a position paper on the practice earlier because it "didn't get around to it," and because the managers of many of those country domains were "rogue operators" who were unlikely to be swayed by the group's opinion.