Changes

He has  worked extensively around the development and deployment of [[IDN]]s, both within VeriSign and in external organizations like ICANN.<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>

He has  worked extensively around the development and deployment of [[IDN]]s, both within VeriSign and in external organizations like ICANN.<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>

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>

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]] 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> While Verisign has been involved with DNSSEC development for some 15 years, the final implementation of the newest protocols has been mainly achieved since 2009, under Pat Kane's supervision.<ref>[http://vimeo.com/8337003 Vimeo Video]</ref>

 

==Community Participation==

==Community Participation==

Mr. Kane is a member of [[ICANN]]'s Presidential Advisory Board on [[IDN]]s, and is also involved in the [[GNSO]]'s IDN Guidelines Review Committee.<ref>[http://www.gtldregistries.org/about-us GTLD Registries.org]</ref>

Mr. Kane is a member of [[ICANN]]'s Presidential Advisory Board on [[IDN]]s, and is also involved in the [[GNSO]]'s IDN Guidelines Review Committee.<ref>[http://www.gtldregistries.org/about-us GTLD Registries.org]</ref>