The world’s newest TLD – ICANN approves .sx

ICANN’s board of directors has finally approved .sx, the new country-code top-level domain for newly autonomous Dutch territory Sint Maarten.
In an unexpected non-meeting earlier this week, the board voted to delegate .sx to SX Registry, a joint venture of Luxembourg registry startup OpenRegistry and Canadian registrar MediaFusion.
The vote had been delayed from the board’s meeting in October as SX Registry went through the required pre-delegation motions with ICANN’s IANA department.
Sint Maarten was created in October 2010 when the Netherlands Antilles (.an) split into three separate territories.
The ccTLD .cw for Curacao was assigned to the University of the Netherlands Antilles in October this year, but .bq for Bonaire, Saint Eustatius and Saba, has yet to be delegated.
The legacy .an domain is scheduled to be decommissioned before October 2014.

ICANN says sorry for crappy hotel complaint

ICANN has apologized to the government of Senegal for its uppity letter of complaint about a hotel used for its recent Dakar meeting.
As I blogged (with sarcasm) earlier this week, ICANN marketing chief Barbara Clay had written to Senegal’s telecommunications minister Moustapha Guirassy to complain that the Hotel des Almadies was not up to the expected standards.
The poor service “damaged ICANN’s reputation as well as the reputation of the Hotel and Senegal”, the letter, which has since been removed from ICANN’s web site (read it here), stated.
Clay has now written to Guirassy to apologize. The letter (pdf) reads:

The letter was sent without appropriate clearance by ICANN’s leadership and so it was not an official statement of ICANN’s position.
ICANN’s leadership, and indeed the entire ICANN community, deeply appreciate the generosity shown by Senegal in hosting our 42nd public meeting. ICANN’s leadership – and I personally – truly regret any embarrassment or distress my letter may have caused you or the Government of Senegal.
I hope you will accept this sincere expression of regret.

The $124-a-night Almadies came in for a torrent of complaints from ICANN’s At Large Advisory Committee and others due to the substandard rooms, poor wifi, rats, smells and lack of security.

DotGreen hires former Neustar exec

New gTLD applicant DotGreen has tapped former Neustar vice president Tim Switzer to be its new chief operating officer and chief financial officer.
Switzer was vice president of registry services at Neustar. It’s the first example I can recall of a senior exec from a registry services provider joining a single-gTLD applicant.
DotGreen, naturally enough, plans to apply to ICANN for the .green top-level domain next year. It’s a not-for-profit company that hopes to channel funds into environment projects.

Sedari hires Fay Howard as COO

New gTLDs start-up Sedari has recruited Fay Howard, formerly general manager of CENTR, the Council for European National Top Level Domain Registries, as its new chief operating officer.
Howard has also previously worked at Nominet and Eurid, where she wrote the winning application for the .eu registry contract, according to Sedari.
It’s one of a number of recent senior hires for the company, which came out of stealth mode this summer to provide new gTLD applicants with application and registry management services.
Last month, the company hired Philip Shepard as director of policy.

Bulgaria told to forget about .бг

ICANN CEO Rod Beckstrom has advised Bulgarians to admit defeat in their ongoing campaign to have .бг approved as a local-script top-level domain to match .bg.
The country’s application for the Cyrillic label was rejected by ICANN’s IDN ccTLD Fast Track program last year because it was found to look too similar to Brazil’s .br.
Nevertheless, the local government and domain name groups have continued to press for the right of appeal, and have indicated they may apply again.
But in an interview with Novinite published today, Beckstrom says:

I would advise the Bulgarians to go for something else. The initial application for .бг was unsuccessful.
The job of ICANN, the organization, is to implement the policies that are developed by the global communities. Those communities did not allow the initial application to go through because of potential visual confusion. So I think the Bulgarians can go back and they can choose what they want to apply for.
The Bulgarians can apply for a three-character name, they can apply for .българия in Cyrillic, it’s really up to the local community.

He goes on to say that Bulgarians could wait for a change in policies then apply again, they could change their desired string, or they could abandon their plans altogether.
However, surveys have found little appetite among the Bulgarian public for alternative strings such as .бгр, .българия, .бя or .бъл.
It’s a tricky problem for ICANN, which is first and foremost tasked with ensuring DNS stability and security.
Confusingly similar TLDs lend themselves to security risks such as phishing, and my understanding is that if .бг were to be approved it would face opposition from interests in Brazil.
The Novinite interview also touches on the possibilities of .софия and .Пловдив, to represent the Bulgarian cities of Sofia and Plovdiv.
The .бг issue was the subject of some apparently heated discussion during the recent Domain Forum new gTLDs conference in Sofia, but I understand Beckstrom had left before that part of the agenda.
You can now watch the entire Domain Forum, including Beckstrom’s introductory keynote, for free on YouTube.

Outrage! ICANN complains about crappy hotel

Sometimes ICANN’s love of procedure defies parody.
It’s no secret that the $124-a-night Hotel des Almadies used at its recent meeting in Dakar, Senegal, was not really up to the Club Med* standards that ICANN wonks are accustomed to.
The At-Large Advisory Committee even conducted a survey of its members after the meeting and found that a whopping 68% of them had complained to hotel management for one reason or another.
ICANN’s response?
It’s sent a letter to Senegal’s telecommunications minister, complete with a 20-page illustrated ALAC report going into excruciating detail not only about the shoddy facilities but also the policy background of the complaint.
Along with reports of rats, patchy Wi-Fi, “musty smells” and inadequate security, there are references to Resolution 2010.08.05.12, the ALAC/At-Large Improvements Implementation Project Plan, and Section 3.2.2.5 of the Travel Policy of the ALAC Review Final Report.
According to the letter, from marketing chief Barbara Clay, ICANN had received assurances that the hotel rooms would be renovated before the Dakar meeting kicked off.
Clay wrote that the hotel’s failure to follow up on its promises “damaged ICANN’s reputation as well as the reputation of the Hotel and Senegal” and she asks for compensation.
I’m guessing Rod Beckstrom’s not going to be on President Wade’s Christmas card list after all.
(*As anyone who has attended more than one ICANN meeting knows, they’re nothing but a week-long orgy of beach limbo parties, $20 cocktails and sordid sexual encounters with exotic prostitutes, all paid for by the humble internet-using public.)

Wanted: somebody to object to new gTLDs

ICANN is looking for somebody to object to new top-level domain applications.
It’s put out a call for an Independent Objector, whose job it will be to file formal objections to new gTLDs that he or she determines may not be in the public interest.
ICANN is looking for somebody with an in-depth knowledge of the new gTLD program and extensive experience in multinational organizations.
The IO has been a planned component of the new gTLD program for a couple of years.
The role is designed to provide a way to kill off “highly objectionable” applications in cases where the affected community may lack the resources or organization to pay for an objection.
Essentially, the IO looks at public comments filed with ICANN and decides whether opposition to a gTLD is substantial enough to warrant a formal objection.
The IO may only use two of the Applicant Guidebook’s objection mechanisms – the Community Objection and the Limited Public Interest (formerly “morality and public order”) Objection and not trademark or string confusion grounds.
My view is that we’re likely to see very few “highly objectionable” applications. And now that ICANN has agreed to fund some government objections, the IO is likely to wind up being a bit of an easy ride for whoever successfully applies for the job.
Interested parties have until December 22 to apply. The job description can be found here.

US quietly revises IANA contract

ICANN will not be allowed to do business with groups designated by the US government as terrorists, according to one of many changes that have been quietly made to the IANA contract.
The IANA contract, which gives ICANN its ability to delegate top-level domains, is up for renewal following the publication of an RFP by the Department of Commerce earlier this month.
But Commerce substantially modified the RFP a week after its initial publication. It’s now about 20 pages longer than the original document, containing many new terms and conditions.
A few changes struck me as notable.
Terrorism
Among the changes is a ban on dealing with groups classified as supporting terrorism under the US Executive Order 13224, signed by President Bush in the aftermath of the the 9/11 attacks.
That Order bans US companies from working with organizations including the IRA, Hamas and Al Qaeda.
While the addition of this clause to the IANA contract doesn’t really change anything – as a US corporation ICANN is bound to comply with US trade sanctions – it may ruffle some feathers.
The new top-level domains Applicant Guidebook banned applicants involved in “terrorism” in its fourth draft, which caused complaints from some quarters.
It was revised over a year ago to instead make reference to US legal compliance and the US Office of Foreign Assets Control and its List of Specially Designated Nationals and Blocked Persons.
Khaled Fattal of the Mulitlingual Internet Group, who first described the unqualified Guidebook ban on “terrorism” as “racist”, continued to voice opposition to this rule, most recently at the ICANN public forum in Dakar, suggesting it betrays ICANN’s American bias.
Data Rights
The revised IANA RFP also contains a new section detailing the US government’s “unlimited rights” to data and software produced by the IANA contractor.
The new RFP states: “The Government shall have… Unlimited rights in all data delivered under this contract, and in all data first produced in the performance of this contract”
“Data,” it says, “means recorded information, regardless of form or the medium on which it may be recorded. The term includes technical data and computer software. The term does not include information incidental to contract administration, such as financial, administrative, cost or pricing, or management information.”
It’s not entirely clear what this clause could potentially cover.
By it’s very nature, much of the data produced by IANA is public – it needs to be in order for the DNS to function – but could it also cover data such as redelegation communications with other governments or private DNSSEC keys?
New gTLDs
There are no big changes to the section on new gTLDs, just one minor amendment.
Whereas the old RFP said that IANA must show that ICANN “followed its policy framework” to approve a gTLD, the new version says it must have “followed its own policy framework”, which doesn’t seem to change the meaning.
Other amendments to the RFP appear to be formatting changes or clarifications.
The more substantial additions – including the terrorism and data rights sections – appear to be standard boilerplate text designed to tick some boxes required by US procurement procedure, rather than being written specifically for ICANN’s benefit.
You can download the original and revised RFP documents here.

GMO wins .tokyo deal

GMO Registry says it has won local government backing to apply to ICANN for the city top-level domain .tokyo.
The company revealed the news on its Twitter feed today, linking to this Tokyo metropolitan government announcement confirming the story.
While perhaps best-known for its planned .shop application, GMO is probably the registry services company with the most announced new gTLD back-end contract wins to date.
It is also on board to provide the registry for the Japanese regional gTLDs .okinawa and .ryukyu, as well as the brand gTLDs .hitachi and .canon. It already runs Somalia’s .so and Indonesia’s .id ccTLDs.
GMO Registry parent GMO Internet is a pretty big deal in its native Japan. Publicly listed on the Tokyo Stock Exchange, it has annual revenue of well over half a billion dollars.

CADNA asks for new gTLDs second round

The Coalition Against Domain Name Abuse, having spent quite a lot of time and effort opposing ICANN’s new top-level domains program, wants ICANN to name the date for a second round.
In a letter to president Rod Beckstrom today, which was inspired by discussions at the recent What’s At Stake conference, CADNA president Josh Bourne writes:

We ask that the ICANN Board request an Issues Report to formally initiate a policy development process to determine when the next round of new gTLD applications will occur, thereby affirming its commitment to opening a second round in a timely manner.

As I’ve noted previously, ICANN has not named the date for the second round so far because it’s promised the Governmental Advisory Committee that it will review the first round first.
But businesses from outside the domain name industry are feeling like they’re being pressured into making a decision whether to apply for a gTLD they don’t necessarily want, Bourne says.

By not disclosing when it will open future rounds of new gTLD applications, ICANN is creating a condition of scarcity that will inevitably result in a massive land rush, where entities will scramble to apply for new gTLDs for the sole purpose of hypothetically “future-proofing” their identities in the new domain name space, without any immediate intentions to use their new gTLDs for innovative means.
Disclosing when it will open a second application round will not only alleviate the anxiety that businesses are feeling, it will give ICANN the chance to quell the animosity that has developed toward it among the business community.

The whole letter is worth a read. No matter what you think of CADNA, it’s difficult to argue with Bourne’s points (though please do so in the comments if you disagree).
Scare sales tactics are already a key source of mainstream hatred for the domain name industry at the second level. Now would be a good time to prevent the same thing happening at the top level too.
It will look very bad for ICANN in a few years’ time if the root is cluttered with useless, unused gTLDs created just because companies felt pressured into defensive applications.