ICANN – Statement of Interest

For most of you, this page will seem odd.  It's just a handy way for me to publish a statement of interest that's required each time I join an ICANN working group.

The participant's current vocation, employer and position

Vocation - domain investor and gadfly

Employer - The O'Connor Company of St Paul

Position - Proprietor

The type of work performed in the bullet above

Very little -- I'm mostly retired.  So I watch the grass grow, volunteer in a variety of public-policy fora, and keep an eye on investments of various kinds.

Identify any financial ownership or senior management/leadership interest in registries, registrars or other entities that are stakeholders or interested parties in ICANN or any entity with which ICANN has a transaction, contract, or other arrangement

None.

Identify any type of commercial interest in ICANN GNSO policy development outcomes. Is the participant representing other parties?

I'm interested in GNSO policy outcomes as a domain-name owner and investor.

I am not representing other parties.

Describe any arrangements or agreements between the participant and any other group, constituency or person(s) regarding the participant's service as a participant in any ICANN policy making process.

None.

Geographic Region associated with the nationality of Participant

North America

Stakeholder Groups in which Member currently participates within ICANN

GNSO Commercial and Business Users Constituency

______

Here are some sections that expand the Statement of Interest to address questions posed by specific working groups

For the High Security Top Level Domain advisory group:

Please mention any ISO/IEC27000 series related experience, education or professional certifications, as well as your level of expertise, if any, in this kind of Information Security framework

My experience in high security TLD matters is just like my experience in all things technical -- learned in the school of hard knocks.  I hold no certifications of any kind.  However, I've spent the better part of my life dealing with security issues in one way or another.  Here's a list of relevant stuff;

  • Led the Security, Redundancy and Vulnerability sub-team of Minnesota's Broadband Advisory Task-Force (appointed by Minnesota Governor Tim Pawlenty)
  • Employed as an enterprise systems consultant (and thus coped with real-life security issues) at various times by Andersen Consulting (now Accenture) and Coopers and Lybrand (now PriceWaterhouseCoopers)
  • Was the Administrative CIO and Controller at the University of Minnesota (plenty of interesting security issues arise when students, faculty and administrative systems share the same networks)
  • Developed the enterprise security function for the 50-campus community and technical college system in Minnesota
  • Owned and ran an ISP starting in 1994 -- again, an opportunity to learn about security when there weren't many sign-posts on the highway

Comments are closed.