<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://166/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">It should be noted that Milton's option 3 was ICANN's original intent, prior to intervention by government lawyers at the end of 1998.<div><br></div><div>- M.</div><div><br></div><div><br></div><div><br><div><div>On Feb 12, 2014, at 1:47 PM, Milton L Mueller <<a href="mailto:mueller@SYR.EDU">mueller@SYR.EDU</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: 'Times New Roman'; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">George. You did not quite get the 3 options right. They were:<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; text-indent: -0.25in; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><span>1)<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Unilateral control by 1 govt (the status quo)<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; text-indent: -0.25in; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><span>2)<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Multilateral control<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; text-indent: -0.25in; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><span>3)<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">De-nationalization of the IANA function; ie., removal of USG control and delegation of it to ICANN. Note well: this does NOT require exclusion of governments from all involvement in ICANN.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">What you propose as a solution, �one based upon multistkeholderism,� is actually an attempt to avoid coming to grips with difference between #2 and #3. By attempting to do this, you are seriously muddying the waters at a time that we need absolutely clarity.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">EITHER root zone changes are the responsibility of ICANN, in which case you are advocating #3 (because ICANN is not an intergovernmental organization) OR governments have some kind of special authority over root zone changes, in which case your solution devolves to #2. Please decide which one you are advocating. I will not let you waffle.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">What you�ve done in an attempt to discredit the de-nationalization option is to pretend that if we devolve control to ICANN, that governments are excluded entirely from the process. This is obviously false. Governments currently play a major role in ICANN, via GAC advice. So one could easily cut the cord to the USG, vest the IANA function in ICANN fully, and governments would still be involved. Even if the GAC were dismantled, as some of us favor, it is still completely possible and indeed desirable for individuals who work for or are contracted by governments to participate in ICANN.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Some of us are proposing to reform the role of governments in ICANN to make it consistent with a truly equal-status, multistakeholder<span class="Apple-converted-space"> </span><a name="_MailEndCompose">governance process. I am really getting tired of hearing, as a response to these proposals, that �governments are a part of our world and we can�t ignore or exclude then.� That is either a dishonest or a completely clueless response. By eliminating special powers for governments and avoiding intergovernmental control, we are not proposing to completely exclude governments from the process. We are simply proposing to adhere more consistently to the MS model and give government agencies and employees the same status as everyone else.<o:p></o:p></a></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Milton Mueller<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Professor, Syracuse University School of Information Studies<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><a href="http://faculty.ischool.syr.edu/mueller/" style="color: purple; text-decoration: underline; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(5, 99, 193); ">http://faculty.ischool.syr.edu/mueller/</span></a><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="color: rgb(31, 73, 125); ">></span>The third approach is in my view equally unrealistic. Governments are<span style="color: rgb(31, 73, 125); "><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">></span>a part of our world. They have useful and essential functions We depend upon the creation and evolution of legal structures along with the administrative and judicial mechanisms that institutes and implement them. We may be concerned with their inappropriate use of power, but we can�t deny that they have a place at the table. We are likely, however, to differ about what that place is and what limitations might be put upon them.<br><br>The second approach, one based upon multistakeholderism, seems like the only viable and significantly acceptable one. While that choice may be comforting in terms of its inclusive orientation, the space of solutions that could be called multistakeholder is vast and multidimensional, with the only necessary condition for being in the set is that all relevant stakeholder groups, however defined, have some degree of inclusion into the process and that no one group has an absolute veto over the activities of the group. Distributions of power, representation, and decision making authority all vary, possibly enormously among stakeholder groups. The very choice of what groups are included and who they include contributes to the diversity among solutions. (For example, while ICANN correctly claims to be organized according to a multistakeholder model, in fact it is organized in accordance with a very specific and well-defined instantiation of the multistakeholder model.)<br><br>So if we are going to talk about multi-stakeholder approaches to the problem, we will need to differentiate between a variety of them that might be suggested. Saying that an approach is a multi-stakeholder approach is not sufficient; it will need to be characterized in a more definite manner.<br><br>Finally, any approach that will be successful must make the great majority of us comfortable with its ability to maintain security, stability, and independence of the Internet�s fundamental naming and addressing systems, and with its ability to withstand takeover by any special interests. Governments, including the US government, must be an integral part of that majority if any transition is to be feasible and ultimately successful. Solutions that do not meet this criterion, and are not demonstrably better than what we have now, should not and will not be adopted.<br><br><br><b><u>Incremental approaches</u></b><br><br>Assuming that there are continuity and stability virtues in minimizing the amount of change that is made, I ask myself: are there acceptable solutions to the problem that minimize the account of change needed? In which direction would they go? I personally don�t have a good answer for that. Perhaps others do.<br><br><br><b><u>Diplomatic approaches, from Jovan Kurbalija</u></b><br><br>In a recent provocative article, Jovan Kurbalija has outlined a number of scenarios that find their rationale in established diplomatic behavior. The article, at:<br><br><span class="apple-tab-span"> <span class="Apple-converted-space"> </span></span><a href="http://www.diplomacy.edu/blog/international-inviolability-root-zone" style="color: purple; text-decoration: underline; ">http://www.diplomacy.edu/blog/international-inviolability-root-zone</a><br><br>contains the following scenarios. I include them here because I think they represent serious approaches to the issue we�re discussing. They may or may not be practical.<br><br><br><o:p></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt; "><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">USE DIPLOMATIC LAW APPROACH TO SOLVE THE POLICY PROBLEM OF THE ROOT ZONE<br><br>The predominantly symbolic relevance of the root zone issue has created the basis for an analogy with diplomatic law, which deals with another highly symbolic issue: representation of countries. It includes diplomatic precedence, the protection of diplomatic buildings, and the main functions of representation.[3] How can the regulation of symbolic aspects of diplomatic relations help in regulating the symbolic aspects of Internet politics? Here are two possibilities:<br><br>The first possibility could be described as a �physical� one, making the server and root database inviolable, in particular from any national jurisdiction. This possibility opens the question of where the root server will be located. It could be located at the UN premises in New York and Geneva, which would simplify matters, since those entities already enjoy inviolability, including immunity from any national jurisdiction. Another option, such as continuing to use the current location would require changes in the US national law, in order to ensure international inviolability of the root database. One could also consider assigning root zone file immunity as part of an ICANN+ arrangement (making ICANN a quasi-international organisation � discussed further down in the text). [4]<br><br>The second possibility, which is a �virtual� one: the root database should be assigned inviolabilityper se, wherever it is located. This solution is based on the analogy with diplomatic law which specifies that �[t]he archives and documents of the mission shall be inviolable at any time and wherever they may be.� (i.e. article 24 of the Vienna Convention on Diplomatic Relations).<br><br>In this way, the root database can enjoy inviolability according to international law. Neither the USA, nor any other authority, can interfere with the root database without necessary authorization. This could be the first phase in the policy process, which could build trust, and prepare for the second phase, which has to deal with the more difficult question:<br><br>WHO WILL HAVE THE RIGHT TO AMEND THE ROOT DATABASE?<br><br>Here we get back to the question of decision-making process and the status of ICANN. This has been exhaustively discussed, and it is clear that a workable solution should be based on a high level of inclusion, transparency, and checks and balances. As a practical solution for the root zone file, one could think of a double key system, involving a strengthened ICANN, with a stronger role for the GAC (to some extent codifying and formalizing what has been happening through the growing relevance of the GAC). A possible role for a reformed UN Trusteeship council could also be considered, as one of the actors in this checks and balances system.<br><br>ICANN�s new quasi-international status, for example, following Swiss laws, could address most of the above-mentioned points. Shifting ICANN from the national to the international level, would require ensuring ICANN�s accountability towards consumers, users, and the Internet industry. Immunity should not be impunity. Again, here we could have a solution through the interplay between international public law and private law options.<br><br>HOW TO ACHIEVE THE NEW ROOT ZONE ARRANGEMENT?<br><br>The closest analogy is the governance of the Red Cross system. Analogous to the Geneva conventions in the humanitarian field, �a root convention� would minimally grant immunity to the root database, and maximally specify how the root database would be managed. If the adoption of a root zone file convention would be too complex, one could consider an advisory opinion of the International Court of Justice, which could recognize the �instant� customary law (practice of the US government of not interfering in countries' domain names without the consent of these countries). Either a convention or instant customary law would provide a functional basis for ICANN, which could be a quasi-international organisation, with a carefully balanced checks and balances approach, and a prominent role for the GAC. Such an ICANN+ would both host the root server, and manage the root database.<br><br>There are some other solutions and possibilities. The bottom line is that there is a solution that could be both practical and legal. The symbolic issue of the root zone, at least, could be put to rest, and allow us to spend �policy energy� on more practical and relevant issues. It could be also be a reasonable compromise.<o:p></o:p></div></blockquote><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div></div><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><br><b><u>Conclusion</u></b><br><br>It�s quite possible that all of the above is a product of too limited thinking, and that an alternative, more comprehensive and high level approach looking at the entire Internet ecosystem as a whole might be more fruitful. If so, what might such an approach be based upon, and why might it look like? Perhaps on further reflection, and considering possible approaches to it, we may find that the problem definition is lacking, and needs modification or amplification. If so, that represented profess of a certain kind.<br><br>I present the above as my thoughts regarding possible approaches, with a large contribution from Jovan. I admit to not having good answers to the problem, but I hope that the above material is helpful to starting a serious discussion. If there is any appetite on the list to continue this discussion, I, and possibly others, would be interested in your comments.<br><br>Regards,<br><br>George<br><br><br><o:p></o:p></p></div></div>_______________________________________________<br>discuss mailing list<br><a href="mailto:discuss@1net.org" style="color: purple; text-decoration: underline; ">discuss@1net.org</a><br><a href="http://1net-mail.1net.org/mailman/listinfo/discuss" style="color: purple; text-decoration: underline; ">http://1net-mail.1net.org/mailman/listinfo/discuss</a></div></blockquote></div><br></div></body></html>