<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    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.&nbsp; 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.&nbsp; Am I missing the checks and
    balances?<br>
    <br>
    Best-<br>
    <br>
    Joe<br>
    <div class="moz-cite-prefix">WOn 3/3/2014 9:43 PM, Milton L Mueller
      wrote:<br>
    </div>
    <blockquote
      cite="mid:6435223fdac74dc98d0def6c100d215a@EX13-MBX-13.ad.syr.edu"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 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";}
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;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle19
        {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]-->
      <div class="WordSection1">
        <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.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><a moz-do-not-send="true"
            name="_MailEndCompose"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></a></p>
        <div>
          <p class="MsoNormal"><span style="color:#1F497D">&gt;</span>Why
            is removing USG not mean just that? End of contract<span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></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.<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></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?<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></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? <o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><span style="color:#1F497D">&gt; </span>What
            problem is being solved by combining functions from other
            organizations to
            <span style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">&gt; </span>create
            another entity dnsa?&nbsp;<span style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></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.
              <o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><span style="color:#1F497D">&gt;</span>The
            proposed Dnsa is potentially a consortium of 1000+
            registries and how would this work.
            <span style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></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.
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></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). <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">&gt;</span>Is
            this different from creating another ICANN&nbsp;<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></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<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:discuss@1net.org">discuss@1net.org</a>
<a class="moz-txt-link-freetext" href="http://1net-mail.1net.org/mailman/listinfo/discuss">http://1net-mail.1net.org/mailman/listinfo/discuss</a></pre>
    </blockquote>
    <br>
  </body>
</html>