Operators of dozens of ccTLDs are said to be furious that they don’t have representation on the group coordinating the transition of the IANA functions from US oversight.
The IANA Stewardship Transition Coordination Group (ICG) has been “captured” by members of ICANN’s country-code Names Supporting Organization, which does not represent all ccTLDs, according to ccTLD sources.
While the ccNSO is the official body representing ccTLDs within ICANN, many refuse to participate.
Some registries fear that signing up to ICANN and its rules may one day lead to them losing their delegations, while others have sovereignty or liability concerns.
It is believed that while 151 ccTLDs participate in the ccNSO, 104 do not.
None of these 104 are represented on the new ICG, which met for the first time to draft a charter in London last Thursday and Friday.
The ICG is tasked with holding the pen when the community writes a proposal for replacing the US government in the management of the DNS root zone and other IANA functions.
The ccTLD community was given four seats on the ICG, out of a total of 27. All four seats were taken by ccNSO members, picked by a five-person selection committee that included one non-ccNSO member.
I gather that about 20 non-ccNSO ccTLDs are up in arms about this state of affairs, which they believe has seen them “proactively excluded” from the ICG.
Some concerns originate from operators of ccTLDs for dependent territories that may face the risk of being taken over by governments in future.
Because IANA manages the DNS root zone, the transition process may ultimately impact ccTLD redelegations.
But the loudest voice, one of only two speaking on the record so far, is India’s government-established National Internet Exchange of India, which runs .in.
Dr Govind (apparently he doesn’t use his first name), CEO of NIXI, said in a statement last week:
Clearly the process has already been captured by a subset of the ccTLD community. The selection process controlled by the ccNSO resulted in all four seats being assigned to their members. A significant section of the ccTLD Registry operator community do not share the objectives of the ccNSO membership are now excluded from the process.
Balazs Martos, registry manager of Hungary’s .hu, added:
I am very concerned that the ccNSO seem to feel they speak for the whole ccTLD Community when dealing with every IANA matter. They do not, .HU is an IANA service user, but we are not a member of the ccNSO.
The joint statement also raises concerns about “cultural diversity”, which seems like a cheap move played from a position in the deck close to the race card.
The ccTLD representation on the ICG comprises the UK, New Zealand, China and Nigeria.
The chair of the ccNSO, .ca’s Byron Holland, has stated that the way the these four were selected from the 12 candidates (two of whom were non-ccNSO) was a “very difficult task”.
The selection committee had to consider factors such as geography, registry size, candidate expertise and available time, governance structure and business model, Holland said.
Blogging last week, addressing Govind’s concerns if not directly acknowledging them, he wrote:
Given the criteria we had to balance, there were no ‘reserved’ seats for any one group. The fact is four seats only allowed us to ensure some – not all – of the criteria were met. The discussion was difficult and the outcome was not unanimous. We did, however, reach consensus. In paring this list down to the final four, we balanced the selection criteria – balance being the keyword here. Geographic diversity is a good example of this – while there are five ICANN-defined geographic regions, we only had four seats on the Coordination Committee.
Did we meet the all of the criteria set out at the beginning of the process? No, but given the constraints we were facing – four seats to represent a community as large and diverse as ccTLDs – I have no hesitation in endorsing each of them for their ability to be representative of the global ccTLD community – both ccNSO members and non-members – effectively.
Top Level Design has scored a bit of a coup for its forthcoming .wiki gTLD — Wikimedia Foundation, which runs Wikipedia, has signed up as an anchor tenant.
According to the registry, Wikimedia will use w.wiki as a URL shortener and they’re in talks about other domains.
The company has also applied to ICANN to release hundreds of two-letter language codes that the foundation wants to use for language-specific short links.
The deal is reminiscent of .CO Internet’s launch, when it allocated the now-ubiquitous t.co for Twitter’s in-house URL shortener, giving it a much-needed marketing boost.
The deal for two-letter domains stands only a slim chance of of being ready in time for .wiki’s general availability, scheduled for May 26, in my view.
Under ICANN’s standard Registry Agreement, all two-character strings are blocked, in order to avoid clashes with country codes used in the ccTLD naming schema.
Top Level Design has now used the Registry Services Evaluation Process to try to get 179 two-letter strings, each of which represents a language code, unblocked.
Wikimedia explicitly endorses the proposal, in a letter attached to the March 11 RSEP (pdf)
The organization plans to use domains such as fr.wiki to redirect to French-language Wikipedia pages and so forth.
It remains to be seen whether ICANN will approve the request. It’s previously been envisaged that registries would approach each country individually to have its ccTLD’s matching string released.
Top Level Design points out that the strings it wants unblocked are from the ISO 639-1 language codes list, not the ISO 3166-1 lists from which ccTLD names are drawn.
But it’s a bit of an argument to nowhere — the strings are identical in most cases.
Under the RSEP policy, Top Level Design really should have been given a preliminary determination by now. It filed its request March 11 but it was only posted last week.
The clock, which gives ICANN 15 days to give the nod or not, may have only just started.
After the preliminary determination, there would be a public comment period and a board of directors decision. The timetable for this would not allow .wiki to launch with the two-letter names active.
But even with the delay, it seems that the registry will be coming out of the door with at least one strong anchor tenant, which is something most new gTLDs have so far failed to manage.
ICANN will soon remove 11 experimental internationalized domain name TLDs from the domain name system.
The TLDs, which represent “.test” in nine scripts and 10 languages, were added to the root almost exactly six years ago in preparation for ICANN’s IDN ccTLDs program.
Now that the program is quite mature, with a few dozen IDN ccTLDs live on the internet with no major reported problems, ICANN has decided that the test TLDs are no longer required.
They will be removed from the DNS root zone on October 31, ICANN said.
The fifteenth installment of dotShabaka Registry’s journal, charting its progress towards becoming one of the first new gTLDs to go live, written by general manager Yasmin Omer.
Thursday 3 October 2013
At a time when ICANN has hit the ‘pause’ button on the new gTLD program in order to assess the impact of “name collisions” on the security and stability of the DNS, we were surprised to see the ICANN Board approve the delegation of ایران., the IDN ccTLD for the Islamic Republic of Iran. While we understand the many distinctions between a ccTLD and a gTLD, the DNS does not make any such distinction.
As we’ve heard from Paul Mockapetris and John Crain recently in their interviews posted on the ICANN website, name collisions (or, more accurately, NX Domain responses) is not a new phenomenon; they have been evident with the introduction of any TLD and with existing TLDs in the root. Experience has shown that steps have been taken to successfully resolve the issues. We understand that ICANN is concerned that the use of NX Domain responses has the potential to create confusion with the introduction of new TLDs into the DNS.
As a contracted party with ICANN, شبكة. (an IDN gTLD) is unable to be delegated as we wait the outcomes of ICANN’s deliberations on name collisions. We have paid our $185,000 application fee, we have undertaken a very resource intensive exercise to ensure a compliant application, we have passed Initial Evaluation, we have signed a registry agreement with ICANN, we have passed pre-delegation testing and yet we sit and wait.
Our understanding of the IDN ccTLD fast track process is that it is much less rigorous, the application fee is voluntary, there is no requirement to enter into a contract with ICANN, the TLD can develop a launch strategy that is not restricted by ICANN mandated rights protection mechanisms, and any contribution to ICANN’s budget is voluntary. But because this is a ccTLD and not a new gTLD, the Board has seen fit to approve this delegation request at this time despite the serious conversation going on in the community about name collisions.
As we said previously, the DNS does not distinguish between a ccTLD or a gTLD, or for that matter an IDN ccTLD or an IDN gTLD. We would appreciate an explanation as to why we sit and wait for delegation while the IDN ccTLD is approved.
Read previous and future diary entries here.
The .tk domain is now the biggest ccTLD in the world, according to the latest stats from Centr.
In its just-published biannual Domainwire Stat Report, Centr says that .tk had 16.7 million registered domains in April, taking the #1 spot in the league table for the first time.
It now out-ranks Germany’s .de (15.4 million), the United Kingdom’s .uk (10.5 million), China’s .cn (7.5 million) and the Netherland’s .nl (5.2 million), despite Tokelau having a population of less than 1,500.
The reason for its success, of course, is that .tk domains are free to register. The ccTLD frequently pops up towards the top of abuse lists for that very reason.
At 54.7%, .tk wasn’t the fastest-growing ccTLD over the six months covered by Centr’s report, however. That honor belongs to .cn, which bounced back from previous declines with an 82.7% growth rate.