Name: Mark McFadden
Address: 513 Elmside
Blvd Madison
WI 53704-5707 USA
Contact: (608) 241 2373 Home
(608) 240 1560 Work
email: mcfadden [at] cix [dot] org
Country of Residence: US
Occupation: Chief Technology Officer
Place of Work: Commercial Internet eXchange
1301 K Street
NW Suite 325
Washington DC 20005
Education: Bachelor of Science
Mathematics and Philosophy University of Wisconsin – Madison
Master of Science in Computer Science University of Wisconsin – Madison

Experience: 11 years of Internet experience in public and private settings as a network engineer, ISP, consultant to ISPs and now as Chief Technology officer at the Commercial Internet eXchange (CIX). CIX is a non-profit trade association of ISPs and public data internetworking service providers which promotes and encourages the development of the industry in both national and international markets. Founded in 1991,CIX is the largest and oldest trade association of ISPs and Internet- related business in the United States. It provides a neutral forum for the exchange of ideas and information and develops positions on legislation and policy issues among suppliers of internetworking services.

In my role as Chief Technology Officer at CIX I have been responsible for the technical coordination of all of CIX’s activities. As a routine participant in the IETF and in the open work of the regional registries I have contributed to the development of global addressing policy over the last seven years. I’ve also been asked to provide technical guidance to governmental and regulatory bodies on technical issues related to addressing and connectivity.

I’ve been a participant at the IFWP meetings that helped propel the activity that eventually became ICANN. I’m currently one of the editors of ICANN’s Ad Hoc report on Addressing and a regular participant in the work of the ASO and the ISP and connectivity provider constituency in the DNSO.

I believe that it is a critical time in the evolution of ICANN. Many of ICANN’s basic decision making structures have been called into question. While many of the battle lines have been drawn in the area of naming, I believe that addressing will come under scrutiny as well. What ICANN needs is leadership with a firm foundation in the technical operation of the Internet. Even at the ICANN Board level there is a critical need for management with an understanding of how addressing policy is developed and implemented. Ensuring that the ICANN board has a resource that understands the interaction between the regional registries, their customers, and the new global pressures that are being brought on addressing policy is critical.

In addition, it is essential that ICANN have leadership that works to preserve ICANN’s original goal of combining an open and transparent global forum for consensus building on a limited number of technical issues. I seek to ensure that ICANN does not suffer from “scope creep” so often associated with new bodies that emerge into a policy vacuum. If ICANN is to achieve its goal of gaining credibility in the Internet community it must succeed at balancing its natural tendency to expand its policy role with a commitment to limit its work to the technical coordination role for which it was originally established. Whether the issue is naming, addressing or protocol development ICANN should not attempt to replace organizations that are already succeeding. Instead it should provide a global forum for coordination and consensus development between constituents and organizations that already exist.

I think the combination of my experience with the regional registries, day-to-day production engineering, and in ICANN itself are good qualifications for this effort.