Registrar: Difference between revisions
Simoncousins (talk | contribs) No edit summary |
Added translate and languages tag and subtracted Chinese for separate article. |
||
| Line 1: | Line 1: | ||
<translate> <languages /> | |||
{{Glossary| | {{Glossary| | ||
|note = This article is neutral, but is [[Sponsorship|sponsored]] by<br> [[Google]], an applicant for [[New gTLD Program|new gTLDs]], among many other things. | |note = This article is neutral, but is [[Sponsorship|sponsored]] by<br> [[Google]], an applicant for [[New gTLD Program|new gTLDs]], among many other things. | ||
| Line 64: | Line 65: | ||
On 29 May 2014, ICANN announced that a security breach had occurred and RADAR would be taken offline until a review was conducted. Registrar's passwords, usernames, and email addresses may have been accessed. ICANN stated that they had no evidence unauthorized logins had occurred but was resetting all Registrar passwords as precautionary measure.<ref>[https://www.icann.org/news/announcement-2-2014-05-28-en RADAR announcement 28 May 2014] Retrieved 29 May 2014</ref><ref>[http://domainincite.com/16738-icann-registrar-database-hacked ICANN Registrar Database Hacked, DomainIncite] Retrieved 29 May 2014</ref> ICANN stated the database will be offline for at least two weeks while the organization conducts a security audit of RADAR and other ICANN processes.<ref>[http://domainincite.com/16756-radar-to-be-down-at-least-two-weeks-after-hack RADAR to be down at least two weeks, DomainIncite] Retrieved 30 May 2014</ref> | On 29 May 2014, ICANN announced that a security breach had occurred and RADAR would be taken offline until a review was conducted. Registrar's passwords, usernames, and email addresses may have been accessed. ICANN stated that they had no evidence unauthorized logins had occurred but was resetting all Registrar passwords as precautionary measure.<ref>[https://www.icann.org/news/announcement-2-2014-05-28-en RADAR announcement 28 May 2014] Retrieved 29 May 2014</ref><ref>[http://domainincite.com/16738-icann-registrar-database-hacked ICANN Registrar Database Hacked, DomainIncite] Retrieved 29 May 2014</ref> ICANN stated the database will be offline for at least two weeks while the organization conducts a security audit of RADAR and other ICANN processes.<ref>[http://domainincite.com/16756-radar-to-be-down-at-least-two-weeks-after-hack RADAR to be down at least two weeks, DomainIncite] Retrieved 30 May 2014</ref> | ||
==References== | ==References== | ||
| Line 142: | Line 76: | ||
[[Category: Glossary]] | [[Category: Glossary]] | ||
[[Category:Articles with Chinese]] | [[Category:Articles with Chinese]] | ||
</translate> | |||
Revision as of 20:33, 28 August 2015
Google, an applicant for new gTLDs, among many other things. | |
 | |
| ICANNWiki Gold Sponsor |
A registrar has direct relationships with domain name registries and is authorized to sell domain names. In order to become a registrar, one has to be accredited through ICANN,[1] which requires that they meet certain business and technical requirements.
See our list of registrars.
Related Terms[edit | edit source]
- Accredited Registrar: A Registrar that has been certified as meeting certain minimum criteria to act as a Registrar for a specific TLD. This term is almost solely used when referring to Registrars that have been certified by ICANN. ccTLD Registries also accredit registrars through a separate process, however though they may use differing terms, the concepts are largely the same.
- Sponsoring Registrar: The Registrar responsible for the submission of the domain name to the Registry.
- Registrar Operator: A term used to denote the entity providing the technical services to a Registrar in support of their registration services. Also referred to as a "Registrar Outsourcer" or "Registrar Provider".
Background[edit | edit source]
NSI Cooperative Agreement & the SRS[edit | edit source]
From 1993 to 1998, Network Solutions (NSI) was the only Registrar and Registry Operator for the .com, .net and .org top level domain names (TLDs), based on a Cooperative Agreement between NSI and the National Science Foundation (NSF).[2] The Department of Commerce (DOC) extended and amended the Cooperative Agreement with NSI when the contract expired in 1998. Under the new Cooperative Agreement, NSI would continue to serve as a Registry Operator, but would implement a Shared Registry System (SRS) by June 1, 1999, meaning that multiple registrars could be accredited by a new non-profit organization that was to be created to take over the technical management of the DNS. Five new registrars were to be chosen by the new corporation to test the SRS.[3] The Agreement was modified twice in order to adjust the date of the deployment of the SRS from June 1 to June 25, 1999,[4] to include a registration fee for new domain names ($9 for one year and $18 for two years), and to include the Registrar License Agreement.[5]
ICANN's Registrar Accreditation Policy[edit | edit source]
On November 1998, the DOC officially recognized ICANN as the new private, non-profit organization responsible in administering the technical management of DNS. Some of its responsibilities would include supervision of the deployment and transition to SRS, development and implementation procedures for registrar accreditation that would ensure a competitive registration system, and to maintain the stability and security of the internet.[6]
On March 4, 1999, the ICANN Board adopted the Statement of Registrar Accreditation Policy for the .com, .net and .org TLDs. Under the policy, registrars seeking to participate in the SRS Testbed Program would be required to pay $2,500, while all other registrar applicants would pay $1,000. Applicants that were not selected for the test bed would be considered for regular accreditation.[7]
Participants for the SRS Testbed Program[edit | edit source]
ICANN accepted applicantions for the SRS Testbed Program from March 11 to April 8, 1999. On April 21, 1999, ICANN announced that the following five registrars had been selected to participate in the testbed:[8]
- America Online (AOL)
- CORE (Internet Council of Registrars)
- France Telecom/Oléane
- Melbourne IT
- Register.com
In addition, ICANN also announced the names of 29 additional companies that would receive accreditation after the completion of the SRS Testbed Program. The testbed ended on November 30, 1999. The List of Businesses to be Accredited as Post-Testbed Registrars is available here.
ICANN has continued to accept applications for registrar accreditation since then. Here is a complete list of existing ICANN Accredited Registrars.
The Registrar Accreditation Agreement (RAA)[edit | edit source]
ICANN implemented a new version of Registrar Accreditation Agreement (RAA) on March 17, 2001 effective until March 21, 2009. A new revision was again introduced on March 21, 2009 with 17 amendments. Some of the revisions include:[9]
- improved enforcement tools to ensure full compliance with the ICANN contract and policies
- expansion of requirements for reseller agreements
- additional requirements for audit and data escrow
- additional requirements to ensure precise contact information
- new notice requirements
- provisions for termination
Read the 2013 RAA.
Registry and Registrar[edit | edit source]
Vertical Separation[edit | edit source]
When the U.S. Department of Commerce amended Network Solutions' (NSI) cooperative agreement and implemented the Shared Registry System (SRS), the DOC also put a condition on the renewal of NSI's contract: the company would be able to automatically renew its contract for another four years as long as it separated its registry and registrar businesses. This was done in order to promote more competition in the domain space.[10]
In 2000, Verisign purchased Network Solutions for $16 billion. Verisign decided to sell the registrar business to Pivotal Private for $100 million in order to concentrate on its new registry business.[11] This move enabled Verisign to re-negotiate its registry agreement with ICANN. On April 16, 2001, a Revised Registry Agreement for .com, .net and .org was adopted. Number 23 (C) Fair Treatment of ICANN-Accredited Registrars on the revised agreement stipulated, "Registry Operator shall not act as a registrar with respect to the Registry TLD. This shall not preclude Registry Operator from registering names within the domain of the Registry TLD in compliance with Section 24. This also shall not preclude an affiliate (including wholly-owned subsidiaries) of Registry Operator from acting as a registrar with respect to the Registry TLD, provided that Registry Operator complies with the provisions of Subsection 23(E)." Sub-section E also stated that Registry Operators must ensure that their assets and revenues would not be utilized to advance the interests of their affiliate registrars against other accredited competitor registrars.[12]
The separation of ownership, or vertical separation, was also implemented to all un-sponsored TLD registry operators to maintain registrar competition.[13]
ICANN's Policy Change on Vertical Separation[edit | edit source]
On November 5, 2010, the ICANN Board passed a resolution allowing the removal of registry-registrar cross-ownership restriction for existing and new gTLDs.[14] Further explanation on this issue, vertical integration, is available here.
RADAR[edit | edit source]
ICANN maintains Registrar Contact Information Database, called RADAR, that Registrars can log into to perform Domain Name transfers and other functions.
On 29 May 2014, ICANN announced that a security breach had occurred and RADAR would be taken offline until a review was conducted. Registrar's passwords, usernames, and email addresses may have been accessed. ICANN stated that they had no evidence unauthorized logins had occurred but was resetting all Registrar passwords as precautionary measure.[15][16] ICANN stated the database will be offline for at least two weeks while the organization conducts a security audit of RADAR and other ICANN processes.[17]
References[edit | edit source]
- ↑ Registrar Definition
- ↑ A Brief History of NSF and the Internet
- ↑ Special Award Conditions NCR-9218742 Amendment No. 11
- ↑ Amendment Number 12
- ↑ Amendment Number 13
- ↑ Registrar Accreditation: History of the Shared Registry System
- ↑ Statement of Registrar Accreditation Policy
- ↑ ICANN Names Competitive Domain-Name Registrars
- ↑ Registrar Accreditation: History of the Shared Registry System
- ↑ ICANN-NSI Registry Agreement
- ↑ VeriSign selling domain registrar business
- ↑ Revised VeriSign .com Registry Agreement, 16 April 2001
- ↑ Proposed Unsponsored TLD Agreement, 26 February 2001
- ↑ Special Meeting of the ICANN Board of Directors
- ↑ RADAR announcement 28 May 2014 Retrieved 29 May 2014
- ↑ ICANN Registrar Database Hacked, DomainIncite Retrieved 29 May 2014
- ↑ RADAR to be down at least two weeks, DomainIncite Retrieved 30 May 2014