Pat Kane: Difference between revisions

Line 15:

==VeriSign==

He is responsible for the operational management, and relevant policy development for all [[TLD]]s operated by VeriSign under contract with the ICANN; which include [[.com]], [[.net]], [[.name]], [[.jobs]], and [[.edu]]. He has worked extensively around the development and deployment of [[IDN]]s, and is a member of [[ICANN]]'s Presidential Advisory Board for IDNs.<ref>[http://www.verisigninc.com/en_AU/news-events/press-room/executive-bios/index.xhtml#kane VerisignInc.com]</ref>

He is responsible for the operational management, and relevant policy development for all [[TLD]]s operated by VeriSign under contract with the ICANN; which include [[.com]], [[.net]], [[.name]], [[.jobs]], and [[.edu]].

He has worked extensively around the development and deployment of [[IDN]]s, and is a member of [[ICANN]]'s Presidential Advisory Board for IDNs.<ref>[http://www.verisigninc.com/en_AU/news-events/press-room/executive-bios/index.xhtml#kane VerisignInc.com]</ref> As the [[IDN]] implementation process has opened up, VeriSign, via Pat Kane, has confirmed its interest in pursuing its "[[.com]]" and "[[.net]]" interests in their [[IDN]] format. That is, Mr. Kane wrote on February 17th, 2011, that VeriSign has every intention to pursue the equivalent transliterations of .com and .net in non ASCII text.<ref>[http://domainincite.com/verisigns-upcoming-battle-for-the-chinese-com/comment-page-1/#comment-4263 DomainIncite Public Comments]</ref>

Recently, Pat Kane has been working on the implementation of [[DNSSEC]]; VeriSign has been tackling the security measures gradually as it is weary of disrupting any functioning for the large [[.com]] and [[.net]] domains for which it is responsible.<ref>[http://www.zdnet.co.uk/news/security-management/2009/11/16/verisign-major-internet-security-update-by-2011-39877966/ Zdnet.co.uk]</ref>

@@ Line 15: / Line 15: @@
 ==VeriSign==
-He is responsible for the operational management, and relevant policy development for all [[TLD]]s operated by VeriSign under contract with the ICANN; which include [[.com]], [[.net]], [[.name]], [[.jobs]], and [[.edu]]. He has  worked extensively around the development and deployment of [[IDN]]s, and is a member of [[ICANN]]'s Presidential Advisory Board for IDNs.<ref>[http://www.verisigninc.com/en_AU/news-events/press-room/executive-bios/index.xhtml#kane VerisignInc.com]</ref>
+He is responsible for the operational management, and relevant policy development for all [[TLD]]s operated by VeriSign under contract with the ICANN; which include [[.com]], [[.net]], [[.name]], [[.jobs]], and [[.edu]].
+He has  worked extensively around the development and deployment of [[IDN]]s, and is a member of [[ICANN]]'s Presidential Advisory Board for IDNs.<ref>[http://www.verisigninc.com/en_AU/news-events/press-room/executive-bios/index.xhtml#kane VerisignInc.com]</ref>  As the [[IDN]] implementation process has opened up, VeriSign, via Pat Kane, has confirmed its interest in pursuing its "[[.com]]" and "[[.net]]" interests in their [[IDN]] format. That is, Mr. Kane wrote on February 17th, 2011, that VeriSign has every intention to pursue the equivalent transliterations of .com and .net in non ASCII text.<ref>[http://domainincite.com/verisigns-upcoming-battle-for-the-chinese-com/comment-page-1/#comment-4263 DomainIncite Public Comments]</ref>
 Recently, Pat Kane has been working on the implementation of [[DNSSEC]]; VeriSign has been tackling the security measures gradually as it is weary of disrupting any functioning for the large [[.com]] and [[.net]] domains for which it is responsible.<ref>[http://www.zdnet.co.uk/news/security-management/2009/11/16/verisign-major-internet-security-update-by-2011-39877966/ Zdnet.co.uk]</ref>