<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#333333;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:#333333;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:#333333;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:#333333;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:#333333;}
span.moz-txt-citetags
{mso-style-name:moz-txt-citetags;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I'm re-sending this because Parminder has ignored it. Really interested in rational dialogue on this topic.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">==============</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Some responses to Parminder's views on CIR oversight<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">It is important to do so, if we have to legitimately argue for safe-guarding existing distributed system of CIR management and technical standards setting.<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[MM] Let me begin by pointing out that neither you nor your group has ever attended an ICANN meeting, nor have you sought membership
or participation in the civil society representational organs of ICANN, despite many invitations and despite the many battles ICANN civil society has needed help to fight. Thus, it is surprising to see you eager to redefine the whole structure suddenly. One
wonder whose agenda it is, as it is certainly not civil society's. Also, some awareness of the behavior of the Governmental Advisory Committee within ICANN might be sufficient to convince those with a reality-focused, objective perspective that the types of
"oversight" you are calling for can be troublesome, to put it mildly. I'd encourage you to make better use of the many resources - experience, expertise, and networks - that already exist among ICANN-focused civil society, before developing yet another manifesto.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">The other option is that developing countries lean towards the ITU, which can shift the terrain toward development of a new top-down, centralised and bureaucratic CIR management/ tech standards model.
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[MM] Many developing countries have "leaned toward the ITU" for years. It is unlikely to affect anything. If the case for your
proposed changes is fear of this alternative, it is a very weak case.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">(1) Shifting oversight of CIRs from US gov to an international body<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[MM] It should not be "international" it should be "non-national." To be "international" is to be an intergovernmental organization,
which means _<i>not acceptable to Internet freedom advocates</i>_. A smaller club of governments (which has been proposed by European Commission at one time) could be even worse. Oddly, you seem to be completely unaware of the critiques of the whole notion
of "oversight," and its sister concept of "public policy" that have been developed in the wake of WSIS.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The path toward accountability and legitimate process in CIRs is _<i>not</i>_ going to come from concepts of an additional (governmental
or MS) committee providing "oversight" on behalf of "public policy" or "public interest" concerns. On the contrary, as we have learned from the end game of the new gTLD process, the concept of oversight inevitably devolves into a politicized battle among special
interests to undo, or re-do, policies emerging from the bottom up process if they don't like the outcome. "Oversight" means arbitrary, politicized, unpredictable and hence unjust and inefficient process. "Oversight" means imposing another unaccountable board
on top of the existing ICANN board, when the problem is that the existing one is not accountable enough. Replacing US oversight with oversight by multiple governments compounds the problem we have, it doesn’t fix it.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What is needed are clear rules - rules designed both to restrain and limit ICANN, and to restrain and limit the external forces,
including especially governments, who might interfere with ICANN and its processes. IGP made a pretty good start at defining the principles underlying such rules in its filings on the ICANN "transition" back in 2009.
<a href="http://www.internetgovernance.org/wordpress/wp-content/uploads/IGP-June09NTIAcomment.pdf">
http://www.internetgovernance.org/wordpress/wp-content/uploads/IGP-June09NTIAcomment.pdf</a> (See section "Revising the model")<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In those comments, you may find a great deal of common ground - we recognize the need for legally binding forms of accountability
and that this may need to involve coordinated action among states to pass a treaty. The big difference is that you seem to want an "oversight" body with the arbitrary power to make policy from the top down and impose it on ICANN processes and communities,
whereas our proposals are designed to prevent just that. We want the involved community to make policy, within very narrowly defined boundaries, and we want rules we need from governments, and liberal, freedom-enhancing rules - not a blank check to second-guess
or re-do or control and regulate people's actions via the Internet. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Milton L. Mueller<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Professor, Syracuse University School of Information Studies<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Internet Governance Project<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a href="http://blog.internetgovernance.org">http://blog.internetgovernance.org</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
</div>
</body>
</html>