Will ICANN punt on .amazon again?
Amazon is piling pressure onto ICANN to finally approve its five-year-old gTLD applications for .amazon, but it seems to me the e-commerce giant will have a while to wait yet.
The company sent a letter to ICANN leadership this week calling on it to act quickly on the July ruling of an Independent Review Process panel that found ICANN had breached its own bylaws when it rejected the .amazon and and Chinese and Japanese transliterations.
Amazon’s letter said:
Such action is necessary because there is no sovereign right under international or national law to the name “Amazon,” because there are no well-founded and substantiated public policy reasons to block our Applications, because we are committed to using the TLDs in a respectful manner, and because the Board should respect the IRP accountability mechanism.
ICANN had denied the three applications based on nothing more than the consensus advice of its Governmental Advisory Committee, which had been swayed by the arguments of primarily Brazil and Peru that there were public policy reasons to keep the gTLD available for possible future use by its own peoples.
The string “Amazon”, among its many uses, is of course the name of a river and a rain forest that covers much of the South American continent.
But the IRP panel decided that the ICANN board should have at least required the GAC to explain its public policy arguments, rather than just accepting its advice as a mandate from on-high.
Global Domains Division chief Akram Atallah had testified before the panel that consensus GAC advice sets a bar “too high for the Board to say no.”
But the governmental objections “do not appear to be based on well-founded public policy concerns that justify the denial of the applications” the IRP panelists wrote.
The panel, in a 2-to-1 ruling, instructed ICANN to reopen Amazon’s applications.
Since the July ruling, ICANN’s board has not discussed how to proceed, but it seems likely that the matter will come up at its Montevideo, Uruguay retreat later this month.
No agenda for this meeting has yet been published, but there will be an unprecedented public webcast of the full formal board meeting, September 23.
The Amazon letter specifically asks the ICANN board of directors to not refer the .amazon matter back to the GAC for further advice, but I think that’s probably the most likely outcome.
I say this largely because while ICANN’s bylaws specifically allow it to reject GAC advice, it has cravenly avoided such a confrontation for most of its history.
It has on occasion even willfully misinterpreted GAC advice in order to appear that it has accepted it when it has not.
The GAC, compliantly, regularly provides pieces of advice that its leaders have acknowledged are deliberately vague and open to interpretation (for a reason best known to the politicians themselves).
It seems to me the most likely next step in the .amazon case is for the board to ask the GAC to reaffirm or reconsider its objection, giving the committee the chance to save face — and avoid a lengthy mediation process — by providing the board with something less than a consensus objection.
If ICANN were to do this, my feeling is that the GAC at large would probably be minded to stick to its guns.
But it only takes one government to voice opposition to advice for it to lose its “consensus” status, making it politically much easier for ICANN to ignore.
Hypothetically, the US government could return to its somewhat protectionist pre-2014 position of blocking consensus on .amazon, but that might risk fanning the flames of anti-US sentiment.
While the US no longer has its unique role in overseeing ICANN’s IANA function, it still acts as the jurisdictional overlord for the legal organization, which some other governments still hate.
A less confrontational approach might be to abstain and to allow friendly third-party governments to roadblock consensus, perhaps by emphasizing the importance of ICANN being seen to accountable in the post-transition world.
Anyway, this is just my gut premonition on how this could play out, based on the track records of ICANN and the GAC.
If ICANN can be relied on for anything, it’s to never make a decision on something today if it can be put off until tomorrow.
If you find this post or this blog useful or interestjng, please support Domain Incite, the independent source of news, analysis and opinion for the domain name industry and ICANN community.
As someone living and working in Amazon’s company town, Seattle, I can tell you that Amazon the corporation is accustomed to getting its way. They have deep pockets, persistence, and philosophically it would never occur to them that the geography they drew their name from has a better right to that name.
I neglected to mention it this time around, but there were no governmental objections to .ipiranga when the Brazilian oil company by the same name applied for the matching gTLD. If we’re going to grant IP rights to rivers, let’s at least be consistent about it.
There is no “Ipirangan” community, and it’s not even a river but a stream. The name nowadays refer to the neighborhood, so it’s as geographic as Bronx or Paddington.
But it is mentioned in your national anthem, right?
Southern Cross is mentioned in the Australian anthem too, but a .southerncross would also not raise sensitivities there.
But the objection to .AMAZON being some kind of geographic string is spurious. The reason? Because that’s only in English. In Portuguese or Spanish, which is what is spoken over the bulk of the river’s length, it would be .AMAZONAS — which Amazon the company has never laid claim to, to my knowledge.