Registry Services

Languages in the Root: A TLD Launch Strategy Based on ISO 639

TLD registrations in the Internet's root-zone file currently are divided into two broad classifications: generic and country-code top-level domains. With respect to the latter classification, no new "strategy" is required to add further ccTLDs as a relatively well-working process is already in place to integrate the occasional new country-code top-level domain. With one of these two classifications under reasonably sound management, it is therefore perfectly understandable to see that the ICANN organization consequently views its obligation to "Define and implement a predictable strategy for selecting new TLDs" as a mandate "to begin the process of allocating and implementing new gTLDs"... the flaw in this conclusion, however, stems from the presumption that the Internet's taxonomy must necessarily contain only the two above-so-mentioned broad classifications. I am proposing a third TLD classification -- based on languages.

VeriSign’s Anti-Trust Claim Against ICANN Dismissed

ICANN confirmed today that Judge A. Howard Matz of the U.S. District Court, Central District of California has issued an order dismissing VeriSign, Inc.'s anti-trust claims against ICANN, with prejudice. In dismissing VeriSign's anti-trust claims, Judge Matz noted that VeriSign had failed in its first amended complaint to sufficiently allege an anti-trust claim.

Domain Registry Models: Thin or Thick?

The domain registrars discussion -- despite the occasional bizarrity -- mostly demonstrates that there is no unanimity among registrars on this issue. So, what arguments can be made in favor of either model, from a registrant's point of view? The thick domain registry model -- under the assumption that registries are more diligent with registrant data than some registrars may be -- helps take care of escrow concerns...

Sex.com Settles Monumental Case Against VeriSign/Network Solutions

Sex.com announced today a final settlement with VeriSign (formerly Network Solutions, Inc.), concluding a six-year legal fight that set several important precedents for the future of the Internet. After the Ninth Circuit Court of Appeals granted Sex.Com a sweeping victory that held VeriSign/Network Solutions, Inc. (collectively "VeriSign") strictly responsible for mishandling the famous domain name, Sex.Com and VeriSign have settled Sex.Com's lawsuit against VeriSign.

New TLD Public Comments: Jumping-to-Conclusions?

Having been involved in the whole TLD issue since its inception, back in the ancient history of the mid-1990's, one would think that nothing would surprise me anymore. As it turns out, however, watching the comments on ICANN's public comment list with respect to the new sTLD proposals, I find that I'm taken-back by some of the kinds of comments I'm seeing.

ICANN Explains Why Judge Should Dismiss VeriSign’s Lawsuit

In a 33-page motion filed on Monday, April 5, 2004, ICANN has asked a federal judge in Los Angeles to dismiss VeriSign's recent lawsuit filed against the non-profit organization. More specifically, the filed motion has asked the court to "dismiss VeriSign's first six claims for relief with prejudice," which are...

Top-Level Domains for Addressing by Physical Context

This article proposes the reservation of a special use TLD to allow a more convenient addressing of devices by general physical location or context. ...As wireless networking and devices become more common there may be a need for a convenient way to address hosts by physical location or context, especially when the users themselves are using mobile or wearable devices.

Did ICANN Over Regulate VeriSign?

CircleID recently interviewed Jonathan Weinberg, Professor of Law at Wayne State University to discuss legal and regulatory issues that have been raised against Internet Corporation For Assigned Names and Numbers (ICANN). VeriSign, the registry operator of the two most popular top-level domains .com and .net, filed a lawsuit against ICANN on February 26, 2004 complaining that the Internet regulatory body has extended "its authority beyond the scope of its contracts". Did ICANN cross its contractual boundaries? To what extent does ICANN's contract limit its technical coordination functions and how much of a threat does VeriSign's lawsuit impose? Jonathan Weinberg explains...

TLD for Online Communities and Social Networking?

A company called PW Registry Corporation makes the following announcement regarding the .PW ccTLD originally designated for the country of Palau: "The PW Registry Corporation announced today plans for the activation of the PW top- level domain (TLD), the Internet's first and only domain extension devoted to "Communities of Shared Interests". Unlike other domain extensions, such as .com, .biz, and .info, PW is aimed at providing individuals and consumer/affinity organizations a highly-personalized, permanent and portable e-mail address and a managed platform for community and social networking."

Where Did the .Root Top-Level Domain Come From?

It was pointed out to me the other day that the ICANN/NTIA/Verisign root zone file contains a previously undiscussed top level domain. The contents of this TLD suggest that it was created by Verisign, the company that actually constructs the root zone file used by the dominant set of root servers. (The same zone file is also used by at least one of the competing root systems.) That TLD is .root. It's existence is as real as any other TLD such as .com or .org...