The ICANN community and United Nations agencies are heading for a clash, with governments accused this morning of trying to bypass the ICANN policy-making process.
According to the leader of an ICANN volunteer working group, governments and UN-affilated intergovernmental organizations (IGOs) have circumvented the usual ICANN consensus-building process in order to extract the policies they want directly from the ICANN board of directors and staff.
It’s the first time since the IANA transition, which happened less than a week ago, that governments have been accused of exploiting their special access to the board, and it may become a hot topic at next month’s ICANN 57 meeting in India.
Governments and UN agencies now stand accused of “bypassing the ICANN community” in order to achieve their policy goals.
But the policy being debated is not directly linked to the IANA transition, nor to the thoroughly debunked notion that the UN has taken over ICANN.
Indeed, the issue in question — the permanent protection of IGO acronyms in gTLDs — is almost embarrassingly narrow and predates the announcement of the IANA transition by at least three years, going back to at least 2011.
Basically, the policy questions that look set to cause even more conflict between governments and others are: should IGO acronyms be protected, and if so, how?
IGO acronyms are strings such as WIPO, UNESCO and OECD.
The ICANN board punted this question in May 2014, when it received conflicting advice from the Governmental Advisory Committee and Generic Names Supporting Organization.
Since then, a GNSO Policy Development Process working group has been working on recommendations. It has not yet issued its initial findings, but is close.
Simultaneously and separately, members of ICANN’s board and staff have been quietly talking to a handful of GAC members and IGOs about the same issue in what has become known as the “small group”.
Because it’s small. And a group.
Yesterday, ICANN divulged the consensus of the small group in a letter (pdf) to the leaders of the GNSO Council.
Its recommendations conflict in almost every respect with what the GNSO working group intends to recommend.
The small group wants ICANN to create IGOs-acronyms-only versions of the Trademark Clearinghouse database, Trademark Claims service and UDRP and URS dispute resolution mechanisms — basically “functionally equivalent” mirrors of almost all of the rights protection mechanisms currently only available to trademark owners.
They would be administered at least partially by the GAC and at no cost to the IGOs themselves (presumably meaning ICANN would pick up the tab).
It seems like a disproportionate amount of faff considering the problem ICANN is trying to solve is the vanishingly small possibility that somebody attempts to cybersquat the United Nations Entity For Gender Equality And The Empowerment Of Women (UNWOMEN) or the Postal Union Of The Americas Spain And Portugal (PUASP).
A lot of it is also in direct opposition to what the GNSO WG plans to recommend, according to chair Phil Corwin and the current draft of the WG’s recommendations.
The WG currently plans to recommend that IGOs should be allowed to use the existing URS and UDRP mechanisms to take down or take over domains that use their acronyms in bad faith. It does not currently seem to recommend anything related to Trademark Claims.
A foundational disagreement relates to the status of IGOs under the law. While IGOs in the small group seem to think they are in a special category of entity that is not subject to regular trademark law, the WG hired expert legal counsel that determined the contrary.
Corwin, in his initial response to the small group letter, said that the implications of the debate go beyond how IGO acronyms should be protected.
IGOs carried out a “near boycott” of the GNSO PDP discussions, he wrote, preferring instead to talk to the small group “behind closed doors”. He wrote:
we continually urged members of the GAC, and IGOs, to participate in our WG. That participation was so sporadic that it amounted to a near-boycott, and when IGO representatives did provide any input they stressed that they were speaking solely as individuals and were not providing the official views of the organizations that employed them.
Of course, why should they participate in the GNSO policy processes when they are permitted to pursue their goals in extended closed door discussions with the Board, and when the Board seeks no input from the GNSO in the course of those talks?
He directly linked the timing of the small group report to the expiration last Friday of ICANN’s IANA functions contract with the US Department of Commerce, and suggested that the IGO acronym issue could be a litmus test for how ICANN and governments function together under the new oversight regime.
I note that transmission of the letter has been delayed until after the completion of the IANA transition, and that the post-transition role of governments within ICANN was a central controversy surrounding the transition.
What is at stake in this matter goes far beyond the relatively rare instance in which a domain registrant infringes upon the name or acronym of an IGO and the IGO seeks relief through a CRP [Curative Rights Protection mechanism]. The larger issue is whether, in a post-transition ICANN, the GAC and the UN agencies that comprise a large portion of IGOs, will participate meaningfully in GNSO policy activities, or will seek their policy aims by bypassing the ICANN community and engaging in direct, closed door discussions with the Board.
The financial effects of this seemingly interminable debate on the gTLD industry are probably pretty minor.
Currently, all new gTLDs have temporarily blocked, from launch, all of the IGO acronyms in question. That’s roughly 200 domains per gTLD that could otherwise be sold.
Many of the strings are three, four and five-letter acronyms that could fetch “premium” prices in the open market (though, in my judgement, not much more than a couple hundreds bucks in most cases).
A small number of the acronyms, such as WHO and IDEA, are potentially more valuable.
Off the top of my head and the back of an envelope, I’d put the cost to the industry as a whole of the IGO acronym blocks probably somewhere in the very low millions.
The harms being prevented are also very minor, in my view. With a small handful of exceptions, the IGOs in question are not attractive cybersquatting targets.
But, as is so often the case in ICANN matters, the arguments in this case boil down to matters of law, principle and process much more than practical impact.
NCC Group, registry for the .trust gTLD and domain data escrow provider, provided several of the supporting stars for a UK reality TV game show that started a few weeks ago.
Hunted is a Channel 4 show in which 10 members of the public turn “fugitive” for a month.
The contestants are pursued on foot and electronically by a team of military, law enforcement and security experts.
Contestants have to keep on the move and are not allowed to leave the UK. Each fugitive team has a covert cameraman recording their escapades.
It’s basically a big televised game of hide-and-seek.
Whoever makes it 28 days without being physically captured by the “hunters” wins a share of £100,000.
NCC provides four of members of the hunter team, all from the firm’s security division.
Here’s the pre-launch trailer.
Two episodes in to the six-episode series, I’d have to say it’s a fun watch, even if you have to take the “cyber” elements slightly with a pinch of salt.
Because the “hunters” don’t actually have legal access to CCTV cameras, phone records, car registration databases and the like, that element is simulated by the show’s makers, overseen by an ex-cop independent adjudicator.
It airs on Channel 4 on Thursday nights in the UK. The first two episodes are currently available on-demand.
A Texas judge refused demands for a temporary restraining order preventing the IANA transition going ahead last weekend because the suing state attorneys general were unlikely to succeed at trial.
That was one of several reasons Judge George Hanks refused the TRO, which had been requested by the Republican AGs of Texas, Arizona, Oklahoma and Nevada.
Hanks’ order on the motion, which was published last night (pdf), said the AGs:
have not shown that there is a substantial likelihood that they will prevail on the merits of this case. Nor have they shown that there is a substantial threat that an irreparable injury will be suffered. Nor have they shown that the threated injury outweighs the threatened harm to the United States. Finally, they have not shown that granting the injunction will not disserve the public interest.
The lawsuit claims that the IANA transition, which involves the US government removing itself from its oversight roles of ICANN and DNS root zone management, represents a threat to free speech and to the stability of the .mil and .gov TLDs.
The eleventh-hour complaint was filed on Thursday, after attempts by Senator Ted Cruz and his allies to block the transition via a Congressional funding bill failed.
But Hanks ruled that the AGs claims about potential future harms amounted to no more than “speculation” and “hearsay”.
He wrote: “counsel’s statements of what ‘might’ or ‘could’ happen are insufficient to support the extraordinary relief sought in this case.”
He also pointed to one significant logical inconsistency in their argument:
Even if the Court were to find that some past harm or bad acts by the Internet Corporation for Assigned Names and Numbers (“ICANN”) impacted the interests of the States in their respective websites and alleged rights at interest, the Court notes that these past harms happened under the exact regulatory and oversight scheme that the States now seek to preserve. This, along with the lack of evidence regarding any predictable or substantially likely events, greatly undermines the States’ request for they relief they seek.
The AGs are reportedly considering their options following the ruling, and may appeal.
But another school of thought holds that the suit was largely a political gesture designed to creating talking points for the Republican party ahead of next month’s presidential election, and could be allowed to fade away.
The DNS root saw its 1,500th concurrent live TLD come into existence on Friday, just hours before the US relinquished its oversight powers.
Amazon received its delegation for .通販 (.xn--gk3at1e, Japanese for “online shopping”) and satellite TV company Hughes got .dvr, meaning “digital video recorder”.
That took the number of TLDs in the root to exactly 1,500, which is where it still stands today.
Both went live September 30, which was the final day of ICANN’s IANA contract with the US National Telecommunications and Information Administration, which expired that night.
An ICANN spokesperson confirmed that the two new gTLDs “were the last ones requiring NTIA’s approval.”
From now on, the small clerical role NTIA had when ICANN wanted to make changes to the root is no more.
The fact that it hit a nice round number the same day as ICANN oversight switched to a community-led approach is probably just a coincidence.
Amazon’s .通販 was almost banned for being too confusingly similar to “.shop”, but that ludicrous decision was later overturned.
Hughes’ .dvr was originally intended as a single-registrant “closed generic”, but is now expected to operate as a restricted but multi-registrant space.
An explosion and fire aboard a cargo ship has caused hardware destined for the ICANN’s upcoming meeting in Hyderabad to be impounded.
A welding accident caused the explosion aboard the mega container vessel as it was docked in Hamburg, on September 1 according to reports.
The resulting fire took four days for firefighters to put out, according to ICANN.
ICANN had two containers — a 40-footer and 20-footer — on the ship, moving gear from June’s Helsinki meeting to next month’s ICANN 57 in India, ICANN said.
The smaller of the two containers was close to the fire and has been “detained” in Germany where it may not be released for months or years.
It held “printers, remote participation computers, camera kits, digital signage equipment, and all network hardware and wireless equipment, including over 5 miles (8 km) of cabling”, ICANN said in a blog post.
While replacements have been secured for much of the equipment — likely at a cost of many thousands of dollars — some of the gear cannot be replaced in time for Hyderabad.
The main impact of this will be that remote meeting hubs will not be able to broadcast live into the Hyderabad venue, according to ICANN.
On-site participants may also experience slower than expected downloads due to the unavailability of the Akamai content delivery network servers the meetings usually use.
ICANN ships about 100 tonnes of kit to each of its meetings.
ICANN 57 will run from November 3 to November 9 at the International Convention Centre.