Home / Blogs

Amazon’s Letter to ICANN Board: It’s Time to Approve Our Applications for .AMAZON TLDs

Protect your privacy:  Get NordVPN  [ Deal: 73% off 2-year plans + 3 extra months ]
10 facts about NordVPN that aren't commonly known
  • Meshnet Feature for Personal Encrypted Networks: NordVPN offers a unique feature called Meshnet, which allows users to connect their devices directly and securely over the internet. This means you can create your own private, encrypted network for activities like gaming, file sharing, or remote access to your home devices from anywhere in the world.
  • RAM-Only Servers for Enhanced Security: Unlike many VPN providers, NordVPN uses RAM-only (diskless) servers. Since these servers run entirely on volatile memory, all data is wiped with every reboot. This ensures that no user data is stored long-term, significantly reducing the risk of data breaches and enhancing overall security.
  • Servers in a Former Military Bunker: Some of NordVPN's servers are housed in a former military bunker located deep underground. This unique location provides an extra layer of physical security against natural disasters and unauthorized access, ensuring that the servers are protected in all circumstances.
  • NordLynx Protocol with Double NAT Technology: NordVPN developed its own VPN protocol called NordLynx, built around the ultra-fast WireGuard protocol. What sets NordLynx apart is its implementation of a double Network Address Translation (NAT) system, which enhances user privacy without sacrificing speed. This innovative approach solves the potential privacy issues inherent in the standard WireGuard protocol.
  • Dark Web Monitor Feature: NordVPN includes a feature known as Dark Web Monitor. This tool actively scans dark web sites and forums for credentials associated with your email address. If it detects that your information has been compromised or appears in any data breaches, it promptly alerts you so you can take necessary actions to protect your accounts.

When ICANN launched the new gTLD program five years ago, Amazon eagerly joined the process, applying for .AMAZON and its Chinese and Japanese translations, among many others. Our mission was—and is—simple and singular: We want to innovate on behalf of our customers through the DNS.

ICANN evaluated our applications according to the community-developed Applicant Guidebook in 2012; they achieved perfect scores. Importantly, ICANN’s Geographic Names Panel determined that “AMAZON” is not a geographic name that is prohibited or one that requires governmental approval. We sincerely appreciate the care with which ICANN itself made these determinations, and are hopeful that a full approval of our applications is forthcoming.

In a letter we sent to the ICANN Board on September 7, 2017 (the full text of which may be found below), we laid out the reasons for why our applications should be swiftly approved now that an Independent Review Process (IRP) panel found in our favor. Our letter highlights the proactive engagement we attempted with the governments of the Amazonia region over a five year period to alleviate any concerns about using .AMAZON for our business purposes.

First, we have worked to ensure that the governments of Brazil and Peru understand we will not use the TLDs in a confusing manner. We proposed to support a future gTLD to represent the region using the geographic terms of the regions, including .AMAZONIA, .AMAZONICA or .AMAZONAS. We also offered to reserve for the relevant governments certain domain names that could cause confusion or touch on national sensitivities.

During the course of numerous formal and informal engagements, we repeatedly expressed our interest in finding an agreed-upon outcome. And while the governments have declined these offers, we stand by our binding commitment from our July 4, 2013 Public Interest Commitment (PIC) to the .AMAZON applications, which stated that we will limit registration of culturally sensitive terms—engaging in regular conversations with the relevant governments to identify these terms—and formalizing the fact that we will not object to any future applications of .AMAZONAS, .AMAZONIA and .AMAZONICA.

We continue to believe it is possible to use .AMAZON for our business purposes while respecting the people, culture, history, and ecology of the Amazonia region.

We appreciate the ICANN Board’s careful deliberation of our applications and the IRP decision. But as our letter states, approval of our .AMAZON applications by the ICANN Board is the only decision that is consistent with the bottom-up, multistakeholder rules that govern ICANN and the new gTLD program. We urge the ICANN Board to now approve our applications. An ICANN accountable to the global multistakeholder community must do no less.

The full text of our letter is below.

* * *

Dear Chairman Crocker and Members of the ICANN Board of Directors:

We write as the ICANN Board considers the July 10, 2017 Final Declaration of the Independent Review Process Panel (IRP) in Amazon EU S.à.r.l. v. ICANN regarding the .AMAZON Applications. Because the Panel concluded that the Board acted in a manner inconsistent with its Bylaws, we ask the Board to immediately approve our long-pending .AMAZON Applications. 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.

First, the Board should recognize that the IRP Panel carefully examined the legal and public policy reasons offered by the objecting governments and found each to be insufficient or inaccurate. The Board should respect the IRP Panel conclusions.

Second, for the last 5 years, Amazon has repeatedly offered to work with the concerned governments to find an amicable solution, offering to explore how we can best use .AMAZON for our business purposes while respecting the people, culture, history, and ecology of the Amazonia region. Although those governments consistently declined our offers, we remain willing to adhere to our July 4, 2013 Public Interest Commitment (PIC) to the .AMAZON Applications. This binding commitment, which provides a practical solution, underscores why acting towards approving these applications immediately is in the public interest.

Finally, the Board last acted in 2014—before the IANA transition and the resulting changes to ICANN’s Bylaws. The Board should take this opportunity to demonstrate to everyone—including those who objected to the IANA transition on the grounds that it would give too much control to governments—that ICANN is appropriately responsive to the accountability measures that the multistakeholder community required as part of the transition.

Almost one year ago, Chairman Crocker heralded the ICANN multistakeholder community’s dedication and commitment in developing a broadly supported, consensus proposal to enhance ICANN’s transparency and accountability—a proposal that preserved “the existing multistakeholder system while laying the foundation for a more accountable and equitable balance within the ICANN ecosystem.” With the .AMAZON Applications, the Board should publicly and clearly honor this commitment to transparency and accountability. In contrast, permitting the GAC to veto TLD applications that received perfect application evaluation scores (41/41) based upon reasons that are neither well-founded nor merit-based directly contravenes ICANN’s oft-stated and critically important commitment to serving the public interest, as determined by rules agreed to by the multi-stakeholder community.

The ICANN-authorized IRP, the ICANN-selected Community Objection dispute resolution provider, and the ICANN-selected legal expert have rejected every reason put forth for denying the .AMAZON Applications. The Board should not grant Brazil and Peru a fourth, and the GAC a third, opportunity to try to further delay the global public interest benefits associated with .AMAZON. It is now time for the Board to approve the .AMAZON Applications. (A full timeline of our applications is in the Appendix.)

We are aware that governmental pressure on the Board in connection with matters of Internet governance, although unrelated to the .AMAZON Applications, is of concern to ICANN. Such pressure does not change the truth—that for four years Brazil and Peru have been unable to provide legally and factually sound reasons for rejecting the .AMAZON Applications. If the Board yields to such pressure, it will undermine ICANN’s leadership in advancing the multistakeholder approach to Internet governance. In fact, rejection of the .AMAZON Applications after they received perfect application evaluation scores will undoubtedly be used by those stakeholders who were (and are) skeptical of ICANN’s ability to remain independent of governmental overreach to question and challenge ICANN’s ongoing legitimacy.

Board rejection of the .AMAZON Applications may also adversely impact any new gTLD subsequent procedure. Globally, hundreds (if not thousands) of brands have names similar to regions, land formations, mountains, towns, cities, and other geographic places, and the uncertainty of ICANN’s sui generis protection of geographic names will deter these potential .BRAND applicants. Other applicants will also have reason to doubt the certainty and predictability of the gTLD subsequent procedure. After all, if an application that receives a perfect score, clears all third-party objections, passes Geographic Names Panel review, and is the subject of a favorable IRP Panel decision can be rejected because of an arbitrary GAC veto, no gTLD applicant can be certain of its application’s prognosis.

The ICANN Board should now re-evaluate the .AMAZON Applications, mindful of the Panel’s recommendations, and approve the .AMAZON Applications. ICANN’s Bylaws and Core Values mandate such a decision. The Board should not request or consider any further GAC advice on the .AMAZON Applications. The GAC had ample time and opportunity to develop and reach consensus on “well-founded, merits-based public policy reasons for denying [our] applications.” It did not because it could not then, and it cannot now, as recognized by the IRP. The Board also does not need to wait for policy recommendations from the new Subsequent Procedures PDP WG Geographic Names Work Track; that work, while important, does not impact the .AMAZON Applications, which we properly submitted under the Applicant Guidebook.

We request the opportunity to present to the Board and answer questions about the .AMAZON Applications before the Board acts on them, as well as an opportunity to review and respond to any subsequent submission by the GAC, Brazil, Peru, or any other party in connection with the .AMAZON Applications. We filed these applications over 5 years ago. Since then, multiple independent and objective experts have repeatedly found that our .AMAZON Applications are consistent with ICANN rules and existing law. The IRP Panel heard arguments on the length of time the applications have been pending and recommended that the Board should act “promptly.” It is now time for the Board to act promptly and allow our .AMAZON Applications to proceed. That is the only decision that is consistent with the global public interest, the IRP Final Declaration, and the rule of law.

Sincerely,

Scott Hayden
Vice President, Amazon

Brian Huseman
Vice President, Amazon

By Brian Huseman, Vice President, Public Policy at Amazon

Filed Under

Comments

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

Related

Topics

Domain Names

Sponsored byVerisign

Threat Intelligence

Sponsored byWhoisXML API

IPv4 Markets

Sponsored byIPv4.Global

DNS

Sponsored byDNIB.com

Brand Protection

Sponsored byCSC

New TLDs

Sponsored byRadix

Cybersecurity

Sponsored byVerisign