Latest news of the domain name industry

Recent Posts

ICANN may kick .xxx into new gTLD round

Kevin Murphy, March 27, 2010, Domain Registries

ICANN has chosen to deal with the controversial .xxx TLD application by leaving essentially all options, including urging it into the next gTLD round, wide open.

ICM Registry had pushed for a speedy resolution to its long-running application, following the Independent Review Panel decision that went in its favour last month, but it hasn’t got one.

In Nairobi, ICANN’s board asked ICANN’s staff to tell it what its options were for dealing with the ruling, and staff today responded with this flowchart. Oh, and this flowchart.

It seems that these options are still on the table: (continue reading)

The most confusing new gTLDs (allegedly)

Kevin Murphy, March 26, 2010, Domain Registries

I don’t know how I missed it until today, but I’ve discovered ICANN has a web-based tool that will be used to determine whether new gTLDs could be confused with existing strings.

The Sword Group algorithm compares applied-for strings with a list of existing TLDs and reserved words such as “icann” and “ripe”.

It looks for “visual similarity”, which means not only common sequences of characters but also the pixel-by-pixel similarities of each character.

Numerical scores are assigned. Any match scoring below 30 is not considered worthy of reporting.

As an experiment, I ran each of the strings on newTLDs.tv’s list of publicly announced TLD hopefuls through the available “pre-production” algorithm.

Here are my findings.

1. The algorithm is pretty much worthless. (continue reading)

Pornographers still hate .xxx

Kevin Murphy, March 24, 2010, Domain Registries

The Free Speech Coalition, a trade group for the porn industry, has condemned the proposed .xxx top-level domain as “untenable” and “detrimental”.

In a letter to ICANN, FSC executive director Diane Duke challenged ICANN’s board to “settle the issue once and for all by going to the actual community to test the application’s true level of support”.

The FSC is concerned that the introduction of .xxx, as proposed and pursued by ICM Registry for the last 10 years, will inevitably lead to government regulation of the online porn industry.

Duke wrote: “a proposal for a ‘Sponsored’ top-level domain by a company that is not of the industry, with the added intent to ‘regulate’ an industry it knows nothing about, is simply untenable”.

The FSC has an even bigger problem with IFFOR, the International Foundation for Online Responsibility, the group set up by ICM to act as its sponsoring organisation

IFFOR – a bit of a hack to get around the fact that ICM was essentially applying for a gTLD during a “sponsored” TLD round – was loosely modelled on ICANN’s own bottoms-up structure, with four supporting organisations creating policy for .xxx domains.

Judging by this flowchart, which is open to interpretation, the adult industry would control less than half the votes.

“Our resolute position is that no self-respecting industry would ever agree to have a minority voice on a board tasked with setting critical policies for its members,” Duke wrote.

While ICANN ultimately rejected .xxx due to the lack of community support, ICM did manage to get some support from other areas of the adult community back in 2005.

ICANN was found at fault when it rejected .xxx. The question now is whether ICANN decides to stand by its first decision, to approve .xxx, or its second, to reject it.

Bottom line: It can’t win either way.

Dot-XXX lights fire under ICANN’s feet

Kevin Murphy, March 22, 2010, Domain Registries

ICM Registry has urged ICANN to stop messing around and finalise the contract that would add .xxx to the domain name system.

“There is no legitimate obstacle to the approval of ICM’s registry agreement,” ICM chair Stuart Lawley said in a letter to ICANN yesterday. “We can see no reason for further delay in the process of approving ICM’s registry agreement”.

At its Nairobi meeting earlier this month, ICANN’s board decided to hand the problem of how to handle .xxx to its staff, saying it “wishes to create a transparent set of process options which can be published for public comment.”

ICM now claims that no such process options are necessary. The .post application, Lawley said, was approved last December, six years after it was made, without the need for any new processes.

There are some differences between .post and .xxx, of course. While the .xxx application has previously been approved, it has also previously been rejected.

It is back on the table following an Independent Review Panel decision that ICANN broke its fairness rules by singling out ICM for special treatment.

Lawley reminds ICANN of as much several times in his latest letter, which can be found here.

ICANN’s staff is expected to deliver its process options next week. There will be a period of public comment, and the board will have to make a call by its June meeting in Brussels.

ICANN: .xxx is not approved

Kevin Murphy, March 12, 2010, Domain Registries

ICANN never makes a decision if it can make a process instead, and that seems to be the case with the board’s latest call on .xxx.

The board voted this morning to kick ICM’s proposal until after the Brussels meeting in June, on the basis that it needs a process by which it can approve .xxx.

While this is mixed news for ICM – it’s not what it hoped for but the company still has a pretty good chance of getting what it wants – the language used in the resolution clearly indicates that the board believes .xxx is currently in an unapproved state: (continue reading)