The .amazon argy-bargy is STILL going on – and Uncle Sam has had enough with ICANN

Will Amazon finally get hold of its internet namesake?

Analysis Enough’s enough. That was the message from the US government this weekend at an international meeting where the creation of a new internet space – .amazon – was again the subject of heated debate.

“The United States does not support further intervention that effectively works to prevent or delay the delegation of .amazon and and we do not believe that it is required,” its representative told a meeting of governments in Montreal, Canada, organized by DNS overlord ICANN.

The intervention came after Brazil’s government representative argued that the long-running dispute between South American governments and the US online retail giant be extended again to allow for a “mutually acceptable solution” to be reached.

That negotiation has been going over for over a year with no sign of resolution but Brazil promises that this time will be different. As it did last time. And the time before that.

Agreement seems unlikely however. While arguing that the eight ACTO (Amazon Cooperation Treaty Organization) countries felt there was room for a “possible compromise,” if an independent mediator was hired to negotiate the issue, Brazil also stated that the word “Amazon” was its “birthright”. The current plan to approve .amazon and give it to the US retailer would “run roughshod over the concerns and cultural heritage of eight nations and tens of millions of people,” it said.

It’s been seven-and-a-half years since Amazon applied for its online namesake with DNS overseer ICANN and initially everything seemed fine: dozens of other companies had applied for, and been given permission to run, their company names as separate pieces of the internet.

But that all changed following Edward Snowden's revelations of mass surveillance by the US, including of the mobile phone of Brazil’s then-president. Suddenly, Brazil – later joined by other governments – was appalled that anyone would consider use of the name “amazon” online.

It made a big fuss and the US government decided to stay out of the way, which led to the Governmental Advisory Committee (GAC) asking ICANN to reject the application. Which ICANN then did.

How about 'no'?

But both groups had reckoned without Amazon’s determination. The company spent years and millions of dollars going through ICANN’s cycle of review processes before a panel of independent judges finally decided that the decision to kill .amazon wasn’t valid for the simple reason that neither the governments nor ICANN had ever given an actual reason for denying it.

That led to an extended period of negotiations between ACTO and Amazon that went nowhere, finally prompting ICANN’s Board to tell its CEO to sort out the issue personally. The CEO’s efforts to even hold a meeting kept being put off; one time after he had flown to Brazil and was waiting in a hotel room. The ACTO countries blamed a crisis in Venezuela for not being able to discuss things that time.

And so, fed up, ICANN finally stood up to the governments and said it was going to approve .amazon and give it to Amazon – but only after yet another comment period and making it clear it was prepared to delay the decision again if asked.

That was back in March. But despite what looked like determination on ICANN’s part in May, the issue has continued to drag on.

ICANN took until September to put out Amazon’s “public interest commitments” – effectively how the web giant will run the .amazon registry – for review, going out of its way to make the public comment period difficult to find; presumably in an effort to limit input.

Regardless, Brazil and others found the comment period and sent in furious responses claiming that approving .amazon would be equivalent to an “expropriation from the Amazon countries and ACTO of their right to use and be recognized by the name ‘Amazon’.”

Groundhog Day

At a meeting of governments on Sunday [slides here [PDF]], Brazil tried to throw another spanner in the works, calling for the GAC to formally “advise” the ICANN Board that it must hold off approving .amazon and instead hire an independent mediator to start the process all over again (see video at 22 minutes in).

It was at this point that the US government (35 mins in) – which persistently tires of ICANN’s preference for delay and process over resolution – stepped in. “The United States does not support further GAC advice on the .amazon issue. Any further questions from the GAC to the Board on this matter we believe is unwarranted,” its representative stated.

As for Brazil’s “birthright”, it was sick of that argument too. “We are unaware of any international consensus that recognizes inherent governmental rights and geographic names. Discussions regarding protections of geographic names is the responsibility of other forums and therefore should be discussed and those relevant and appropriate forums.”

Amazon CEO Jeff Bezos

Jeff Bezos finally gets .Amazon after DNS overlord ICANN runs out of excuses to delay decision any further


And just to make things really clear: “It is the position of the United States that the Board’s various decisions authorizing ICANN to move forward with processing the application are consistent with all relevant GAC advice.”

The US was supported by Israel but then, reflecting global politics more than the .amazon issue, representatives from China, the European Commission (EC), Switzerland, Portugal and Belgium all weighed in. They all argued for more negotiation, and the Portuguese government went so far as to argue that approving .amazon without more negotiations would set a “terrible precedent.”

As things stand, as the ICANN meeting continues, Brazil has conceded it won’t be able to get formal GAC advice telling ICANN that it has to prepare yet more negotiation. But whether ICANN follows its own process and hands .amazon to Amazon over the objections of other governments is – yet again – undecided.

One indication that ICANN is going to fall back on its death-by-process default is that it has not added the .amazon issue to its Board meeting at the end of the week. That would have been the logical time to decide the issue once and for all. But it seems that, so long as some governments remain unhappy and are willing to say as much, there is always another way to not make a decision.

Amazon has previously offered millions of dollars in free Kindles and cloud hosting to ACTO countries as a way to sweeten the deal but what those countries really want is the joint-ownership of .amazon, with the US tech giant forced to get their approval before it can make any changes to the registry.

Having been at the end of eight years of delays, you could forgive Amazon for not wanting to partner up. ®

Similar topics

Other stories you might like

  • Prisons transcribe private phone calls with inmates using speech-to-text AI

    Plus: A drug designed by machine learning algorithms to treat liver disease reaches human clinical trials and more

    In brief Prisons around the US are installing AI speech-to-text models to automatically transcribe conversations with inmates during their phone calls.

    A series of contracts and emails from eight different states revealed how Verus, an AI application developed by LEO Technologies and based on a speech-to-text system offered by Amazon, was used to eavesdrop on prisoners’ phone calls.

    In a sales pitch, LEO’s CEO James Sexton told officials working for a jail in Cook County, Illinois, that one of its customers in Calhoun County, Alabama, uses the software to protect prisons from getting sued, according to an investigation by the Thomson Reuters Foundation.

    Continue reading
  • Battlefield 2042: Please don't be the death knell of the franchise, please don't be the death knell of the franchise

    Another terrible launch, but DICE is already working on improvements

    The RPG Greetings, traveller, and welcome back to The Register Plays Games, our monthly gaming column. Since the last edition on New World, we hit level cap and the "endgame". Around this time, item duping exploits became rife and every attempt Amazon Games made to fix it just broke something else. The post-level 60 "watermark" system for gear drops is also infuriating and tedious, but not something we were able to address in the column. So bear these things in mind if you were ever tempted. On that note, it's time to look at another newly released shit show – Battlefield 2042.

    I wanted to love Battlefield 2042, I really did. After the bum note of the first-person shooter (FPS) franchise's return to Second World War theatres with Battlefield V (2018), I stupidly assumed the next entry from EA-owned Swedish developer DICE would be a return to form. I was wrong.

    The multiplayer military FPS market is dominated by two forces: Activision's Call of Duty (COD) series and EA's Battlefield. Fans of each franchise are loyal to the point of zealotry with little crossover between player bases. Here's where I stand: COD jumped the shark with Modern Warfare 2 in 2009. It's flip-flopped from WW2 to present-day combat and back again, tried sci-fi, and even the Battle Royale trend with the free-to-play Call of Duty: Warzone (2020), which has been thoroughly ruined by hackers and developer inaction.

    Continue reading
  • American diplomats' iPhones reportedly compromised by NSO Group intrusion software

    Reuters claims nine State Department employees outside the US had their devices hacked

    The Apple iPhones of at least nine US State Department officials were compromised by an unidentified entity using NSO Group's Pegasus spyware, according to a report published Friday by Reuters.

    NSO Group in an email to The Register said it has blocked an unnamed customers' access to its system upon receiving an inquiry about the incident but has yet to confirm whether its software was involved.

    "Once the inquiry was received, and before any investigation under our compliance policy, we have decided to immediately terminate relevant customers’ access to the system, due to the severity of the allegations," an NSO spokesperson told The Register in an email. "To this point, we haven’t received any information nor the phone numbers, nor any indication that NSO’s tools were used in this case."

    Continue reading

Biting the hand that feeds IT © 1998–2021