The Governmental Advisory Committee has advised ICANN to do as it’s told and stop listening to the views of other stakeholders, on the issue of protection mechanisms for the Red Cross.
In a barely believable piece of formal advice to the ICANN board this morning, part of its London communique (pdf), the GAC said:
the protections due to the Red Cross and Red Crescent terms and names should not be subjected to, or conditioned upon, a policy development process
That’s the GAC telling the ICANN board to do what the GAC says without involving the rest of the ICANN community, specifically the multi-stakeholder Generic Names Supporting Organization.
Some in the GNSO have already informally expressed their anger about this. More, and more formal, responses are expected to follow.
It’s a baffling GAC move given that most governments have spent much of the ICANN 50 meeting this week professing how much they support the multi-stakeholder model of internet governance.
Now the GAC is explicitly telling ICANN to ignore anyone that isn’t the GAC, on this particular issue.
That’s unprecedented, though many would say that GAC statements often sound like the existence of other advisory committees and supporting organizations is little more than an annoyance to members.
During a meeting between the ICANN board and the GAC on Tuesday, UK GAC member Mark Carvell expressed some of that frustration, saying ICANN’s approach to the issue has been “completely unacceptable”.
we’re talking about names that are protected under international law and implemented in national legislation
So, for example, if you go down Pride Street around the corner, you won’t find Red Cross Burgers. You won’t find Patisserie Croix Rouge in Paris anywhere, or in London, indeed, because it’s against the law to use those names.
So the response that we’ve had from the Board is equating these names to trademarks by referring to the GNSO response, saying that this is a matter for incorporation of policy development that would use the trademark clearinghouse.
So I just wanted to make the point here that this is completely unacceptable to us. We’re in a position as governments and administrations in implementing national law. So our advice continues to be that these names need to be protected and not subject to some policy development process that equates these names to trademarks
That point of view seems to have translated directly into the GAC’s communique today.
The GAC statement is doubly baffling because the Red Cross and Red Crescent already enjoy protections in the new gTLD program, and the GNSO has voted to make these protections permanent.
The GAC has been pushing for protections for the Red Cross for years.
It’s a noble effort in principle, designed to help thwart fraudsters who would use the Red Cross brand to bilk money out of well-meaning internet users in the wake of human tragedies such as earthquakes and tsunamis.
The ICANN board of directors first agreed to adopt such protections in 2011, when it approved the new gTLD program.
Red Cross protections were added to the program rules then on a temporary basis, pending a formal GNSO policy on the matter.
The GNSO took a while to get there, but it formally passed a resolution in November last year that would protect a list of Red Cross organizations at both the top and second levels in the new gTLD program.
So what’s the GAC’s problem?
ICANN director Chris Disspain asked Carvell during the Tuesday GAC-board session. Carvell responded:
I’m talking about our advice with regard to protection of national entities at the second level. So, for example, British Red Cross dot whatever. That protection does not exist, and is not agreed as we understand it.
The original list of Red Cross/Red Crescent strings for which the GAC demanded protection includes strings like “redcross” and “croissant-rouge”, but it does not include strings such as “americanredcross”.
There are 189 national Red Cross organizations that are not currently protected, according to the GAC.
Why are these strings not on the list?
It appears to be because the GAC didn’t ask for such protections until March this year, six months after the GNSO concluded its PDP and close to three years after the temporary protections were originally implemented.
The GAC communique from the latest Singapore meeting (pdf) contains a request for national Red Cross organizations to be protected, but I can’t find any matching GAC advice that predates March 2014.
The GAC seems to have screwed up, in other words, by not asking for all the protections it wanted three years ago.
And now it’s apparently demanding that its new, very late demands for protection get implemented by ICANN without a PDP and with no input from any other area of the ICANN community.
The GAC spent a lot of time this week talking up the multistakeholder process, but now it seems prepared to throw the concept under a bus either in the name of expediency or to cover up the fact that it seriously dropped the ball.
Nobody can deny that its heart is in the right place, but is abandoning support for multistakeholderism really the best way to go about getting what it wants, at a time when everyone is claiming governments won’t control the newly liberated ICANN?
The new gTLD applications for .wine and .vin are now live again, raising the ire of European governments.
ICANN chair Steve Crocker has written to the European Commission, along with the governments of France, Spain and the US that the three applications are once again being processed.
That’s after a 60-day temporary freeze, ostensibly in order to give the governments more time to push applicants for geographic indicator protections, expired earlier this month.
Geographic indicators are terms such as “Champagne” and “Bordeaux” which are protected under European law — they have to be produced in those regions — but not in the US and other non-EU countries.
France is expected to point to the .wine controversy as evidence of how ICANN is deficient as an organization.
“The problem is it is totally opaque, there is no transparency at all in the process,” Axelle Lemaire, minister for digital affairs, told the Financial Times today.
France also reckons ICANN’s decision will impact transatlantic trade negotiations unrelated to the domain name industry, the FT reported.
Lemaire’s comments about transparency are odd, given that pretty much the entire debate — whether in person at ICANN meetings or through correspondence — has been put on to the public record by ICANN.
The issue seems to be rather than the ICANN process does not give national governments a means to push their agendas onto the industry unless all participating governments agree.
The Governmental Advisory Committee was unable to come to a consensus on .wine and .vin — EU states wanted strong protection for GIs, but the US, Canada and Australia disagreed.
Lacking GAC consensus, ICANN had no mandate to act on requests for individual government requests.
The EC, UK, France, Spain, Italy, Portugal, Luxembourg and Switzerland then filed formal Requests for Reconsideration with ICANN, asking for the decision to be overturned.
Those RfRs were rejected by ICANN’s Board Governance Committee a month ago.
Last week Crocker wrote to governments on both sides of the debate to confirm that, with the 60 days expired and no outstanding GAC advice, .wine and .vin will proceed to contention resolution and contracting as normal.
The letters are all pretty much the same, with Crocker explaining the process to date and suggesting again that ICANN be not be the best forum for governments to hash our their disagreements over GI protections.
Crocker told (pdf) EC vice president Neelie Kroes:
should the GAC be in a position to provide any additional advice on this issue, we would welcome it. Similarly, should governments succeed in resolving these issues in other global trade fora such as the WTO [World Trade Organization] that, too, will be taken into account.
Expect the debate to continue this week at ICANN 50, the public meeting that kicked off in London yesterday.
The EU and its most-affected member states are not going to let this die.
ICANN has rejected demands by the Belgian government by giving Donuts the go-ahead to proceed with its application for .spa, which Belgium says infringes on a geographic name.
Noting that the Governmental Advisory Committee had submitted no consensus advice that Donuts .spa bid should be rejected, the ICANN board’s New gTLD Program Committee said last week “the applications will proceed through the normal process.”
That means the two-way contention set is presumably going to auction.
The English dictionary word “spa” derives from Spa, a small Belgian town with some springs.
The other applicant is Asia Spa and Wellness Promotion Council, which has made a deal with Spa to donate some of its profits to local projects and give the city some control over the registry.
Donuts refused to sign a similar deal, leading to Belgium last month asking ICANN to delegate the gTLD to ASWPC and not Donuts.
The GAC’s last word on .spa was this, from the recent Singapore meeting:
Regarding the applications for .spa, the GAC understands that the relevant parties in these discussions are the city of Spa and the applicants. The GAC has finalised its consideration of the .spa string and welcomes the report that an agreement has been reached between the city of Spa and one of the applicants.
There’s no ICANN fudging here; if the GAC wanted to issue a consensus objection it could have.
The question is: why didn’t it?
Why does the string “amazon”, which does not exactly match the name of a place in its local languages, qualify for a GAC objection, while “spa”, which exactly matches the name of a city, does not?
ICANN’s board of directors has refused to choose between the Generic Names Supporting Organization and the Governmental Advisory Committee on the issue of intergovernmental organization protections.
In a resolution last week, the board decided to approve only the parts of the GNSO’s unanimous consensus recommendations that the GAC does not disagree with.
The GNSO said last November that IGOs should not have their acronyms blocked forever at the second level in new gTLDs, going against the GAC consensus view that the acronyms should be “permanently protected”.
The GAC wants IGOs to enjoy a permanent version of the Trademark Claims notifications mechanism, whereas the GNSO thinks they should only get the 90 days enjoyed by trademark owners.
Instead of choosing a side, ICANN passed a resolution last Wednesday requesting “additional time” to reach a decision on these points of difference and said it wants to:
facilitate discussions among the relevant parties to reconcile any remaining differences between the policy recommendations and the GAC advice
The decision is not unexpected. Board member Bruce Tonkin basically revealed the board’s intention to go this way during the Singapore meeting a couple of months ago.
The differences between the GAC and the GNSO are relatively minor now, and the board did approve a large part of the GNSO’s recommendations in its resolution.
IGOs, the Olympics, Red Cross and Red Crescent will all get permanent blocks for their full names (but not acronyms) at the top level and second level in the new gTLD program.
International nongovernmental organizations (INGOs) will also get top-level blocks for their full names and protection in the style of the Trademark Claims service at the second level.
The dispute over acronyms was important because many obscure IGOs, which arguably don’t need protection from cybersquatters, have useful or potentially valuable acronyms that new gTLD registries want to keep.
Belgium wants Donuts’ application for .spa rejected after the new gTLD applicant declined to sign a deal with the city of Spa.
In a March 20 letter to ICANN, published today, the Belgian deputy prime minister Johan Vande Lanotte said “negotiations between the stakeholders are closed”, adding that Belgium:
requests the Board of Directors of the ICANN to delegate the new “.spa” gTLD to the candidate who has a formal agreement with the local authorities of Spa and in respect of the public interest.
That’s the other applicant in the two-horse .spa race, Asia Spa and Wellness Promotion Council, which has promised to earmark up to 25% of its European profits to spa-related uses in the environs of Spa.
The letter was sent a week before the Governmental Advisory Committee issued its Singapore communique, which noncommittally noted that it “welcomes” the agreement between Spa and ASWPC.
ICANN may or may not be currently in receipt of firm, consensus GAC advice to accept or reject either of the remaining .spa applications.
In Beijing a year ago, the GAC put .spa on a list of gTLD strings where “further GAC consideration may be warranted” and asked ICANN to “not proceed beyond Initial Evaluation”.
At the Durban and Buenos Aires meetings last year the GAC said ICANN should not “proceed beyond initial evaluation until the agreements between the relevant parties are reached.”
Given that Donuts and Spa evidently cannot come to an agreement, ICANN presumably remains advised to keep one or both .spa applications on hold. The advice is pretty vague.
The string “spa” is not a geographic name within the rules of the new gTLD program. Donuts argues that it’s too generic nowadays to belong just to Spa.