.name: Difference between revisions
No edit summary |
|||
(One intermediate revision by one other user not shown) | |||
Line 17: | Line 17: | ||
During the early years of ICANN's establishment, one of the main activities of the organization was the development of new TLDs. The [[DNSO|Domain Name Supporting Organization]] (DNSO) was delegated to conduct a development process for the introduction of new TLDs and protection of popular trademarks. On July 16, 2000, the [[ICANN Board]] adopted a policy for the introduction of new TLDs.<ref>[http://www.icann.org/en/minutes/prelim-report-16jul00.htm#00.46 July 16, 2000 ICANN Yokohama Meeting]</ref> By August, ICANN issued the new TLD application process wherein proposals to sponsor or operate new TLDs were received from September 5 to October 2, 2000.<ref>[http://www.icann.org/en/tlds/application-process-03aug00.htm New TLD Application Process Overview]</ref> Eventually, on November 16, 2000, '''.name''' was one of the seven new TLDs selected by the ICANN Board along with [[.aero]], [[.biz]], [[.coop]], [[.info]], [[.museum]], and [[.pro]]. | During the early years of ICANN's establishment, one of the main activities of the organization was the development of new TLDs. The [[DNSO|Domain Name Supporting Organization]] (DNSO) was delegated to conduct a development process for the introduction of new TLDs and protection of popular trademarks. On July 16, 2000, the [[ICANN Board]] adopted a policy for the introduction of new TLDs.<ref>[http://www.icann.org/en/minutes/prelim-report-16jul00.htm#00.46 July 16, 2000 ICANN Yokohama Meeting]</ref> By August, ICANN issued the new TLD application process wherein proposals to sponsor or operate new TLDs were received from September 5 to October 2, 2000.<ref>[http://www.icann.org/en/tlds/application-process-03aug00.htm New TLD Application Process Overview]</ref> Eventually, on November 16, 2000, '''.name''' was one of the seven new TLDs selected by the ICANN Board along with [[.aero]], [[.biz]], [[.coop]], [[.info]], [[.museum]], and [[.pro]]. | ||
The first operator of the .name gTLD was delegated to the [[GNR|Global Name Registry]] (GNR), a British company, in November, 2000.The company launched .name in 2002, and offered second level (''jane.name'') and third level (''jane.smith.name'') registration for domain names, which facilitated personalized e-mail addresses.<ref>[http://www.crunchbase.com/company/globalnameregistry www.crunchbase.com]</ref> The company was acquired by [[Verisign]] in 2008, which is the current registry of the .name gTLD.<ref>[http://www.icann.org/en/tlds/agreements/name/assignment-assumption-agreement-28feb09-en.pdf Assignment and Assumption of .name Registry Agreement]</ref> | The first operator of the .name gTLD was delegated to the [[GNR|Global Name Registry]] (GNR), a British company, in November, 2000.The company launched .name in 2002, and offered second level (''jane.name'') and third level (''jane.smith.name'') registration for domain names, which facilitated personalized e-mail addresses.<ref>[http://www.crunchbase.com/company/globalnameregistry www.crunchbase.com]</ref> The company was acquired by [[Verisign]] in 2008, which is the current registry of the .name gTLD.<ref>[http://www.icann.org/en/tlds/agreements/name/assignment-assumption-agreement-28feb09-en.pdf Assignment and Assumption of .name Registry Agreement]</ref> Prior it its acquisition of GNR, Verisign was already providing certain registry functions to the company. It acquired GNR for $11.7 million.<ref>[http://www.wikinvest.com/stock/VeriSign_(VRSN)/Acquisition Verisign Acquisition, Wikinvest.com]</ref> | ||
==Global Name Registry Criticism== | ==Global Name Registry Criticism== | ||
Line 30: | Line 30: | ||
[[Category:TLD]] | [[Category:TLD]] | ||
[[Category:TLDs with Registry Agreements|name]] |
Revision as of 21:18, 10 October 2013
Status: | Active |
country: | International |
Manager: | Verisign |
Registry Provider: | Verisign |
Date Implemented: | November, 2000 |
Type: | gTLD |
More information: |
.name is a generic top level domain name in the root zone of the Internet's Domain Name System (DNS). It is designed to provide a name space for individuals who want to use their names, nicknames, or screen names to denote their blogs, websites, profession or business. Verisign is the registry operator of .name.[1]
Background[edit | edit source]
During the early years of ICANN's establishment, one of the main activities of the organization was the development of new TLDs. The Domain Name Supporting Organization (DNSO) was delegated to conduct a development process for the introduction of new TLDs and protection of popular trademarks. On July 16, 2000, the ICANN Board adopted a policy for the introduction of new TLDs.[2] By August, ICANN issued the new TLD application process wherein proposals to sponsor or operate new TLDs were received from September 5 to October 2, 2000.[3] Eventually, on November 16, 2000, .name was one of the seven new TLDs selected by the ICANN Board along with .aero, .biz, .coop, .info, .museum, and .pro.
The first operator of the .name gTLD was delegated to the Global Name Registry (GNR), a British company, in November, 2000.The company launched .name in 2002, and offered second level (jane.name) and third level (jane.smith.name) registration for domain names, which facilitated personalized e-mail addresses.[4] The company was acquired by Verisign in 2008, which is the current registry of the .name gTLD.[5] Prior it its acquisition of GNR, Verisign was already providing certain registry functions to the company. It acquired GNR for $11.7 million.[6]
Global Name Registry Criticism[edit | edit source]
In 2007, the Global Name Registry was criticized by Internet security researchers because access to its Whois]] database relied on payment. According to Internet security researchers, the practice limited their ability to police the Internet, and GNR created a haven for hackers who conduct Internet scams.[7]
On the other hand, ICANN domain registrar liaison Karen Lentz explained that ICANN's contract with GNR allowed the Whois database be kept behind a paid firewall in compliance with the British government's privacy law. Lentz further explained, "There is certain data, that is minimal data, that is free, and there is tiered access to more detailed information. One level involves paying a fee to get you access to more data for a limited period of time".[8]