Registry Services

Reaction to VeriSign-NSI Break Up

On October 16, 2003, VeriSign announced the sale of its Network Solutions (NSI) business unit three years after its purchase from SAIC. This is a report on the historical snapshot of Network Solutions and a collection of commentaries made in response to this event...Network Solutions, Inc. was founded by Emmit J. McHenry as a joint venture with the National Science Foundation and AT&T...

ICANN and the Almost Invisible New TLD Evaluation Process

There is a worldwide interest in the extension of the namespace to include new Top-Level Domains (TLDs) and select new registries to run them. If these New TLDs are to be selected objectively, and without partisan favours to insiders, then there is a clear need for criteria and careful evaluation of lessons gained from previous TLD launches. This was the principle behind the "Proof of Concept" approach, promised by ICANN, and yet ICANN appears to have retreated to a lightweight in-house evaluation, carried out obscurely, in the hands of selected individual under a 6-month contract 4 months ago. What have we learned about Sunrise, about Landrush, about abuse of process, about implementation and enforcement of agreements, about registrars who game the system to warehouse names for themselves, about proposed marketing budgets which evaporate into thin air?

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...

Can VeriSign Sue You Over SiteFinder?

Attention so far has been focusing on the ethics of the move (positively satanic), its effects on DNS and non-Web applications (Considered Harmful), and on possible technical responses (Software Aimed at Blocking VeriSign's Search Program). On the legal side of the fence, though, we're not just talking about a can of worms. We're talking about an oil drum of Arcturan Flesh-Eating Tapeworms.

3rd Lawsuit Against VeriSign; Seeks Class Action Status

A third lawsuit has been filed late Friday in a federal district court in California against VeriSign, Inc. over its controversial DNS wildcard redirection service known as SiteFinder. It was filed by the longtime Internet litigator Ira Rothken. In addition, while two other lawsuits have been filed by Go Daddy Software, Inc. and Popular Enterprises, LLC. in Arizona and Florida, this is the first lawsuit to seek class-action status. Here is an excerpt from the "Introduction" section of this class-action lawsuit...

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...

It’s “Verisign vs. Users”

But even if the collateral damage is left out of the picture, the very idea behind SiteFinder is user-unfriendly, and that's the second half of the ALAC's note: SiteFinder is, ultimately, about short-cutting other error handling methods, and redirecting any users that enter non-existing domain names into a web browser to Verisign's own service, for commercial purposes. SiteFinder is designed so it becomes difficult to deploy superior error handling services that would compete with it -- because errors aren't flagged.

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..."

$100 Million Lawsuit Filed Against VeriSign

Popular Enterprises LLC, the parent company of Netster.com, has filed a $100 million dollar lawsuit against VeriSign, Inc. The Complaint alleges antitrust violations, unfair competition and violations of the Deceptive and Unfair Trade Practices Act based upon VeriSign's release of the Site Finder product. The suit requests injunctive relief to prevent VeriSign from operating Sitefinder, and to otherwise cease what Popular Enterprises believes to be its monopolistic practices.