Changes

Jump to navigation Jump to search
840 bytes added ,  12 years ago
Line 138: Line 138:     
== Relationship with ICANN ==
 
== Relationship with ICANN ==
 +
===Sponsorship===
 +
Verisign is consistently one of the largest sponsors of [[ICANN]]'s meetings; they sponsored at the Platinum level or above for all 2011 meetings.<ref>[http://dakar42.icann.org/ Dakar42.ICANN.org]</ref><ref>[http://singapore41.icann.org/ Singapore41.ICANN.org]</ref><ref>[http://svsf40.icann.org/ SVSF40.ICANN.org]</ref> Some commentators attributed the ability of ICANN to secure former U.S. President, [[Bill Clinton]], to speak at [[ICANN 40]] to the especially high level at which Verisign sponsored that meeting.<ref>[http://domainincite.com/verisign-drops-150000-on-icann-singapore/ Verisign Drops 150,000 on ICANN Singapore, DomainIncite.com]</ref><ref>[http://www.tldmagazine.com/bill-clinton-to-address-icann-san-francisco-meeting.html Bill Clinto to Address ICANN San Francisco Meeting, TLDmagazing.com]</ref>
 +
 
===Site Finder Service===
 
===Site Finder Service===
 
Verisign launched Site Finder September, 2003, which caused a user to be redirected to its Site Finder search engine after the user attempted to access an unregistered address. [[ICANN]] published a report against this policy stating "Verisign violated architectural principles, codes of conduct and good practice," and [[ICANN]] declared Site Finder in violation of Verisign's contracts for running the master address lists for [[.com]]<ref>"[http://www.out-law.com/page-4716 Out-law.com]</ref> [[ICANN]] then asked Verisign to suspend its Site Finder service.<ref>[http://www.out-law.com/page-3921 Out-law.com]</ref> In October, a hearing took place place in Washington, D.C. to review technical issues with the U.S. Department of Commerce, which gives permission to Verisign to operate the [[DNS]] for [[.com]] and [[.net]]; VeriSign  subsequently shut down the service.
 
Verisign launched Site Finder September, 2003, which caused a user to be redirected to its Site Finder search engine after the user attempted to access an unregistered address. [[ICANN]] published a report against this policy stating "Verisign violated architectural principles, codes of conduct and good practice," and [[ICANN]] declared Site Finder in violation of Verisign's contracts for running the master address lists for [[.com]]<ref>"[http://www.out-law.com/page-4716 Out-law.com]</ref> [[ICANN]] then asked Verisign to suspend its Site Finder service.<ref>[http://www.out-law.com/page-3921 Out-law.com]</ref> In October, a hearing took place place in Washington, D.C. to review technical issues with the U.S. Department of Commerce, which gives permission to Verisign to operate the [[DNS]] for [[.com]] and [[.net]]; VeriSign  subsequently shut down the service.
Line 144: Line 147:  
===.net Renewals===
 
===.net Renewals===
 
Also, in other domain name negotiations with [[ICANN]], Verisign traded the [[.org]] [[TLD]] in return for continued rights over [[.com]]. In mid 2005, when Verisign's contract for operation with [[.net]] expired, Verisign and 5 other companies bid for it. Verisign was supported by renowned IT companies like Microsoft, [[IBM]], [[Sun Microsystems]], and [[MCI]]. On June 8, 2005, [[ICANN]] announced that Verisign had been approved to operate [[.net]] until 2011.<ref>[http://www.icann.org/en/tlds/dotnet-reassignment/dotnet-general.htm]</ref> These agreements have presumptive right of renewal clauses that encourage the registry operators to invest in critical Internet infrastructure. They were subsequently approved to operate the .net registry through 2017.<ref>[http://www.internetnews.com/infra/icann-renews-verisigns-.net-contract.html ICANN Renews Verisign .net Contract, InternetNews.com]</ref>
 
Also, in other domain name negotiations with [[ICANN]], Verisign traded the [[.org]] [[TLD]] in return for continued rights over [[.com]]. In mid 2005, when Verisign's contract for operation with [[.net]] expired, Verisign and 5 other companies bid for it. Verisign was supported by renowned IT companies like Microsoft, [[IBM]], [[Sun Microsystems]], and [[MCI]]. On June 8, 2005, [[ICANN]] announced that Verisign had been approved to operate [[.net]] until 2011.<ref>[http://www.icann.org/en/tlds/dotnet-reassignment/dotnet-general.htm]</ref> These agreements have presumptive right of renewal clauses that encourage the registry operators to invest in critical Internet infrastructure. They were subsequently approved to operate the .net registry through 2017.<ref>[http://www.internetnews.com/infra/icann-renews-verisigns-.net-contract.html ICANN Renews Verisign .net Contract, InternetNews.com]</ref>
 +
 
==New gTLDs==
 
==New gTLDs==
 
In December, 2011, weeks before the opening of [[ICANN]]'s new [[gTLD]] program, the Chinese national [[registry]], [[CNNIC]], announced that it was applying for the IDN equivalents of .company, and .network.<ref>[http://tech.sina.com.cn/i/2011-12-20/10326538420.shtml Tech.Sina.com]</ref> This move was seen as potentially problematic given Verisign's own plans to seek the IDN equivalents of their [[.com]] and [[.net]] TLDs; Verisign has previously said that they will apply for all transliterated versions of .com and .net.<ref>[http://www.managingip.com/Article/2761204/VeriSign-wants-com-and-net-IDNs.html Verisign Wants Com and Net, ManagingIP.com]</ref> Verisign's [[Pat Kane]] later added, in January, 2012, that the company was planning on applying for "about 12" new gTLDs, and noted that most of these were going to be transliterations of [[.com]].<ref>[http://seekingalpha.com/article/322517-verisign-management-discusses-q4-2011-results-earnings-call-transcript?part=qanda 2011 Results Earnings Call Transcript, SeekingAlpha.com]</ref> Confirmed languages that will be applied for include Japanese, Hangul, Chinese, Cyrillic, Arabic, and Hebrew.<ref>[http://domainnamewire.com/2012/01/26/verisign-plans-to-apply-for-about-12-new-top-level-domain-names/ Verisign Plans to Apply for About 12 New Top Level Domain Names, DomainNameWire.com]</ref> At that time it was also noted that Verisign had already been chosen to provide [[registry]] services for several [[Brand gTLD|.brand]] initiatives.<ref>[http://domainincite.com/verisign-to-apply-for-a-dozen-new-gtlds/ Verisign to Apply for a Dozen New gTLDs, DomainIncite.com]</ref>
 
In December, 2011, weeks before the opening of [[ICANN]]'s new [[gTLD]] program, the Chinese national [[registry]], [[CNNIC]], announced that it was applying for the IDN equivalents of .company, and .network.<ref>[http://tech.sina.com.cn/i/2011-12-20/10326538420.shtml Tech.Sina.com]</ref> This move was seen as potentially problematic given Verisign's own plans to seek the IDN equivalents of their [[.com]] and [[.net]] TLDs; Verisign has previously said that they will apply for all transliterated versions of .com and .net.<ref>[http://www.managingip.com/Article/2761204/VeriSign-wants-com-and-net-IDNs.html Verisign Wants Com and Net, ManagingIP.com]</ref> Verisign's [[Pat Kane]] later added, in January, 2012, that the company was planning on applying for "about 12" new gTLDs, and noted that most of these were going to be transliterations of [[.com]].<ref>[http://seekingalpha.com/article/322517-verisign-management-discusses-q4-2011-results-earnings-call-transcript?part=qanda 2011 Results Earnings Call Transcript, SeekingAlpha.com]</ref> Confirmed languages that will be applied for include Japanese, Hangul, Chinese, Cyrillic, Arabic, and Hebrew.<ref>[http://domainnamewire.com/2012/01/26/verisign-plans-to-apply-for-about-12-new-top-level-domain-names/ Verisign Plans to Apply for About 12 New Top Level Domain Names, DomainNameWire.com]</ref> At that time it was also noted that Verisign had already been chosen to provide [[registry]] services for several [[Brand gTLD|.brand]] initiatives.<ref>[http://domainincite.com/verisign-to-apply-for-a-dozen-new-gtlds/ Verisign to Apply for a Dozen New gTLDs, DomainIncite.com]</ref>

Navigation menu