[discuss] [IANAxfer] [ccnso-igrg] Two accountability questions - help pls- Workshop 23 - ICANN accountability
Milton L Mueller
mueller at syr.edu
Fri Sep 5 06:47:11 UTC 2014
I actually don't know if moving the IANA outside of ICANN is a good idea or not; there are
certain stability issues that weigh heavily, but we also have existence proof that such teams
can be transitioned from their parent organizations successfully. My main point is that moving
IANA (or not) doesn't actually have any meaningful impact on the ICANN accountability, which
appears (from those on the sidelines such as myself) to be the DNS communities principal
source of angst.
You pretend to not have an opinion about something but then offer arguments and observations that support only one point of view. I find this less than transparent. Let's be honest and clear about this: you want the IANA functions to stay in ICANN, and all of your arguments are structured to defend that point of view, and they have been for months.
Now let me take up your argument that structural separation "has no meaningful impact on ICANN accountability."
For someone whose interventions are usually well supported, it seems an unusually poorly thought out argument.
The ultimate form of accountability is when the IANA functions can be taken away from the provider. That is, the contract can be awarded to someone else if ICANN performs poorly, takes ultra vires actions, etc. The separability of IANA is meant to foster this kind of a relationship. If ICANN the policy development organ and ICANN the IANA functions operator are indelibly linked together, you cannot change the provider of the IANA services without also destroying the policy development functions. You would have to start all over, create an entirely new ICANN or (what is more likely) limp along with bad performance or abuses and try to flog away at them from the inside of ICANN. That option is clearly an inferior one. A structurally separated ICANN lends itself to a clear focus on the performance of the IANA functions in isolation and lends itself to clear, quick and clean rectification of problems.
Under the NTIA contracting regime we do have such separation, more or less, because in principle NTIA can award the IANA contract to someone else. Thus, the IANA functions provider is separable from ICANN.
The other way in which separation affects accountablity is by making the relationship between finalized policy and implementation more visible, more easily regulated, more transparent. The process of moving from ICANN policy to IANA implementation has to move across clear organizational boundaries, and that means it can be observed and organized for oversight better. This also has the very important effect of preventing the policy developer from implementing a policy that has not really been finalized. Imagine what would happen, e.g., if ICANN could just put something in the root, or remove it, without going through a consensus policy process. It would have arbitrary power over the global DNS. Structural separation of the policy development process from implementation prevents this from happening; ergo, it is more accountable.
I hope this makes it clear to you how accountability and structural separation are related. Of course, I don't expect to change your position on this - as I said, it is evident that you do take sides on this issue and that you oppose structural separation.
Milton L Mueller
Syracuse University School of Information Studies
Internet Governance Project
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss