Difference between revisions of "Registrar Accreditation Agreement"
| Line 6: | Line 6: | ||
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, as per the suggestion of 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.<ref>[http://www.icann.org/en/topics/raa/ Revised RAA]</ref> But, following this revision, there were still those who thought the RAA did not do enough to address public concerns. Thus the [[RAA-DT]] was formed, made up of members of the [[GNSO]] and the [[At-Large Community]], to propose further revisions. | 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, as per the suggestion of 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.<ref>[http://www.icann.org/en/topics/raa/ Revised RAA]</ref> But, following this revision, there were still those who thought the RAA did not do enough to address public concerns. Thus the [[RAA-DT]] was formed, made up of members of the [[GNSO]] and the [[At-Large Community]], to propose further revisions. | ||
| − | In October, 2011, at the [[ICANN 42]] meeting in Dakar, Senegal, the [[ICANN Board]] | + | In October, 2011, at the [[ICANN 42]] meeting in Dakar, Senegal, the [[ICANN Board]] approved the immediate negotiation between ICANN and gLTD registrars regarding the proposed amendments to the RAA. The amendment topics which include law enforcement, registrant protection and internet stability were recommended by the Governmental Advisory Committee ([[GAC]])and the[[GNSO]][[WG|Working Group]]. The result of the amendment negotiation will be considered by ICANN during its meeting in Costa Rica on March 2012.<ref>[http://www.icann.org/en/groups/board/documents/resolutions-28oct11-en.htm#7 Registrar Accreditation Agreement Amendments]</ref> |
| + | |||
| + | 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 will be considered for the Final Issue Report, to be presented to the [[GNSO]] council following the closure of the comment period. All this has been in anticipation of the topic to discussed at the [[ICANN 43]] meeting in Costa Rica, at the request of the Board.<ref>[http://www.icann.org/en/announcements/announcement-2-12dec11-en.htm Preliminary GNSO Issue Report on the Registrar Accreditation Agreement Amendments]</ref> | ||
==Contents of RAA== | ==Contents of RAA== | ||
Revision as of 00:49, 7 April 2012
The Registrar Accreditation Agreement (RAA) is, simply stated, the contract that governs the relationship between ICANN and its accredited registrars.
History
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, as per the suggestion of 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-DT was formed, made up of members of the GNSO and the At-Large Community, to propose further revisions.
In October, 2011, at the ICANN 42 meeting in Dakar, Senegal, the ICANN Board approved the immediate negotiation between ICANN and gLTD registrars regarding the proposed amendments to the RAA. The amendment topics which include law enforcement, registrant protection and internet stability were recommended by the Governmental Advisory Committee (GAC)and theGNSOWorking Group. The result of the amendment negotiation will be considered by ICANN during its meeting in Costa Rica on March 2012.[3]
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 will be considered for the Final Issue Report, to be presented to the GNSO council following the closure of the comment period. All this has been in anticipation of the topic to discussed at the ICANN 43 meeting in Costa Rica, at the request of the Board.[4]
Contents of RAA
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.[5]
References