<div dir="ltr"><cclist trimmed><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Mar 22, 2014 at 6:33 AM, Jefsey <span dir="ltr"><<a href="mailto:jefsey@jefsey.com" target="_blank">jefsey@jefsey.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">At 09:58 22/03/2014, David Cake wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would very much agree with Greg that Parminder's scenario of a single entity (or even a single stakeholder group, or organised cabal across a wide range of stakeholders) taking control of the ICANN board is extremely farfetched, a matter for conspiracy theory novels not a genuine worry. It is a scenario that does not plausibly survive even a casual examination of how board members are selected.<br>
<br>
There is only one likely scenario of all ICANN board members having their decision influenced by the same entity - and that entity is ICANN itself. While an oversight mechanism should function in such a way as to guard against a board that was all somehow controlled by a commercial entity willing to patiently infiltrate and suborn a range of ICANN processes, it should be focussed on the more likely issue that ICANN board will take decisions that are in the interests of ICANN itself, rather than the community it serves.<br>
</blockquote>
<br></div>
David, McTim,<br></blockquote><div><br></div><div><br></div><div>Why am I involved in this thread?</div><div><br></div><div>I've not commented at all since the subject line was changed and we went down this particular rathole.</div>
<div><br></div><div>Leave me out of this nonsense please!�</div><div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
let get real please. The far farfetched scenario is the one we are living with for 31 years and the majority of the world's multititude wants now to get rid off. The single entity has a name and reasons clearly explained in <a href="http://www.eisenhower.archives.gov/research/online_documents/farewell_address/1961_01_17_Press_Release.pdf" target="_blank">http://www.eisenhower.<u></u>archives.gov/research/online_<u></u>documents/farewell_address/<u></u>1961_01_17_Press_Release.pdf</a>. 53 years ago. The change is that this single entity was, in spite of RFC 3869 able to make RFC 6852 produced and obtained the Montevideo statement.<br>
<br>
However, what has changed since 1961, due to the internet, is that the 1961 warning is no more sent to the fellow Americans, but to the Multitude. And that the Multitude has a more powerfull capacity for peace, and also for war, than a single people, however great it can be. �The question is simple enough: will the whole internet ordinarily become de facto under the sole US law jurisdiction as the NTIA statement leads to. Followed by a cecession (cyber)war.<br>
<br>
Let get real please. IG is not only a legal or technical issue, it is first a international political affair. We all know that the US are cyberdestructible. This list does not include many citizens of the Dubai majority (<a href="https://www.techdirt.com/articles/20121214/14133321389/who-signed-itu-wcit-treaty-who-didnt.shtml" target="_blank">https://www.techdirt.com/<u></u>articles/20121214/14133321389/<u></u>who-signed-itu-wcit-treaty-<u></u>who-didnt.shtml</a>). <br>
<br>
Sao Paulo must not be a new Munich.<br>
<br>
jfc<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
______________________________<u></u>_________________<br>
discuss mailing list<br>
<a href="mailto:discuss@1net.org" target="_blank">discuss@1net.org</a><br>
<a href="http://1net-mail.1net.org/mailman/listinfo/discuss" target="_blank">http://1net-mail.1net.org/<u></u>mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Cheers,<br><br>McTim<br>"A name indicates what we seek. An address indicates where it is. A route indicates how we get there."� Jon Postel
</div></div>