Pat Kane: Difference between revisions
| Line 16: | Line 16: | ||
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> 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><ref>[http://www.theregister.co.uk/2005/11/24/icann_idn_committee/ The Register.co.uk 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]] 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> | 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> | ||
Revision as of 18:38, 25 February 2011
 |
 |
| Country: | USA |
| Email: | pkane [at] verisign.com |
| LinkedIn: |  [Patrick Kane Pat Kane]
|
Patrick Kane is the Senior vice-President and General Manager of Naming Services at VeriSign, where he has worked since 1999.[1]
VeriSign[edit | edit source]
Pat Kane is responsible for the operational management, and relevant policy development for all TLDs 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 IDNs, both within VeriSign and in external organizations like ICANN.[2]Cite error: Closing </ref> missing for <ref> tag
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.[3] 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.[4]
Community Participation[edit | edit source]
Mr. Kane is a member of ICANN's Presidential Advisory Board on IDNs, and is also involved in the GNSO's IDN Guidelines Review Committee.[5] Pat participated in VeriSign's February, 2011, celebration of 15 years of the commercial Internet in New Delhi, India.[6] He is a frequent particpant at ICANN's meetings.[7][8]
Prior Work[edit | edit source]
- Senior Principal, American Management Systems
- Engagement Manager, State & Local Governments
- Account Manager, Electronic Data Systems
- Systems Engineering Manager, Various Companies[9]