<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>
<!-- Template generated by Exclaimer Mail Disclaimers on 11:49:04 Tuesday, 4 March 2014 -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">P.93b5a155-0e5a-4951-b82e-e4e57c15e417 {
MARGIN: 0cm 0cm 0pt
}
LI.93b5a155-0e5a-4951-b82e-e4e57c15e417 {
MARGIN: 0cm 0cm 0pt
}
DIV.93b5a155-0e5a-4951-b82e-e4e57c15e417 {
MARGIN: 0cm 0cm 0pt
}
TABLE.93b5a155-0e5a-4951-b82e-e4e57c15e417Table {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</style>
<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:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle21
{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="#0563C1" vlink="#954F72">
<p class="93b5a155-0e5a-4951-b82e-e4e57c15e417"></p>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">The popular term for this might be “the fox guarding the henhouse.” Of course, if it is merely “operational,” then perhaps the concern is overblown. But if these functions are merely operational, why not just
leave them at ICANN?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Greg Shatan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> discuss-bounces@1net.org [mailto:discuss-bounces@1net.org]
<b>On Behalf Of </b>joseph alhadeff<br>
<b>Sent:</b> Tuesday, March 04, 2014 9:55 AM<br>
<b>To:</b> discuss@1net.org<br>
<b>Subject:</b> Re: [discuss] Roadmap for globalizing IANA<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">While I am not as well versed in these issues and their history of some of the more frequent commentators, it would seem that accountability is often benefited by and predicated on a separation of duties in oversight. The new organization
seems to rely on self-interested parties having an alignment of interest with the public good as opposed to the more traditional concept of separation of duties/interest in oversight. Am I missing the checks and balances?<br>
<br>
Best-<br>
<br>
Joe<o:p></o:p></p>
<div>
<p class="MsoNormal">WOn 3/3/2014 9:43 PM, Milton L Mueller wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="color:#1F497D">Nii, thanks for your questions. Most of them are actually answered in the paper itself, but I will answer your questions directly.
</span><o:p></o:p></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D"> </span></a><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">></span>Why is removing USG not mean just that? End of contract<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">First, it would be the end of 2 contracts, not one. ICANN and Verisign. You cannot just end the IANA functions contract.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Second, both contracts contain serious accountability measures. However wrongly conceived the idea of unilateral U.S. oversight is, how do we ensure that the root zone is managed properly and what is the recourse
if the root zone managers are either negligent, incompetent or corrupt? What do you replace the IANA contract with?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">The reason for a DNSA is that registries have the strongest incentive to get root zone management right. It is their data that the root zone contains. To ensure impartial administration we create a nondiscriminatory
right to own DNSA to all registries? </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">> </span>What problem is being solved by combining functions from other organizations to
<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">> </span>create another entity dnsa? <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">As noted above: 1) accountability problem; 2) incentives problem. To which we can add: not letting ICANN get too powerful.
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">></span>The proposed Dnsa is potentially a consortium of 1000+ registries and how would this work.
<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Not that many companies involved. More like a few hundred; lots of companies have multiple TLDs. Ownership shares might be based on some metric of size, such as names under registration, etc.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">How does GNSO work? How does ccNSO work? How did Intelsat work? (consortium of ~200 national telecom operators). How did Nominet work? (shared ownership by many registrars) How does IEEE work? (hundreds of thousands
of members). </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">></span>Is this different from creating another ICANN <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Very different. ICANN is for making policy. It involves representation of diverse stakeholders and a complicated process for developing consensus on policy and approval by the board. DNSA is for operations. Most
people I have talked to agree that we need to keep those things separate. So, we separate them</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>discuss mailing list<o:p></o:p></pre>
<pre><a href="mailto:discuss@1net.org">discuss@1net.org</a><o:p></o:p></pre>
<pre><a href="http://1net-mail.1net.org/mailman/listinfo/discuss">http://1net-mail.1net.org/mailman/listinfo/discuss</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
</div>
<p></p>
<p class="93b5a155-0e5a-4951-b82e-e4e57c15e417"> </p>
<p class="93b5a155-0e5a-4951-b82e-e4e57c15e417" align="center"><font size="1"><font size="3" face="Arial"><font size="2" face="Arial">* * *</font></font></font></p>
<p class="93b5a155-0e5a-4951-b82e-e4e57c15e417"><font size="1"><font size="3" face="Arial"><font size="2" face="Arial">This E-mail, along with any attachments, is considered confidential and may well be legally privileged. If you have received it in error,
you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Thank you for your cooperation.</font></font></font></p>
<p class="93b5a155-0e5a-4951-b82e-e4e57c15e417" align="center"><font size="1"><font size="3" face="Arial"><font size="2" face="Arial">* * *</font></font></font></p>
<p class="93b5a155-0e5a-4951-b82e-e4e57c15e417"><font size="1"><font size="3" face="Arial"><font size="2" face="Arial">To ensure compliance with Treasury Department regulations, we inform you that, unless otherwise indicated in writing, any U.S. Federal tax
advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (1) avoiding penalties under the Internal Revenue Code or applicable state and local provisions or (2) promoting,
marketing or recommending to another party any tax-related matters addressed herein.</font></p>
<p style="MARGIN: 0in 0in 0pt" align="right"><font size="1">Disclaimer Version RS.US.20.10.00</font></p>
</font></font>
<p></p>
<p></p>
<p></p>
<p></p>
</body>
</html>