Pat Kane: Difference between revisions
No edit summary |
m added Category:IDN Community using HotCat |
||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{People | {{People | ||
|portrait | |portrait=PatKanePortraitNew.JPG | ||
|caricature = Digital Caricatures Live Pat K.jpg | |caricature=Digital Caricatures Live Pat K.jpg | ||
| | |organization=Verisign | ||
|country | |region=North America | ||
|email | |country=USA | ||
|stakeholdergroup= | |||
|affiliation=GNSO | |||
|email=pkane [at] verisign.com | |||
|linkedin | |linkedin=https://linkedin.com/pub/patrick-pat-kane/2/292/367 | ||
|userbox | |userbox={{Template:UBX-CARDSSING}} | ||
}} | }} | ||
'''Patrick Kane''' is the Senior Vice-President and General Manager of Naming Services at [[Verisign]], where he has worked since 1999.<ref>[http://www.verisigninc.com/en_AU/news-events/press-room/executive-bios/index.xhtml#kane VerisignInc.com]</ref> | '''Patrick Kane''' is the Senior Vice-President and General Manager of Naming Services at [[Verisign]], where he has worked since 1999.<ref>[http://www.verisigninc.com/en_AU/news-events/press-room/executive-bios/index.xhtml#kane VerisignInc.com]</ref> | ||
| Line 17: | 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><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 | 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== | ||
| Line 36: | Line 35: | ||
{{reflist}} | {{reflist}} | ||
__NOTOC__ | __NOTOC__ | ||
[[Category:Private Sector - Domain Name Industry]] | |||
[[Category:IDN Community]] | |||
Latest revision as of 18:45, 6 July 2021
 |
 | ||
| Organization: | Verisign | ||
| Affiliation: | GNSO | ||
| Region: | North America | ||
| Country: | USA | ||
| Email: | pkane [at] verisign.com | ||
| LinkedIn: |  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
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][3] 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.[4]
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.[5] 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.[6]
Community Participation edit
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.[7] Pat participated in Verisign's February, 2011, celebration of 15 years of the commercial Internet in New Delhi, India.[8] He is a frequent participant at ICANN's meetings.[9][10]
Prior Work edit
- Senior Principal, American Management Systems
- Engagement Manager, State & Local Governments
- Account Manager, Electronic Data Systems
- Systems Engineering Manager, Various Companies[11]