ICANN is now running two processes dealing with the accountability of its global Internet governance regime: 1) the IANA transition and 2) The “enhancing ICANN accountability and Governance process.”
Unfortunately, the community is getting so deeply involved in the details of both of these processes that they are losing sight of the fundamental issue at stake. The big issue here is not the particular structures of these entities or who is represented on them. The fundamental issue isn’t even ICANN accountability per se. The big issue is this: how can we have an effective regime for global governance of Internet identifiers that maintains the decentralized and distributed, open, free and innovative nature of the Internet? In other words, there is something at stake here more important than accountability, and that is the scope of ICANN’s mission, and Internet freedom itself. Accountability is relevant only insofar as it serves the bigger goal of keeping the internet open and free.
Various types of accountability mechanisms have been proposed, ranging from creation of a new contracting authority, the creation of a new body with the right to second guess any of ICANN’s decisions, and the creation of a membership that can elect and unseat the Board. But these proposals sidestep the more important question: how much power should ICANN have?
Are the DNS root and ICANN going to become a centralized point for broad-based governance of Internet content and conduct, or will we minimize ICANN’s power and try to keep it focused on a relatively narrow mission focused on global interoperability and operational policies directly related to domain names?
If ICANN is willing to accept constitutional limitations on its power then the organizational changes needed to keep ICANN accountable will be much less sweeping and easier to implement.
On the other hand, if ICANN is not willing to accept binding constitutional limitations on its authority, then the accountability safeguards and requirements of both the IANA transition and the ICANN enhanced accountability process have to be beefed up, and the changes will have to be more complex, risky and difficult.
These are the meta-questions that both ICANN the organization and its antagonists and protagonists must answer before they can determine appropriate solutions in the two accountability processes.
A contract that limits the scope of ICANN’s binding policies might be easier to achieve than complicated organizational changes, and could be used to fend off pressures from the GAC and others to turn ICANN into a general purpose Internet Governance body. If such constitutional limitations were in place, the urgency of addressing other structural changes would be reduced.
The terms of such a contract might look something like this (and here I draw heavily on thinking done by David Johnson):
1. ICANN will not establish any binding policy, mandatory contract terms, or other rules governing actions or inactions by domain name Registries, Registrars or Registrants,
(a) in the absence of demonstrated consensus support by affected parties;
(b) relating to any issues other than those the uniform global resolution of which is necessary to assure sound technical operation of the domain name system and associated registration processes; or
(c) regulating online content or online behaviors other than use of a domain name registration itself to commit fraud or engage in extortion, vandalism or system abuse.
2. Any domain name Registry, Registrar or Registrant harmed by ICANN’s violation of the preceding provisions should be able to bring a case before a standing Independent Review Panel with the authority to make binding decisions enforcing those provisions.
3. In consideration of ICANN’s agreement to these terms, the undersigned [Registries] agree to support the proposed IANA transition plan
To conclude, the ongoing debate about ICANN’s accountability cannot be detached from broader concepts of ICANN’s mission and its role in the overall system of Internet governance. More than anything else, accountability mechanisms should be designed with the preservation and enhancement of Internet freedom and openness in mind. Accountability mechanisms should not be designed to legitimate or facilitate the assertion of centralized power over the global Internet.
Milton –
An excellent and thought-provoking post… While I have no view on the merits of the suggestion of contractual limitation with respect to DNS matters, I’m not certain it is clear whether you are suggesting such a limit on ICANN solely in its DNS policy development role, or in both its DNS policy development and implementation roles, or potentially in the larger scope of its oversight for Internet names _and_ numbers? Could you clarify what roles/responsibilities you believe would be covered by such a contract?
Thanks!
/John
John Curran
President and CEO
ARIN
John
The proposal is targeted at ICANN in its role as policy developer for names. Given that ICANN itself does not really make policy for numbers and protocols, but is only supposed to implement policies in its capacity as IANA, it is hard to see how the proposal would apply to these other areas.
A question about your question: if you have no view on the merits of the suggestion, why bother to ask?
As you noted, your proposal is targeted at ICANN in its role as policy developer for names, and the appropriate accountability mechanisms for such activities are best addressed by the affected (i.e. DNS) community.
However, depending on your proposed scope and the particulars of its implementation, your proposal could have unintended side-effects on the ability of the Internet _number_ registry system to be able to facilitate policy development by its relevant community, particularly to the extent that the Internet number registry system (i.e. RIRs/NRO/ASO) remains coupled to ICANN’s overall Internet identifier coordination mission.
Thanks,
/John
John Curran
President and CEO
ARIN
John,
As someone with better than average knowledge of how number policy making takes place, I am having trouble understanding how a constitutional limitation on ICANN’s authority could have unintended side effects on the internet number registry system. At the very least, it would have no effect; at its strongest, it would simply prevent the RIRs, as well as ICANN, from exploiting their position as coordinators and policy makers for the number space to regulate content or other forms of conduct unrelated to the administration of IP addresses. Which would be a good thing. Right?