Tina Dam, senior director of internationalized domain names at ICANN, has quit.
The news appears to have been broken on Twitter by Adrian Kinderis, CEO of AusRegistry, which does quite a bit of work with IDNs in the middle-east.
It’s my understanding that Dam may have actually resigned almost a month ago, during ICANN’s meeting in Cartagena.
Her move comes at an awkward time for ICANN, which is in the middle of revamping its IDN ccTLD Fast Track program, which Dam headed.
Dam has been with ICANN for many years, and is widely well-regarded by the community.
Overseeing the IDN program is a highly specialized and, one imagines, quite stressful position. Finding a qualified replacement will not be trivial.
Her name is added to the list of senior ICANN staffers to either quit or get fired over the last year, which currently numbers at least half a dozen.
.CO Internet has started allowing registrars to offer Whois privacy services for .co domains, according to Go Daddy.
In a blog post, Go Daddy’s “RachelH”, wrote:
When the Internet Corporation for Assigned Names and Numbers (ICANN) and .CO Internet S.A.S. drafted the .co policy earlier this year, they decided to hold off on private registration to prevent wrongful use of the new ccTLD — especially during the landrush. Now that .co has carved its place among popular TLDs, you can add private registration to your .co domain names.
Unless I’m mistaken, ICANN had no involvement in the creation of .co’s policies, but I don’t think that’s relevant to the news that .co domains can now be made private.
During its first several months, .CO Internet has been quite careful about appearing respectable, which is why its domains are relatively expensive, why its trademark protections were fairly stringent at launch, and why it has created new domain takedown policies.
It may be a sign that the company feels confident that its brand is fairly well-established now that it has decided to allow Whois privacy, which is quite often associated with cybersquatting (at least in some parts of the domain name community).
It could of course also be a sign that it wants to give its registrars some love – by my estimates a private registration would likely double their gross margin on a .co registration.
ICANN may have to fund some of its IDN ccTLD Fast Track program out of its own pocket, due to at least one country not paying its full fees, judging from information released this week.
ICANN had invoiced applicants for a total of $572,000, but only $106,000 had been received, according to briefing documents (pdf, page 114) presented at the ICANN board’s October 28 meeting.
The organization invoices registries $26,000 for each TLD string it evaluates, but the fees are not mandatory, for political reasons. As of October, it had presumably billed for 22 strings.
At least one country appears to have had its applications processed at a knock-down rate.
Sri Lanka, which was billed $52,000 for two strings, only paid $2,000, and the remaining $50,000 appears to have been written off as “uncollectable”.
Russia, Egypt, South Korea and Tunisia had paid their fees in full.
While the remaining 17 evaluated ccTLDs may not have paid up by October, that’s not to say they have not paid since or will not pay in future.
ICANN also plans to bill IDN ccTLDs 1-3% of annual revenue as a “contribution”, which also won’t be mandatory, but no registry has been live long enough to receive that bill yet.
A domain name registrar association from Bulgaria is laying the groundwork to appeal ICANN’s rejection of the country’s proposed Cyrillic top-level domain.
Uninet has filed a Documentary Information Disclosure Policy request, asking ICANN to publish its reasons for turning down the .бг (.bg) application and the criteria it used.
The domain, which had the backing of the Bulgarian government and people, was rejected in May on the grounds that it is “confusingly similar to an existing TLD”, believed to be Brazil’s .br.
In order to prepare for a future appeal, the Uninet organization wants ICANN to release:
1. The DNS Stability panel working criteria (or parts of it) that were applied to evaluate and subsequently reject the Bulgarian application.
2. The decision of the DNS Stability panel, used to reject the Bulgarian application.
While the ICANN panel’s decision isn’t exactly a state secret (even I have a copy), there seems to be a feeling in Bulgaria that ICANN may not have released all of its reasoning.
The document does not, for example, specify which TLD .бг is confusingly similar to.
It does, however, reveal just how strict ICANN is when it comes to evaluating IDN domains, including a default assumption that any two-letter string is confusing.
We note that two-character strings consisting of Unicode code points in the Latin, Greek, and Cyrillic script blocks are intrinsically confusable with currently defined or potential future country code TLD
We therefore apply a very conservative standard in our assessment of applied-for strings that consist of two Greek, Cyrillic, or Latin characters, including a default presumption of confusability to which exceptions may be made in specific cases.
Uninet said that the Bulgarian government plans to challenge the .бг decision if and when ICANN revises its existing IDN ccTLD Fast Track program to create an appeals process. It wrote:
Many people have criticized the lack of transparency and appeal options in this process, but after the ongoing public comment period we hope that it would be amended by the ICANN Board and the Bulgarian government (as a requester) will have the chance to apply for a re-evaluation of the proposed string.
In the meantime, the Bulgarian government’s IT ministry today started encouraging its citizens to write to ICANN to demand that its application is re-evaluated.
A handful of Bulgarian internet users have asked ICANN for the right to appeal the rejection of .бг, the proposed Cyrillic country-code top-level domain.
ICANN has received five emails from from the country in the last week, all expressing frustration that .бг (.bg) was turned down with no public explanation and no right to reply.
The string was rejected in May due to what ICANN determined was its confusing visual similarity with Brazil’s ccTLD, .br.
Polls of the Bulgarian people have been unable to find consensus on a suitable alternative, and the government has repeatedly said it would like to apply again or appeal.
Whether to introduce a right of appeal for rejected applicants is one of the topics ICANN is currently soliciting comments on as part of the review of its IDN ccTLD Fast Track program.
Bulgarian freelance developer Stoyan Danev wrote in his comment:
The Bulgarian community has clearly demonstrated that selecting another string is unacceptable and if the proposed one is not approved, Bulgaria will remain WITHOUT an IDN ccTLD. This is really against the ICANN policy of making Internet accessible to everyone.
He questioned whether .бг really is confusable with .br, linking to the Unicode web site, which suggests that б can be confused with 6 but not b, to prove his point.
Another commenter suggested that that the .бг registry could make it a matter of policy to only accept registrations at the second level that include at least one uniquely Cyrillic character.