Governments are toying with the idea of asking ICANN for greater powers over gTLDs that match their geographic features.
The names of rivers, mountains, forests and towns could be protected under ideas bandied around at the ICANN 57 meeting in India today.
The Governmental Advisory Committee held a session this morning to discuss expanding the list of strings that already enjoy extra ICANN protections on grounds of geography.
In the 2012 application round, gTLDs matching the names or ISO acronyms of countries were banned outright.
For capital city names and non-capital names where the gTLD was meant to represent the city in question, government approval was required.
For regions on the ISO 3166 list, formal government non-objection was required whether or not the gTLD was intended to represent the region.
That led to gTLDs such as .tata, a dot-brand for Tata Group, being held up indefinitely because it matches the name of a small region of Morocco.
One applicant wound up agreeing to fund a school to the tune of $100,000 in order to get Montenegro’s support for .bar.
But other names were not protected.
Notably, the string “Amazon” was not on any of the protected lists, largely because while it’s a river and a forest it doesn’t match the name of a formal administrative region of any country.
While GAC objections ultimately killed off Amazon’s bid for .amazon (at least for now), the GAC wants to close the Amazon loophole in time for the next new gTLD application round.
The GAC basically is thinking about the power to write its own list of protected terms. It would build on the existing list to also encompass names of “geographic significance”.
GAC members would be able to submit names to the list; applicants for those names would then require non-objection letters from the relevant government(s).
Some governments, including the UK and Peru, expressed concern that “geographic significance” is a little vague.
Truly, without a narrow definition of “significance” it could turn out to be a bloody big list. The UK alone has over 48,000 towns, not to mention all the named forests, rivers and such.
Peru, one of the nations that had beef with Amazon, said it intended to send ICANN a list of all the geographic names it wants protecting, regardless of whether the GAC decides to create a new list.
Other GAC members, including Iran and Denmark, pressed how important it was for the GAC to coordinate with other parts of the ICANN community, mainly the GNSO, on geo names, to avoid overlap and conflict further down the line.
The GAC has a working group looking at the issue. It hopes to have something to recommend to the ICANN board by the Copenhagen meeting next March.
Who needs rounds? The idea of allocating new gTLDs on a first-come, first-served basis is getting some consideration at this week’s ICANN 57 meeting.
Such a move could have profound implications on the industry, creating new business opportunities while scuppering others.
Whether to shift to a FCFS model was one of many issues discussed during a session today of the GNSO’s working group tasked with looking at the next new gTLD round.
Since 2000, new gTLDs have been allocated in strict rounds, with limited application windows and often misleading guidance about when the next window would open, but it’s not written in stone that that is the way it has to be.
The idea of switching to FCFS — where any company could apply for any gTLD at any time — is not off the table.
FCSC would not mean applicants would merely have to ask for a string and automatically be granted — there’d still be multiple phases of evaluation and opportunities for others to object, so it wouldn’t be just like registering a second-level domain.
Depending on how the new process was designed, doing away with rounds could well do away with the concept of “contention” — multiple applicants simultaneously vying for the same string.
This would basically eliminated the need for auctions entirely.
No longer would an applicant be able to risk a few hundred thousand bucks in application expenses in the hope of a big private auction pay-day. Similarly, ICANN’s quarter-billion-dollar pool of last-resort auction proceeds would grow no more.
That’s potentially an upside, depending on your point of view.
On the downside, and it’s a pretty big downside, a company could work on a solid, innovative gTLD application for months only to find its chances scuppered because a competitor filed an inferior application a day earlier.
A middle way, suggested during today’s ICANN 57 session, would be a situation in which the filing of an application starts a clock of maybe a few months during which other interested parties would be able to file their own applications.
That would keep the concept of contention whilst doing away with the restrictive round-based structure, but would present plenty of new opportunities for exploitation and skulduggery.
Another consequence of the shift to FCSC could be to eliminate the concept of Community gTLDs altogether, it was suggested during today’s session.
In 2012, applicants were given the opportunity to avoid auction if they could meeting exacting “Community” standards. The trade-off is that Community gTLDs are obliged to be restricted to their designated community.
If FCSC led to contention going away, there’d be no reason for any applicant to apply for a Community gTLD that could unnecessarily burden their business model in future.
For those strongly in favor of community gTLDs, such as governments, this could be an unwelcome outcome.
Instinctively, I think FCSC would be a bad idea, but I think I’d be open to persuasion.
I think the main problem with the round-based structure today is that it’s unpredictable — nobody knows when the next round is likely to be so it’s hard to plan their new gTLD business ideas.
Sure, FCSC would bring flexibility, allowing companies to apply at times that are in tune with their business objectives, but the downsides could outweigh that benefit.
Perhaps the way to reduce unpredictability would be to put application windows on a predictable, reliable schedule — once a year for example — as was suggested by a participant or two during today’s ICANN 57 session.
The discussions in the GNSO are at a fairly early stage right now, but a switch to FCSC would be so fundamental that I think it needs to be adopted or discarded fairly quickly, if there’s ever going to be another application round.
ICANN’s transition away from US government oversight is not even a month old and the same old bullshit power struggles and existential threats appear to be in play as strongly as ever.
Governments, via the chair of the Governmental Advisory Committee, last week yet again threatened that they could withdraw from ICANN and seek refuge within the UN’s International Telecommunications Union if they don’t get what they want from the rest of the community.
It’s the kind of thing the IANA transition was supposed to minimize, but just weeks later it appears that little has really changed in the rarefied world of ICANN politicking.
Thomas Schneider, GAC chair, said this on a conference call between the ICANN board and the Generic Names Supporting Organization on Thursday:
I’m just urging you about considering what happens if many governments consider that this system does not work. They go to other institutions. If we are not able to defend public interest in this institution we need to go elsewhere, and this is exactly what is happening currently at the ITU Standardization Assembly.
This is a quite explicit threat — if governments don’t like the decisions ICANN makes, they go to the ITU instead.
It’s the same threat that has been made every year or two for pretty much ICANN’s entire history, but it’s also something that the US government removing its formal oversight of ICANN was supposed to help prevent.
So what’s this “public interest” the GAC wants to defend this time around?
It’s protections for the acronyms of intergovernmental organizations (IGOs) in gTLDs, which we blogged about a few weeks ago.
IGOs are bodies ranging from the relatively well-known, such as the World Health Organization or World Intellectual Property Organization, to the obscure, such as the European Conference of Ministers of Transport or the International Tropical Timber Organization.
According to governments, the public interest would be served if the string “itto”, for example, is reserved in every new gTLD, in other words. It’s not known if any government has passed laws protecting this and other IGO strings in their own ccTLDs, but I suspect it’s very unlikely any have.
There are about 230 such IGOs, all of which have acronyms new gTLD registries are currently temporarily banned from selling as domains.
The multi-stakeholder GNSO community is on the verge of coming up with some policy recommendations that would unblock these acronyms from sale and grant the IGOs access to the UDRP and URS mechanisms, allowing them to reclaim or suspend domains maliciously exploiting their “brands”.
The responsible GNSO working group has been coming up with these recommendations for over two years.
While the GAC and IGOs were invited to participate in the WG, and may have even attended a couple of meetings, they decided they’d have a better shot at getting what they wanted by talking directly to the ICANN board outside of the usual workflow.
The WG chair, Phil Corwin of the Internet Commerce Association, recently described IGO/GAC participation as a “near boycott”.
This reluctance to participate in formal ICANN policy-making led to the creation of the so-called “small group”, a secretive ad hoc committee that has come up with an opposing set of recommendations to tackle the same IGO acronym “problem”.
I don’t think it’s too much of a stretch to call the the small group “secretive”. While the GNSO WG’s every member is publicly identified, their every email publicly archived, their every word transcribed and published, ICANN won’t even say who is in the small group.
I asked ICANN for list of its members a couple of weeks ago and this is what I got:
The group is made up of Board representatives from the New gTLD Program Committee (NGPC), primarily, Chris Disspain; the GAC Chair; and representatives from the IGO coalition that first raised the issue with ICANN and some of whom participated in the original PDP on IGO-INGO-Red Cross-IOC protections – these would include the OECD, the UN, UPU, and WIPO.
With the publication two weeks ago of the small group’s recommendations (pdf) — which conflict with the expect GNSO recommendations — the battle lines were drawn for a fight at ICANN 57, which kicks off this week in Hyderabad, India.
Last Thursday, members of the GNSO Council, including WG chair Corwin, met telephonically with GAC chair Schneider, ICANN chair Steve Crocker and board small group lead Disspain to discuss possible ways forward.
What emerged is what Crocker would probably describe as a “knotty” situation. I’d describe it as a “process clusterfuck”, in which almost all the relevant parties appear to believe their hands are tied.
The GNSO Council feels its hands are tied for various reasons.
Council chair James Bladel explained that the GNSO Council doesn’t have the power to even enter substantive talks.
“[The GNSO Council is] not in a position to, or even authorized to, negotiate or compromise PDP recommendations that have been presented to use by a PDP working group and adopted by Council,” he said.
He went on to say that while the GNSO does have the ability to revisit PDPs, to do so would take years and undermine earlier hard-fought consensus and dissuade volunteers from participating in policy making. He said on the call:
By going back and revisiting PDPs we both undermine the work of the community and potentially could create an environment where folks are reluctant to participate in PDPs and just wait until a PDP is concluded and then get engaged at a later stage when they feel that the recommendations are more likely adopted either by the board or reconciled with GAC advice.
He added that contracted parties — registries and registrars — are only obliged to follow consensus policies that have gone through the PDP process.
Crocker and Disspain agreed that the the GAC and the GNSO appear to have their hands tied until the ICANN board makes a decision.
But its hands are also currently tied, because it only has the power to accept or reject GNSO recommendations and/or GAC advice, and it currently has neither before it.
Chair Crocker explained that the board is not able to simply impose any policy it likes — such as the small group recommendations, which have no real legitimacy — it’s limited to either rejecting whatever advice the GAC comes up with, rejecting whatever the GNSO Council approves, or rejecting both.
The GNSO WG hasn’t finished its work, though the GNSO Council is likely to approve it, and the GAC hasn’t considered the small group paper yet, though it is likely to endorse it it.
Crocker suggested that rejecting both might be the best way to get everyone around a table to try to reach consensus.
Indeed, it appears that there is no way, under ICANN’s processes, for these conflicting views to be reconciled formally at this late stage.
WG chair Corwin said that any attempt to start negotiating the issue before the WG has even finished its work should be “rejected out of hand”.
With the GNSO appearing to be putting up complex process barriers to an amicable way forward, GAC chair Schneider repeatedly stated that he was attempting to reach a pragmatic solution to the impasse.
He expressed frustration frequently throughout the call that there does not appear to be a way that the GAC’s wishes can be negotiated into a reality. It’s not even clear who the GAC should be talking to about this, he complained.
He sounds like he’s the sensible one, but remember he’s representing people who stubbornly refused to negotiate in the WG over the last two years.
Finally, he raised the specter of governments running off to the UN/ITU, something that historically has been able to put the willies up those who fully support (and in many cases make their careers out of) the ICANN multistakeholder model.
Here’s a lengthier chunk of what he said, taken from the official meeting transcript:
If it turns out that there’s no way to change something that has come out of the Policy Development Process, because formally this is not possible unless the same people would agree to get together and do the same thing over again, so maybe this is what it takes, that we need to get back or that the same thing needs to be redone with the guidance from the board.
But if then nobody takes responsibility to — in case that everybody agrees that there’s a public interest at stake here that has not been fully, adequately considered, what — so what’s the point of this institution asking governments for advice if there’s no way to actually follow up on that advice in the end?
So I’m asking quite a fundamental question, and I’m just urging you about considering what happens if many governments consider that the system does not work. They go to other institutions. They think we are not able to defend public interest in this institution. We need to go elsewhere. And this is exactly what is happening currently at the ITU Standardization Assembly, where we have discussions about protection of geographic names because — and I’m not saying this is legitimate or not — but because some governments have the feeling that this hasn’t been adequately addressed in the ICANN structure.
I’m really serious about this urge that we all work together to find solutions within ICANN, because the alternative is not necessarily better. And the world is watching what signals we give, and please be aware of that.
The proposal calls for governments to get more rights to oppose geographic new gTLD applications more or less arbitrarily.
It emerged not from any failure of ICANN policy — geographic names are already protected at the request of the GAC — but from Africa governments being pissed off that .africa is still on hold because DotConnectAfrica is suing ICANN in a California court and some batty judge granted DCA a restraining order.
It’s not really relevant to the IGO issue, nor especially relevant to the issue of governments failing to influence ICANN policy.
The key takeaway from Schneider’s remarks for me is that, despite assurances that the IANA transition was a way to bring more governments into the ICANN fold rather than seeking solace at the UN, that change of heart is yet to manifest itself.
The “I’m taking my ball and going home” threat seems to be alive and well for now.
An explosion on board a cargo ship set ICANN back $700,000, the organization has revealed.
The September 1 blast and subsequent fire, which we blogged about two weeks ago, cause equipment heading to ICANN 57 in Hyderabad to be detained by authorities.
The explosion, at the port in Hamburg, was reportedly caused by a welding accident and nobody was seriously hurt.
Now, in a blog post, ICANN said the cost of replacing the detained gear and shipping it to India was $700,000.
Hyderabad is due to kick off next week.
The ICANN blog post, from CIO Ashwin Rangan, reports that all the equipment required to run the meeting has already arrived safely.
The meeting has also been plagued by widespread reports of difficulties obtaining visas. Many have complained on social media that the process is unnecessarily unpredictable and complicated.
Many of these complaints have come from regular ICANN attendees from North America and Europe, unaccustomed to having to secure visas for international travel.
But the level of complaints has been sufficiently high that ICANN has been talking to Indian government officials about ensuring everyone who wants to attend, can.
ICANN ended its fiscal 2016 with just shy of $400 million on its balance sheet, according to its just-released financial report.
As of June 30, the organization had assets of $399.6 million, up from $376.5 million a year earlier, the statement (pdf) says.
Its revenue for the year was actually down, at $194.6 million in 2016 compared to $216.8 million in 2015.
That dip was almost entirely due to less money coming in via “last-resort” new gTLD auctions.
The growth of the gTLD business led to $74.5 million coming from registries, up from $59 million in 2015.
Registrar revenue grew from $39.3 million to $48.3 million.
Money from ccTLD registries, whose contributions are entirely voluntary, was down to $1.1 million from $2.1 million.
Expenses were up across the board, from $143 million to $131 million, largely due to $5 million increases in personnel and professional services costs.
The results do not take into account the $135 million Verisign paid for .web, which happened after the end of the fiscal year.
Auction proceeds are earmarked for some yet-unspecified community purpose and sit outside its general working capital pool. Regardless, they’re factored into these audited financial reports.
ICANN has to date taken in almost a quarter of a billion dollars from auctions. Its board recently decided to diversify how the money is invested, so the pot could well grow.