<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks for this. Indeed, it explains a lot. Excellent.<br>
Stephanie Perrin<br>
<br>
<div class="moz-cite-prefix">On 2015-08-28 12:19, Pranesh Prakash
wrote:<br>
</div>
<blockquote cite="mid:55E08A1A.5020906@cis-india.org" type="cite">Dear
all,
<br>
Please make sure you read this post by Milton (excellent, as
always).
<br>
<br>
While I highly recommend reading the entire post, for the TL;DR
crowd:
<br>
<br>
[snip]
<br>
<blockquote type="cite">The most interesting part of the
announcement, however, was not the extension itself but the way
the NTIA has finally started to come to grips with the role of
Verisign and changes in the root zone management process. Along
with the extension announcement, NTIA published a proposal “Root
Zone Administrator Proposal Related to the IANA Functions
Stewardship Transition.” As we noted in a blog post back in
March 2014, it is really the Verisign Cooperative Agreement, not
the IANA functions contract, that gives the US government
authority over all root zone file changes. It is Verisign, not
ICANN, that has operational control of the root zone, so if the
Cooperative Agreement with Verisign doesn’t go away, neither
does U.S. control of the DNS root.
<br>
</blockquote>
[/snip]
<br>
<br>
[snip]
<br>
<blockquote type="cite">To conclude, the NTIA-ICANN-Verisign
triumvirate seems inconsistent with the overall ethos of open,
bottom up development of a transition plan. There are reasons
why this is a sticky issue, of course. Still, the U.S.
government and ICANN have to be very careful about how they
handle this. If the “global multi-stakeholder community” invoked
by the original transition announcement goes through an arduous
process to replace the IANA functions contract only to learn
that Verisign and NTIA still have a compact that gives the U.S.
control of root zone changes, their credibility – and the
credibility of the entire process model used to develop the
transition – will be shot, and the ‘transition’ will have done
more damage than good to globalizing Internet governance.
<br>
</blockquote>
[/snip]
<br>
<br>
Regards,
<br>
Pranesh
<br>
<br>
Mueller, Milton L <a class="moz-txt-link-rfc2396E" href="mailto:milton.mueller@pubpolicy.gatech.edu"><milton.mueller@pubpolicy.gatech.edu></a>
[2015-08-20 20:39:28 +0000]:
<br>
<blockquote type="cite">My analysis of the latest NTIA
announcement: "What's going on between NTIA, ICANN and
Verisign?"
<br>
<a class="moz-txt-link-freetext" href="http://www.internetgovernance.org/2015/08/18/whats-going-on-between-ntia-icann-and-verisign/">http://www.internetgovernance.org/2015/08/18/whats-going-on-between-ntia-icann-and-verisign/</a>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">____________________________________________________________
You received this message as a subscriber on the list:
<a class="moz-txt-link-abbreviated" href="mailto:governance@lists.igcaucus.org">governance@lists.igcaucus.org</a>
To be removed from the list, visit:
<a class="moz-txt-link-freetext" href="http://www.igcaucus.org/unsubscribing">http://www.igcaucus.org/unsubscribing</a>
For all other list information and functions, see:
<a class="moz-txt-link-freetext" href="http://lists.igcaucus.org/info/governance">http://lists.igcaucus.org/info/governance</a>
To edit your profile and to find the IGC's charter, see:
<a class="moz-txt-link-freetext" href="http://www.igcaucus.org/">http://www.igcaucus.org/</a>
Translate this email: <a class="moz-txt-link-freetext" href="http://translate.google.com/translate_t">http://translate.google.com/translate_t</a>
</pre>
</blockquote>
<br>
</body>
</html>