<p dir="ltr">Hi Rubens</p>
<p dir="ltr">I think the interference in .ir and Syria case is quite different from .africa. , .In .ir case the claimant had a judgment against iran which it had obtained through the us courts relying on US laws and wanted to enforce the judgement through attaching .ir to the claimant. I call that interference. In .africa two competing organizations have a dispute over the delegation of .africa. I am not sure if we can compare the two.</p>
<div class="gmail_quote">On 22 Jun 2016 22:14, "Rubens Kuhl" <<a href="mailto:rubensk@nic.br" target="_blank">rubensk@nic.br</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Phil,<br>
<br>
I can´t fully follow your segmentation<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I’ll start that discussion by stating that it would likely include interference in ICANN’s policymaking process (outside of advocacy within the GAC) or trying to block or compel a change in the root zone, through methods that are inconsistent with the Bylaws.<br>
</blockquote>
<br>
Agree<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I don’t think it should include private litigation brought against ICANN and heard in state or federal court; or law enforcement actions, such as bringing an antitrust action if there is an allegation of illicit pricing decisions,<br>
</blockquote>
<br>
why not? Who is going to hear the case set liabilities and eventually compensation????<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
or criminal charges against an ICANN employee for embezzlement, etc.<br>
</blockquote>
<br>
Agree<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
Philip S. Corwin, Founding Principal<br>
Virtualaw LLC<br>
1155 F Street, NW<br>
Suite 1050<br>
Washington, DC 20004<br>
202-559-8597/Direct<br>
202-559-8750/Fax<br>
202-255-6172/Cell<br>
<br>
Twitter: @VlawDC<br>
<br>
"Luck is the residue of design" -- Branch Rickey<br>
<br>
From: <a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a> [mailto:<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>] On Behalf Of Mueller, Milton L<br>
Sent: Wednesday, June 22, 2016 3:15 PM<br>
To: Guru Acharya; Roelof Meijer<br>
Cc: <a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a><br>
Subject: [CCWG-ACCT] premature jurisdiction debates<br>
<br>
<br>
<br>
In the reflexive approach, you would ask "what are the institutional mechanisms or procedures to ensure that jurisdiction issue can be addressed in an adverse situation where the US jurisdiction is longer tenable, however rare it may it?" In the absolute rarest of rare cases that the US legislature or judiciary try to interfere with community decisions (the black swan scenario), how would ICANN ensure that this interference is contained/minimised? What are the institutional mechanisms or procedures for addressing the situation where the US (or any other) jurisdiction is no longer hospitable/ideal for the ICANN policymaking or IANA functions? These are the questions that we should be asking in the WS2 on jurisdiction.<br>
<br>
MM: I think this is a good point. Even advocates of US jurisdiction or those who, like me, think there is just no better alternative and that the disruption and risks caused by a change are not worth the uncertain improvements, can easily agree that there should be procedures or plans for how to respond to interference by the U.S. government.<br>
<br>
<br>
Dr. Milton L. Mueller<br>
Professor, School of Public Policy<br>
Georgia Institute of Technology<br>
<br>
<br>
<br>
________________________________<br>
No virus found in this message.<br>
Checked by AVG - <a href="http://www.avg.com" rel="noreferrer" target="_blank">www.avg.com</a><<a href="http://www.avg.com" rel="noreferrer" target="_blank">http://www.avg.com</a>><br>
Version: 2016.0.7497 / Virus Database: 4613/12467 - Release Date: 06/21/16<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</blockquote>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</blockquote></div>