Jump to content

Registrar Accreditation Agreement

From ICANNWiki
Revision as of 15:03, 28 September 2012 by Andrew (talk | contribs)

The Registrar Accreditation Agreement (RAA) is the contract that governs the relationship between ICANN and its accredited registrars.

History[edit | edit source]

The RAA was originally one of several agreements between ICANN, the United States Department of Commerce (DOC), and Network Solutions, with the intent of enhancing and solidifying the competition between .com, .net, and .org TLD registrars. These agreements were tentatively announced on September 28, 1999, and, after oral and written public comments, were revised and then adopted by ICANN on November 4, 1999. At the time, registrars were allowed to take up the new agreement in place of their old agreement.[1]

On May 21, 2009, ICANN approved revisions to the RAA, which were intended to clarify the responsibilities of the registrars and the rights of the registrants. These revisions came about in response to market development and the significant growth in the number of accredited registrars and domain name registrations, and through a comprehensive review of the RAA and the Accreditation process called for in March 2007 by then-ICANN CEO Paul Twomey. This new RAA applies to all the new registrars, registrars that voluntarily adopt the contract prior the renewal date, and to registrars that renew after the approval date.[2] But, following this revision, there were still those who thought the RAA did not do enough to address public concerns. Thus the RAA Drafting Team was formed, made up of members of the GNSO and the At-Large Community, to propose further revisions.

Law enforcement officials, particularly the Serious Organized Crime Agency (SOCA) in the United Kingdom and the United States Federal Bureau of Investigation (FBI), asked ICANN to implement procedures to curb incidence of abuse in the domain name system (DNS). The two agencies proposed some measures to be incorporated in the RAA such as stronger verification of registrants' name, address, phone number, e-mail address and method of payment for domain names.[3]

In October, 2011, at the ICANN 42 meeting in Dakar, Senegal, the ICANN Board approved the immediate negotiation between ICANN and Registrar Negotiation Team regarding the proposed amendments to the RAA. The amendment topics, which included law enforcement, registrant protection and internet stability, were recommended by the Governmental Advisory Committee (GAC)and the GNSO Working Group. The result of the amendment negotiations were to be considered by ICANN during its meeting in Costa Rica in March, 2012.[4]

On December 13th, ICANN announced an open comment period on the Preliminary GNSO Issue Report regarding the RAA amendments, to close one month later. Comments on the prelininary report were to be considered for the Final Issue Report, to be presented to the GNSO council following the closure of the comment period. This was done in anticipation of discussions at the ICANN 43 meeting in Costa Rica, at the request of the Board.[5]

Prior to the ICANN Meeting in Costa Rica, the RAA Negotiation Team submitted a summary of the negotiations on the RAA on March 1, 2012. The RAA Negotiation Team and ICANN indicated they had nearly reached agreement on a majority of the topics discussed during the 13 negotiation sessions, in both principles and language. You can find the Summary of RAA Negotiations here.

Development[edit | edit source]

In September, 2012, a working group related to the European Commission sent a letter to ICANN warning that its proposed additions to the RAA would infringe on European Privacy laws. The issues in question are the proposals to make registrars retain data about their customers for up to two years after registration, and by the idea that registrars should re-verify contact data every year. These proposals were discussed and supported by the GAC and the law enforcement voices within ICANN at ICANN 44 in Prague. This is potentially conflicting given that the GAC supported these measures and this pan-European body is coming down against it.[6]

Contents of RAA[edit | edit source]

General Obligations of ICANN:

ICANN, under the RAA, is obliged to carry out its functions in an open manner and is to promote intensive competition between registrars. It should also not apply standards, procedures, or policies to single out registrars for disparate treatment unless it has a reasonable cause.

General Obligations of the Registrars:

Registrars are obliged to comply with all related ICANN-adopted policies. The Registrars are also obliged not to restrain competition.[7]

Members of the RAA Drafting Team[edit | edit source]

Some of the members of the RAA Drafting Team include:

The complete RAA-DT membership list is available here

RAA Negotiation Topics[edit | edit source]

Topics discussed during negotiation sessions falls under four categories:[8]

  • Registrar Obligations/Duties
  • Privacy and Proxy Services/Resellers
  • Whois Data
  • Contract Administration

.Nxt Criticism and Investigation on RAA Negotiations[edit | edit source]

Kieren McCarthy of .nxt alleged that ICANN conducted secret negotiation with registrars and it failed to provide adequate openness and transparency regarding the RAA negotiations. For this reason, .nxt conducted its own investigation to find out what actually transpired during the negotiations. In his article, he reported that the .nx investigation uncovered:[9]

  • Disagreements between registrars
  • ICANN was willing to "throw registrars under the bus" just to keep governments happy and show that problems are resolved
  • ICANN's negotiating team was under pressure to deliver results
  • Registrars were forced by ICANN to make public statements regarding the changes in the RAA, even though they did not have clear implementation policies
  • Some registrars refused to acknowledge the changes and were advocating walking-away from the negotiations

References[edit | edit source]

External Links[edit | edit source]