Afilias to extend abuse policy to .pro

Six months after acquiring RegistryPro, Afilias wants approval to extend its existing anti-abuse policy into the .pro gTLD.
The company has filed a Registry Services Evaluation Process request with ICANN for its Anti-Abuse Policy, which is apparently much the same as the one in place at .info for the last four years.
The policy would formally allow Afilias to take down .pro sites in cases of phishing, malware and other types of broadly condemned network abuse. It doesn’t appear to cover wedge issues such as cybersquatting.
Earlier this year, a DI PRO survey found that .pro was, by a large margin, the gTLD with the most instances of apparent cybersquatting among the world’s top 100 brands.
However, .pro has never been particularly known as a haven for other types of abusive practice, possibly due to the verification loops registrants need to jump through to get their domains resolving.
I understand that cleaning up and reinvigorating .pro’s image has been put firmly on the Afilias agenda in recent months. It’s a great string, and I reckon it could do well with the proper marketing.

DotConnectAfrica — disconnected from reality?

DotConnectAfrica’s campaign for .africa (or .dotafrica, depending who you talk to) is getting increasingly weird.
As you may recall, DCA is the Mauritius-based company, headed by the charismatic and telegenic entrepreneur Sophia Bekele, which has been campaigning for a .africa gTLD for the last few years.
It “accidentally” applied for “.dotafrica” — a sign of almost mind-boggling incompetence — instead of the intended “.africa”, but remains confident that ICANN will allow it to change its application to correct the error.
Despite these failings, the firm has put a lot of hard work raising the profile of the .africa gTLD, for which it should be commended. Unfortunately, it’s not going to win.
If anyone is going to get the .africa registry contract, it’s the other applicant: Uniforum, the South African ccTLD registry.
Despite this painful truth, DCA appears to be in denial.
Take this op-ed, published yesterday on CircleID.
In it, somebody from DCA (the piece does not have a byline) states:

DotConnectAfrica remains a strong contender for the DotAfrica string name and actually stands the best chance of being awarded the mandate to operate the .AFRICA gTLD registry

What’s the basis for this confidence?

[DCA] has adhered to, and respected all the guidelines of the new gTLD programme, in addition to accepting ICANN’s oversight of the entire process, unlike UniForum which might be penalized for wrongly attributing the rights of DotAfrica gTLD to the AU [African Union] instead of ICANN in direct contravention of the new gTLD programme guidelines

DCA is essentially saying that ICANN, and not the African Union, should be the body that gets to decide who should run .africa.
That’s true. It’s also complete rubbish.
Nobody, not even DCA, denies that .africa is a “geographic” gTLD application, as defined by the Applicant Guidebook.
You may have noticed that in the current new gTLD round there are no applications that are both “geographic” and contested by multiple applicants. There’s a good reason for that.
According to ICANN’s rules: “If an applicant has applied for a gTLD string that is a geographic name (as defined in this Guidebook), the applicant is required to submit documentation of support for or non-objection to its application from the relevant governments or public authorities.”
Geographic gTLDs only get approved if the government(s) of that geographic region don’t object, in other words.
These letters of support or non-objection are not being published by ICANN, but the public record has quite a bit to say about which governments support which bids.
In the case of .africa, which covers a lot of countries, ICANN requires letters of support or non-objection from 60% of the nations concerned, and no more than one letter of objection from a government.
Uniforum executives told me recently that the company has this 60% support. It also has the explicit, exclusive, unambiguous support of the African Union Commission.
Here’s what the AU has to say on the matter (pdf):

the AU Commission selected UniForum SA (the ZA Central Registry Operator or ZACR), to administer and operate dotAfrica gTLD on behalf of the African community. The endorsement of the ZACR is the only formal endorsement provided by the African Union and its member’s states with regard to dotAfrica.

If DotConnectAfrica wanted to scupper the Uniforum bid, its best bet would be to lobby African governments that are not already supporting Uniforum — such as those that are not members of the AU — in order to secure more than one letter of objection.
That wouldn’t give DCA a chance to win .africa — contested geographic gTLDs do not go to auction — but it would mean Uniforum’s bid would be rejected for want of support.
But DCA is taking a different — and completely inexplicable — approach.
In a June press release, which tried and failed to explain why DCA applied for .dotafrica instead of .africa, the company said:

Uniforum should really be worrying about the more serious problem it has on its hand, to wit: the agreement signed with the AU is with Uniforum SA/ZA Central Registry, but the putative registry operator/applicant for ‘Africa’ is UniForum SA trading as Registry.Africa.
Where is UniForum SA trading as Registry.Africa’s endorsement for ‘Africa’ gTLD? Is it the specious letter of appointment to apply for DotAfrica gTLD, or the purported agreement between the AU and Uniforum SA/ZA Central Registry? DCA Trust will be watching closely to see how UniForum will try to correct these documentation problems to ensure that no illegal acts are committed.

Did you understand that?
DCA is saying that because Uniforum plans to operate .africa under a standard “doing business as” brand of Registry.Africa — something fully disclosed in its gTLD application — its official letter of support from the AU is somehow open to debate.
To make the company look even more out of touch, DCA has recently had an unhealthy focus on the “insidious mass media manipulation” campaign that it reckons Uniforum has been waging against it. Presumably this blog post can be added to that file at DCA HQ.
I’m struggling to recall where I’ve witnessed such nutty PR before.
Oh, wait.

If DCA wants to be taken seriously it’s going to have to explain — in plain, unobfuscated English — one of two things:
1) Which governments support its application (and this letter from 2009 doesn’t count).
2) Why the 60% rule does not apply to its .africa bid.
Until either of those things are clarified, DCA’s messaging is just a confusing mess.

ICANN begins evaluating new gTLD applications

ICANN has already started formally evaluating some of the 1,930 new generic top-level domain applications it has received, according to sources.
Technical and financial evaluations are believed to have been going on for several days at the three outside firms ICANN has contracted with – Ernst & Young, KPMG and JAS Global Advisors.
ICANN staff said a few times during the Prague meeting last month that July 12 was the kick-off date for evaluations, but I’m led to believe they may have started a little later than that.
Nevertheless, they’re underway.
What’s not yet known is how – or if – the 1,930 applications will be batched into more manageable chunks.
The last official word from ICANN came on June 28, when Cherine Chalaby, chair of the board’s new gTLD program committee, said an update would be provided in about three weeks.
With that admittedly vague deadline now in the past, we can only assume that the publication of a new timetable is imminent.

American government kills off .kids.us

The US government is killing off the failed .kids.us domain, ten years after it was created by Congress.
The decision was explained in a statement posted on www.kids.us:

As a result of the changed landscape of the Internet and the many other tools that parents now have available to them to protect their children’s online experience, effective July 27, 2012, the Department of Commerce suspended the kids.us

An accompanying document (pdf) from Commerce says that .us registry operator Neustar should stop accepting new registrations and ask registrants to suspend their sites.
All .kids.us domains will be removed from the .us zone by June 27, 2013.
The .kids.us space was created by the Dot Kids Implementation and Efficiency Act of 2002 and essentially forced on Neustar as a means for some politicians to get some family-friendly fluff on their voting records.
It’s been considered an abject failure ever since, largely due to its strict content regulations and a lack of marketing.
From the Google results and the old .kids.us directory, I’d estimate the number of registrations at fewer than 100.
In the new gTLD program there are two applicants for .kids — Amazon and DotKids Foundation. There’s also an applicant for .kid and an applicant for the Russian “.children”.

Vignes out as CEO of OpenRegistry

OpenRegistry’s founding CEO, Jean-Christophe Vignes, left the position to join a Paris-based law firm last month.
He’s now senior counsel for the domain name practice at Caprioli & Associés.
Vignes said the change of jobs came as part of his family’s move to Paris and that he’s still a member of the OpenRegistry board of directors.
OpenRegistry (also known as Sensirius), which was selected as the back-end registry provider for 21 gTLD applications including .deloitte, .kpn and .schwarz, is based in Belgium.
It is believed that Hans Seeuws, Vignes’ former second in command, is now in charge at OpenRegistry.

Christian group opposes .sex, .porn, .adult

Morality In Media, one of the groups that fought the approval of .xxx for years, has launched a letter-writing campaign against the proposed .sex, .porn and .adult top-level domains.
ICANN has received a couple dozen comments of objection to the three gTLDs over the last couple of days, apparently due to this call-to-arms.
Expect more. MIM was one of the main religion-based objectors to .xxx, responsible for crapflooding ICANN with thousands of comments in the years before the gTLD was approved.
Now that .xxx has turned out to be less successful than ICM Registry hoped, MIM feels its key belief on the subject — that porn gTLDs lead to more porn — has been vindicated.
MIM president Patrick Trueman wrote in one of his comments:

During the years of this fight against the .xxx domain, we said many times that the establishment of a .xxx domain would increase, not decrease the spread of pornography on the Internet, causing even more harm to children, families and communities, and make ICANN complicit in that harm.
That prediction has been fulfilled because the porn sites on the .com domain have not vacated the .com and moved to .xxx. Rather, as we have seen, the .xxx has just added thousand of additional porn sites on the Internet and .com porn sites stayed put. ICANN bears responsibility for this. The .xxx was not needed.

For some reason, the complaints are only leveled at the three ICM Registry subsidiaries that are applying for porn-themed gTLDs, and not the other .sex applicant.
Uniregistry’s application for .sexy has not been targeted.
And MIM has apparently not read the applications it is complaining about; its call to action complains about non-porn companies having to pay “protection money” to defensively register in .sex.
However, the three ICM bids explicitly contemplate an extensive grandfathering program under which all current defensive registrations in .xxx would be reserved in .sex, .porn and .adult.

Does this sexy .sx ad portend a clash with .sex?

In the occasional DI tradition of linkbaiting Domaining.com with promises of scantily clad eye candy, I humbly invite male readers to get their goggles around this beauty:

Phwoar! Eh?
Apologies.
Anyway, there’s a serious point here.
SX Registry, which is in the process of launching the new .sx ccTLD for the recently formed territory of Sint Maarten, distributed this flyer in the goody bags at ICANN 44 in Prague last week.
The marketing was aimed at registrars, presumably, but the company’s web site has similar imagery as well.
It’s pretty clear what angle SX Registry is going for, and it could portend a clash with .sex and .sexy, which have both been proposed by applicants under ICANN’s new gTLD program.
ICM Registry (.sex), Uniregistry (.sexy) and Internet Marketing Solutions Limited (.sex) may have a potential objector on their hands.

Verisign’s .name contract up for renewal

Fresh from winning ICANN approval for its money-spinning .com franchise, Verisign is now going through the same process to renew its .name registry agreement.
Notably, the company isn’t getting the ability to raise its prices — the registry fee for a .name domain will still be fixed at $6 per name per year, according to the new contract.
There are lots of other changes, though. Many terms have been changed to make .name more in line with .net, which Verisign renegotiated last year, and with the standard new gTLD contract.
The company will, for example, be able to launch geographically focused promotions, in line with .net, and will be bound by new service level agreements, in line with new gTLDs.
While there are tweaks to the fee structure, the amount of money ICANN will reap from the deal appears to remain at the current rate of $0.25 per transaction or domain-year.
ICANN published the proposed agreement for public comment on Tuesday. They’re cutting it pretty fine — the current deal, signed in 2007, is due to expire on August 15.

.co.no opens for business after court win

The Norwegian registrant of the domain name co.no has won a court case against .no registry Norid that will allow it to finally launch as a pseudo-ccTLD, according to the company.
A Trondheim court ruled that Norid cannot revoke Elineweb’s registration of co.no for alleged policy violations, but has also ruled that the domain cannot be transferred to a third party.
Therefore, Elineweb plans to start offering third-level .co.no domain names to companies and individuals unable to register the names they want under Norid’s strict policy regime.
The company will open .co.no on a first-come, first-served basis — having already conducted sunrise and landrush periods — tomorrow at 10am Central European Time.
The full list of 70+ accredited registrars can be found here.
DI first covered the lawsuit back in October 2011.
The .co.no namespace is managed by CoDNS, a subsidiary of the registrar EuroDNS that already operates .co.nl as a pseudo-ccTLD, in partnership with Elineweb.
The two namespaces are not official ccTLDs, but they are both recognized by the Public Suffix List, which makes them behave similarly in browsers.

Microsoft, Yahoo and others involved in new dot-brand gTLD group

HSBC, Microsoft, Yahoo and jewelry maker Richemont have told ICANN they plan to form a new GNSO stakeholder group just for single-registrant gTLD registries.
The group would comprise dot-brand registries and — potentially — other types of single-user gTLD manager.
A letter (pdf) to ICANN chair Steve Crocker, signed by executives from the four companies, reads in part:

As a completely new type of contracted party, we do not have a home to represent our unique community. In addition, the existence of conflicts with other contracted parties makes it challenging for us to reside within their stakeholder group.

Combined, the companies have applied for about 30 single-registrant gTLDs, mostly corresponding to brands.
Richemont, which is applying for dot-brands including .cartier, is also applying for the keywords .jewelry and .watches as single-user spaces.
The group plans to discuss formalizing itself at the next ICANN meeting, in Toronto this October.
During the just-concluded Prague meeting, the GNSO’s existing registries stakeholder group accepted several new gTLD applicants — I believe mainly conventional registries — into the fold as observers.
How the influx of new gTLD registries will affect the GNSO’s structure was a hot topic for the Governmental Advisory Committee during the meeting too. I guess now it has some of the answers it was looking for.