<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On Sunday 26 June 2016 01:57 PM, Nigel
Roberts wrote:<br>
</div>
<blockquote
cite="mid:39F30270-E5DC-472C-8E0C-B263B1793478@roberts.co.uk"
type="cite">
<pre wrap="">And is generally declaratory in nature.</pre>
</blockquote>
<br>
Generally, but not always. Look at the investor-to-state dispute
settlements system, which provides enforceable means to protect
investors' (individual legal entities and not states) rights. EU <a
href="http://europa.eu/rapid/press-release_IP-15-5651_en.htm">recently
proposed a new Investment Court System</a> for two trade treaties
that it is involved in. The same proposal also seeks movement
towards an International Investment Court in the future. Note both
that this is not declaratory but enforceable international law, and
that it involves the rights and claims of individual entities and
not states. <br>
<br>
No reason why a similar treaty based court cannot be established for
DNS related disputes, issuing enforceable judgements. <br>
<br>
Internet is primarily global, not becuase of a technical necessity
but as a collective value (on the other hand, trade and investment,
the subject of about international enforcible law, are only
secondarily international). We chose Internet to be global. We could
have, and still can, make it national state based. Every country
gets a ccTLD, and all domains names are on them, and necessarily
have a .in, .us, .de, etc at the end. Like every geographical
addresses ends in a country name. <br>
<br>
There will be no global level domain name policy left to be dealt
with in that case. But we did not do it, becuase we value a
'primarily global' Internet. But to have one, in a legitimate way,
we need to be ready to make the necessary innovations in
global/international law as well. We cannot have a global Internet
without effective global/international law. Basically, we cannot
have have a global Internet run by US laws. Period. <br>
<blockquote
cite="mid:39F30270-E5DC-472C-8E0C-B263B1793478@roberts.co.uk"
type="cite">
<pre wrap="">There is if course international private law but ICANN already operates under that.
And international criminal law. Which is irrelevant to us.
Par minder, you may have seen how I challenged another lawyer on this list when he made an unjustified assumption recently.
We say: "what is your authority for that proposition?"
It's what a judge might say.
It means "tell me the rule of law on which you rely "
If as non lawyer you want to join in .. And lawyers do welcome rational submission ..
You should nonetheless expect to be asked this question a LOT.</pre>
</blockquote>
<br>
As I have done above, always happy to answer all questions.
Meanwhile, in good lawyerly tradition :) , why you too also not
answer some of my questions that are key to framing this debate.
Like<br>
<br>
(1) What is ICANN's plan to do if it gets adverse US court
judgements in .xxx and .africa cases (even .ir is still in the
courts)? Is there no plan at all, which would be absolutely
inappropriate for a responsible organisation. Is the plan to just
accept the judgements, and make necessary policy/ operational
changes? If so, the world needs to know NOW, when jurisdiction is
being discussed, and not realise later when the event happens, the
enormity of US courts dictating global DNS policy. To repeat, ICANN
must right away put forward its plan and position in this regard,
which is an absolutely important, actually necessary, thing to know
for those discussing the jurisdiction question as part of work
stream 2. <br>
<br>
(2) These above are existing cases, now with 100s of new gTLDs
issued to every kind of organisation and for every kind of activity,
you are going to get so many more cases in the US courts of the
above kind. What do you plan vis a vis them? Also, please see the
hypothetical case in my last email, if rojadirecta takes
.rojadirecta as a closed gTLD, and after some time, as they did once
earlier through its US based registry, US authorities want to seize
the .rojadirecta, which can now only be done at the root file level,
and for that sends a order to ICANN, what would ICANN do? Again,
necessary to know while we are in middle of jurisdiction decision.<br>
<br>
If ICANN officially (highly preferred), or otherwise at least the
lawyers here involved on the 'keep US jurisdiction' side of the
discussion, can respond to these questions, it would form a good
basis to move forward.<br>
<br>
I am sure lawyers will also oblige the non lawyers, as I answered
your questions promptly :)<br>
<br>
parminder <br>
<br>
<blockquote
cite="mid:39F30270-E5DC-472C-8E0C-B263B1793478@roberts.co.uk"
type="cite">
<pre wrap="">
Sent from my iPhone
</pre>
<blockquote type="cite">
<pre wrap="">On 26 Jun 2016, at 10:00, Dr Eberhard W Lisse <a class="moz-txt-link-rfc2396E" href="mailto:el@lisse.NA"><el@lisse.NA></a> wrote:
Unless I am mistaken, International Law regulates relations between
states and nations and requires treaties between such
states/nations.
el
</pre>
<blockquote type="cite">
<pre wrap="">On 2016-06-26 07:24 , parminder wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Saturday 25 June 2016 09:55 PM, Alberto Soto wrote:
What would result if this text, replacing US law by: Italian
laws? or Belgium laws? Or …laws?
</pre>
</blockquote>
<pre wrap="">
There is something called international law..... Like we are an
international community working on an international issue, there
is also international law.
best, parminder
</pre>
</blockquote>
<pre wrap="">[...]
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
</body>
</html>