Changes

|region=North America

|region=North America

|country=USA

|country=USA

|stakeholdergroup=Private Sector - Domain Name Industry

|stakeholdergroup=

|affiliation=GNSO

|affiliation=GNSO

|email=pkane [at] verisign.com

|email=pkane [at] verisign.com

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

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

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><ref>[http://www.theregister.co.uk/2005/11/24/icann_idn_committee/ The Register.co.uk]</ref>  As the [[IDN]] new gTLD process opened up, Verisign, via Pat Kane, 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><ref>[http://www.theregister.co.uk/2005/11/24/icann_idn_committee/ The Register.co.uk]</ref>  As the [[IDN]] new gTLD process opened up, Verisign, via Pat Kane, 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 functionality for the large [[.com]] registry 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 largely been achieved since 2009, under Pat Kane's supervision.<ref>[http://vimeo.com/8337003 Vimeo Video]</ref>

Pat Kane has been working on the implementation of [[DNSSEC]]; Verisign has been tackling the security measures gradually as it is wary of disrupting any functionality for the large [[.com]] registry 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 largely been achieved since 2009, under Pat Kane's supervision.<ref>[http://vimeo.com/8337003 Vimeo Video]</ref>

==Community Participation==

==Community Participation==

{{reflist}}

{{reflist}}

__NOTOC__

__NOTOC__