You have my vote
Jeremy Lumby
Minnesota VoIP
9217 17th Ave S
Suite 216
Bloomington MN 55425
Main 612-355-7740
Direct 612-392-6814
EFax 952-873-7425
jlumny(a)mnvoip.com
-------- Original message --------
From: Mike O'Connor <mike(a)HAVEN2.COM>
Date: 6/14/17 1:47 PM (GMT-06:00)
To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET
Subject: [MICE-DISCUSS] a Madison-based ICANN colleague of mine wonders
if he could represent us at ICANN?
_____
>From : Mike O'Connor [mike(a)HAVEN2.COM]
To : MICE-DISCUSS(a)LISTS.IPHOUSE.NET [MICE-DISCUSS(a)LISTS.IPHOUSE.NET]
Date : Wednesday, June 14 2017 13:46:01
hi all,
Mark McFadden inquired as to whether he could take on the volunteer
"represent MICE at ICANN" role that i used to fill. if that decision
were left entirely to me i would say "absolutely" as Mark is one of the
folks i held in highest regard while i was a participant at ICANN. i'm
putting this request to you in much the same way that i did when i
asked whether i could represent us, back in 2012. this would be a
volunteer arrangement in which Mark would stand ready to provide
briefings and insights as MICE requests - in return for which he would
have standing within ICANN to continue his very long involvement in
that organization.
i did a search on "Mark McFadden ICANN" which turned up all kinds of
stuff. i thought this recent letter from Mark did a pretty good job of
summarizing his qualifications.
ICANN:
I am pleased to submit my name for consideration for
the AoC Review Team on Security, Stability, and Resilience of the DNS.
I have attached a short CV and my statement of interest. Note that I
have a formal Conflict of Interests statement, dated 1 August 2016, on
file with ICANN.
I have been a participant in ICANN since its beginnings
serving as Secretariat to the ISPCP constituency, the Chair of the
Address Supporting Organization, member of the RSTEP, and most recently
as a member of the ISPCP constituency. I have also directed work on two
of the Independent Evaluation panels for the new gTLD program.
I have significant experience working with DNS
infrastructure in my time at BT and subsequently as an advisor for
Western European governments on Internet policy related to the DNS. In
that capacity, I’ve worked on DNSSEC projects, standardization efforts
in the IETF, and performance and security management for large DNS
implementations. I believe that the combination of technical and policy
background makes for a very helpful addition to the SSR2.
While with BT, I was responsible for policy and
technical coordination of a global DNS implementation and worked on
DNSSEC, enum and other infrastructure related issues.
My interests in stability issues related to the DNS is
broad. I have been a contributor to DNSOP in the IETF and to the effort
to understand name collision in the context of the expansion of the DNS
namespace.
I believe that the DNS is in the midst of significant
evolutionary change and that the security, stability and resilience of
the DNS is under threat in ways that were not the case during the first
SSR. My interest in SSR2 is in enhancing the security, stability and
resiliency of the DNS is practical, standards-based, data-driven
approaches with clear mandates for ICANN and the community that makes
ICANN effective.
Best regards,
Mark
Mark McFadden
Principal Consultant, Internet Infrastructure and
Governance InterConnect Communications
what say you all? can i expand my "absolutely" vote from me to the
rest of you?
thanks for considering this idea,
mike
WI:(715) 598-4284 MN:(651) 647-6109 Toll Free:(800) 896-0907
Fax:(866)-280-2356
