ICANN

Status After ‘Hurricane SiteFinder’: Is It Over?

After roughly 19 days of its introduction, VeriSign's Site Finder service was finally shutdown on October 4, 2003 following a "Formal Deadline" issued by ICANN (previously reported here). With the plug pulled, the Internet appears to be returning to its regular status ending a historic event that can be best described as a 'Hurricane' -- a Cyber-Hurricane. What follows is a collection of commentaries and questions raised around the Net in response to this event during and after the final hours of VeriSign's deadline...

Reaction to VeriSign’s New 36-Hour Deadline

ICANN today has made a formal demand stating: "Given the magnitude of the issues that have been raised, and their potential impact on the security and stability of the Internet, the DNS and the .com and .net top level domains, VeriSign must suspend the changes to the .com and .net top-level domains introduced on 15 September 2003 by 6:00 PM PDT on 4 October 2003. Failure to comply with this demand by that time will leave ICANN with no choice but to seek promptly to enforce VeriSign's contractual obligations." What follows is a collection of commentaries made around the net and by experts in response to today's announcement...

Online Registries: The DNS and Beyond

As the world grows more connected and more complicated, we all need ways of defining, identifying and keeping track of things and cross-referencing them with their owners. The simplest way to do that is with registries -- everything from the Domesday Book, a medieval registry of land, property and people; to current-day auto registries on the one hand and the worldwide Domain Name System on the other...But now, companies and organizations have to keep track of ever more things and people, not just inside their walls but across extended organizational boundaries. Call this new wrinkle an "external registry". Finally, they may want to interact with things and people, rather than just look them up, via an "active registry".

The Value of Trust in 2007

Applications and devices like cell phones, email, search engines, and automated programs handle the error messages differently; it would be naive for VeriSign to think only humans with browsers rely on DNS. When a user enters a non-exist domain name on their cell phone the DNS error message would prevent downloading. Now cell phones download VeriSign's SiteFinder webpage and Service Providers bill the cell phone user for that extra usage. SPAM prevention programs also rely on this error message to check to see if the domain is real.

If Only Mike Knew

In the year 2000, Mike wanted "d.com" for his company website. After all, if you sneaked around these so called "reserved domains" long enough, you might be puzzled to see...say this at "x.com" or this at "z.com" or perhaps this at "q.com". As mysterious as this is, you can imagine Mike's disappointment after receiving the following email...

President of Tucows in Response to SiteFinder

I have been thinking a lot about stewardship lately in my role as CEO of Tucows and how that relates to employees, a board of directors and investors. Where I've got to, which is not necessarily relevant for this post, is that stewardship needs to exist at EVERY level of a company and a life. With the recent dustup created by Verisign's new Sitefinder service it has crystallized for me what has always bothered me about the .com/.net registry and the way Verisign has approached it.

Breaking the Internet’s Consensus Rule

The Internet, ultimately, is a fragile thing, as an entity. It depends upon the consensus of those responsible for its infrastructure to operate on a daily basis. Because of the inherent robustness as a technical architecture, there is no entity that can "break the Internet" in the sense of stopping the flow of traffic, but there are several entities that can create a variety of inconveniences, some minor and some serious, for the millions who use the Internet.

PIR Opposes SiteFinder; Will Not Implement Similar Service for .ORG

Public Interest Registry, the .ORG registry operator, sent a letter today to ICANN President and CEO Paul Twomey concerning VeriSign's implementation of a DNS wildcard redirection service commonly known as SiteFinder. The letter says that it supports ICANN's call for VeriSign to voluntarily suspend SiteFinder and the Internet Architecture Board (IAB) preliminary position paper. It goes on to say that PIR will not be implementing any DNS wildcard to the .ORG zone...

Go Daddy Sues VeriSign Over Site Finder

Go Daddy Software, Inc. has filed a lawsuit in Federal District Court in Arizona against VeriSign Inc., seeking a temporary restraining order against VeriSign's new Site Finder service, a paid-advertising page VeriSign has established on the Internet to which the traffic associated with mistyped, and other, domain names will be directed. Go Daddy's lawsuit claims that VeriSign is misusing its position as the .com and .net domain registry to gain an unfair competitive advantage by intercepting (and profiting from) internet traffic resulting from the scores of invalid domain names that are typed into users' browsers on a daily basis.

ICANN and IAB Ask VeriSign to Suspend Site Finder

The Internet Corporation for Assigned Names and Numbers (ICANN) has released an "Advisory" concerning VeriSign's deployment of DNS wildcard (Site Finder) service: "Since the deployment, ICANN has been monitoring community reaction, including analysis of the technical effects of the wildcard, and is carefully reviewing the terms of the .com and .net Registry Agreements. In response to widespread expressions of concern from the Internet community about the effects of the introduction of the wildcard..."