<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Too many of the submissions on this thread are building sandcastles. Admittedly, the geopolitical space surrounding the Internet is a vacuum and has many power brokers or wannabe power brokers circling around. So be it. Some people have more time on their hands than others.<div><br></div><div>But as George suggests, let’s leave IANA out of it. </div><div><br></div><div>Believe it or not, Jon Postel created the system of thirteen root servers and recruited their international group of volunteer engineer operators before there ever was an ICANN, or WCIT, GAC, or ATRT, or any of the overburden of alleged oversight. The system is highly redundant, technically robust, globally distributed, and run by people with no financial interest in what they do. It is fully automated, resolving billions of queries every day. More than three quarters of those resolutions are in domains that existed before ICANN and were mercifully not subject to “oversight."</div><div><br></div><div>The policy inputs to the root server table entries are few and remarkably stable. One of them is the UN’s ISO 3166 country code table and it goes years without a change. The principal other one is ICANN’s Board, which has constructed, over six years of community input, a 300 page policy guide on how to establish a new commercial top level domain. </div><div><br></div><div>Do we need a new and elaborate superstructure of “accountable” people and organizations to sit on top of this well functioning piece of critical infrastructure? The short answer is no.</div><div><br></div><div>But what about the existing NTIA role, you might ask. In fact, as others have said, it is an empty role that was never envisaged as part of ICANN. It is not mentioned in the 1998 NTIA White Paper, which contained the policy guidance for creating ICANN. The IANA contract was cooked up after the fact by nervous nellie lawyers within the government under political pressure. It’s main purpose over the years has been to serve as a legal cudgel to satisfy domestic political factions. We are all well rid of it.</div><div><br></div><div>But what about a rogue ICANN, you might ask. With regard to new root server table entries, they are approved by the Board after running the [expensive] gauntlet of the TLD policy process described above. Aggrieved parties have access to multiple layers of reconsideration and to the courts. ICANN has lost in court over allegations of not following its own policy guidance, and certainly newly aggrieved applicants would be quick to use the judiciary again if necessary. It is inconceivable that some new system of process and accountability for new commercial name registries would be substantively better than what has taken so many years to put in place.</div><div><br></div><div>But what about collusion or malfeasance on the Board, you might ask. The process of selecting a majority of the voting members of the Board members has received much attention over the years, and is carefully constructed and controlled by a group of volunteers from the community separately from the Board. It has been reviewed repeatedly. If there is a robust and more equitable method out there, propose it.</div><div><br></div><div>Finally, what about that old bugaboo, “capture” of ICANN and the root. In the early years, perhaps, emphasize perhaps, that had some reality. Today, we have a large, informed, engaged, and activist audience for ICANN policy making. We are in the process of making that audience larger and of finding some way short of crude power politics to enfranchise new stakeholders. Only the paranoid fringe can find traction for capture now.</div><div><br></div><div>But in the cacophonous debate over IG, let’s preserve the peace and competence of IANA. Some days, we don’t seem to know how good a deal we have.</div><div><br></div><div>- Mike</div><div> </div><div><br></div><div> <br><div><br></div><div><br></div><div><br></div><div><br><div><div>On Mar 18, 2014, at 8:24 AM, Alejandro Pisanty <<a href="mailto:apisanty@gmail.com">apisanty@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi,<div><br></div><div>that is not the way the Internet's successful multistakeholder governance mechanisms have emerged - no need to ask for a higher, central, global authority for permission. In fact, the pieces of it that exist had to be circumvented in order to get the Internet to expand. The top-down authorization echoes the delusion of One World Government and is the major flaw of the MIPOG idea. </div>
<div><br></div><div>Alejandro Pisanty</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 18, 2014 at 7:22 AM, Jeremy Malcolm <span dir="ltr"><<a href="mailto:Jeremy@malcolm.id.au" target="_blank">Jeremy@malcolm.id.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 18 Mar 2014, at 5:58 pm, Kleinwächter, Wolfgang <<a href="mailto:wolfgang.kleinwaechter@MEDIENKOMM.UNI-HALLE.DE">wolfgang.kleinwaechter@MEDIENKOMM.UNI-HALLE.DE</a>> wrote:<br>
<br>
> Mechanisms should emerge on the basis of concrete needs and identified gaps. The first thing you have to do is to define the issues which have no existing natural home. Many public policy related Internet issues have a natural home. There are about 50 governmental and non-governmental global organisations dealing with various Internet related issues: From UN bodies like the Human Rights Concil to the I*Organisations. To find out what the missing link is and where we have a gap (or a malfunction) we need first of all something like a Multistakeholder Internet Governance Clearing House (I have called this MIPOG / Multistakeholder Internet Policy Group). If a stakeholder, including a national government, has a problem, it could go to MIPOG with a request and MIPOG would recommend how to move forward by delegating the request to an existing mechanism or by launching a (multistakeholder) process in a bottom up, inclusive, open and transparent way to develop policies (as an RFC) which could, if needed, also include the launch of new multistakeholder mechanisms.<br>
<br>
That is also essentially what the submission posted through Best Bits calls for:<br>
<br>
<a href="http://bestbits.net/netmundial-roadmap/" target="_blank">http://bestbits.net/netmundial-roadmap/</a><br>
<br>
--<br>
Jeremy Malcolm PhD LLB (Hons) B Com<br>
Internet lawyer, ICT policy advocate, geek<br>
host -t NAPTR <a href="http://5.9.8.5.2.8.2.2.1.0.6.e164.org/" target="_blank">5.9.8.5.2.8.2.2.1.0.6.e164.org</a>|awk -F! '{print $3}'<br>
<br>
WARNING: This email has not been encrypted. You are strongly recommended to enable encryption at your end. For instructions, see <a href="http://jere.my/l/pgp" target="_blank">http://jere.my/l/pgp</a>.<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>- - - - - - - - - - - - - - - - - - - - - - - - - - -<br> Dr. Alejandro Pisanty<br>Facultad de Química UNAM<br>Av. Universidad 3000, 04510 Mexico DF Mexico<br>
+52-1-5541444475 FROM ABROAD<br>+525541444475 DESDE MÉXICO SMS +525541444475<br>Blog: <a href="http://pisanty.blogspot.com/" target="_blank">http://pisanty.blogspot.com</a><br>LinkedIn: <a href="http://www.linkedin.com/in/pisanty" target="_blank">http://www.linkedin.com/in/pisanty</a><br>
Unete al grupo UNAM en LinkedIn, <a href="http://www.linkedin.com/e/gis/22285/4A106C0C8614" target="_blank">http://www.linkedin.com/e/gis/22285/4A106C0C8614</a><br>Twitter: <a href="http://twitter.com/apisanty" target="_blank">http://twitter.com/apisanty</a><br>
---->> Unete a ISOC Mexico, <a href="http://www.isoc.org/" target="_blank">http://www.isoc.org</a><br>. . . . . . . . . . . . . . . .
</div>
_______________________________________________<br>discuss mailing list<br><a href="mailto:discuss@1net.org">discuss@1net.org</a><br>http://1net-mail.1net.org/mailman/listinfo/discuss</blockquote></div><br></div></div></body></html>