Changes

Jump to navigation Jump to search
516 bytes removed ,  12 years ago
no edit summary
Line 1: Line 1: −
{{CompanyInfo|
+
{{TLD|
| logo           = Dotnamelogo.JPG
+
|logo   = Dotnamelogo.JPG
| type            =  
+
|status = Active
| industry        = Internet
+
|manager  = [[Verisign]]
| founded        = 2001
+
|country   =
| founders        =
+
|stringcontention =  
| ownership      =  
+
|registryprovider  = Verisign
| headquarters    = 21345 Ridgetop Circle <br>
+
|date = November, 2000
Dulles Virginia 20166
+
|type  = [[gTLD]]
| country         =  
+
|community  =
| businesses      =  
+
|keypeople =  
| products        =  
  −
| employees      =  
  −
| revenue        =
  −
| website        = [http://www.verisigninc.com/en_US/products-and-services/domain-name-services/registry-services/name-domain-names/index.xhtml www.verisigninc.com]
  −
| blog            =
  −
| facebook        =
  −
| linkedin        =
  −
| twitter        =  
  −
| keypeople       = [[D. James Bidzos]], Executive Chairman <br> [[Mark D. McLaughlin]], Pres. & CEO
  −
 
   
}}
 
}}
   −
'''.name''' is a [[gTLD|generic top level domain name]] in the [[Root Zone|root zone]] of the Internet's [[DNS|Domain Name System]] (DNS). It is designed to provide a name space for individuals who uses their names, nicknames, or screen names to promote their blogs, websites, profession or business using their personal and unique identity as a brand. [[Verisign]] is the [[registry]] operator of .name.<ref>
+
'''.name''' is a [[gTLD|generic top level domain name]] in the [[Root Zone|root zone]] of the Internet's [[DNS|Domain Name System]] (DNS). It is designed to provide a name space for individuals who uses their names, nicknames, or screen names to promote their blogs, websites, profession or business using their personal and unique identity as a brand. [[Verisign]] is the [[registry]] operator of .name.<ref>[http://www.verisigninc.com/en_US/products-and-services/domain-name-services/registry-services/name-domain-names/index.xhtml www.verisigninc.com]</ref>
[http://www.verisigninc.com/en_US/products-and-services/domain-name-services/registry-services/name-domain-names/index.xhtml www.verisigninc.com]</ref>
      
==Background==  
 
==Background==  
 
In 1985, Dr. [[Jon Postel]] and [[Joyce Reynolds]] issued [[RFC]] 920,<ref>[http://www.rfc-editor.org/rfc/rfc920.txt RFC 920]</ref> which described the deployment of the original [[TLD|top level domains]] (TLDs), which included [[.com]] (commercial), [[.gov]] (government), [[.edu]] (education), [[.mil.]] (military), [[.org]] (organization)  and the [[.arpa]] intended for the transition of the ARPA-internet. The two-letter (alpha-2) country codes were also delegated under the ISO-3166-1 list. <ref>[http://www.iso.org/iso/english_country_names_and_code_elements ISO 3166-1-alpha-2 code elements]</ref> In 1988, [[.net]] and [[.int]] were added to the root zone of the DNS.
 
In 1985, Dr. [[Jon Postel]] and [[Joyce Reynolds]] issued [[RFC]] 920,<ref>[http://www.rfc-editor.org/rfc/rfc920.txt RFC 920]</ref> which described the deployment of the original [[TLD|top level domains]] (TLDs), which included [[.com]] (commercial), [[.gov]] (government), [[.edu]] (education), [[.mil.]] (military), [[.org]] (organization)  and the [[.arpa]] intended for the transition of the ARPA-internet. The two-letter (alpha-2) country codes were also delegated under the ISO-3166-1 list. <ref>[http://www.iso.org/iso/english_country_names_and_code_elements ISO 3166-1-alpha-2 code elements]</ref> In 1988, [[.net]] and [[.int]] were added to the root zone of the DNS.
   −
The over-all structure and delegation of the DNS was described by Dr. Postel in 1994 in RFC 1591<ref>
+
The over-all structure and delegation of the DNS was described by Dr. Postel in 1994 in RFC 1591<ref>[http://www.rfc-editor.org/rfc/rfc1591.txt RFC 1591]</ref> wherein the seven original TLDs ( .com, .edu. .mil, .gov, .org, .net and .int) are called [[gTLD|generic top level domain names]] (gTLDs) and the alpha-2 country codes. The .mil was restricted for the use of United States military and the .org was also originally restricted to be used by U.S. government agencies. The management and coordination of the entire DNS of the internet was handled by the [[IANA|Internet Assigned Numbers Authority]]. In addition, under RFC 1591 the creation of new gTLDs seemed unlikely to happen.
[http://www.rfc-editor.org/rfc/rfc1591.txt RFC 1591]</ref> wherein the seven original TLDs ( .com, .edu. .mil, .gov, .org, .net and .int) are called [[gTLD|generic top level domain names]] (gTLDs) and the alpha-2 country codes. The .mil was restricted for the use of United States military and the .org was also originally restricted to be used by U.S. government agencies. The management and coordination of the entire DNS of the internet was handled by the [[IANA|Internet Assigned Numbers Authority]]. In addition, under RFC 1591 the creation of new gTLDs seemed unlikely to happen.
      
The use of the Internet increased rapidly and the Internet community expressed their concern of the limited choice in the registration of gTLDs. In 1998, President [[Bill Clinton]] instructed the [[DOC|Department of Commerce]] (DoC) to look into their concerns. In response to the President's directive, the DoC issued the [[Green Paper]], which tackled the different issues related to the DNS, aspects that needs improvement and enumerated the reasons behind the widespread dissatisfaction of the internet community particularly the lack of competition in domain name registration. The Green Paper suggested improvement in the technical management of the DNS as well as introduction of new TLDs.<ref>[http://www.ntia.doc.gov/ntiahome/domainname/022098fedreg.htm Green Paper]</ref>
 
The use of the Internet increased rapidly and the Internet community expressed their concern of the limited choice in the registration of gTLDs. In 1998, President [[Bill Clinton]] instructed the [[DOC|Department of Commerce]] (DoC) to look into their concerns. In response to the President's directive, the DoC issued the [[Green Paper]], which tackled the different issues related to the DNS, aspects that needs improvement and enumerated the reasons behind the widespread dissatisfaction of the internet community particularly the lack of competition in domain name registration. The Green Paper suggested improvement in the technical management of the DNS as well as introduction of new TLDs.<ref>[http://www.ntia.doc.gov/ntiahome/domainname/022098fedreg.htm Green Paper]</ref>
Line 37: Line 25:  
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 selected as 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 selected as one of the seven new TLDs selected by the ICANN Board along with [[.aero]], [[.biz]], [[.coop]], [[.info]], [[.museum]], and [[.pro]].
   −
==Registry Operator==
   
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 including the personalized e-mail address.<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 including the personalized e-mail address.<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>
   Line 47: Line 34:  
==References==
 
==References==
 
{{reflist}}
 
{{reflist}}
  −
  −
  −
  −
  −
  −
  −
  −
  −
  −
  −
       
14,326

edits

Navigation menu