<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On Thursday 23 June 2016 12:44 AM, Mueller, Milton L wrote:<br>
<blockquote
cite="mid:BL2PR07MB2404AF77AF152B248ED73058A12C0@BL2PR07MB2404.namprd07.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in
0in 0in 4.0pt">
<div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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.
</span></p>
</div>
</div>
</div>
</div>
</blockquote>
<br>
<font face="Verdana">One proposal that I made recently to the ISOC
and Just Net Coalition lists was precisely to have a clear
statement of and criteria for 'undue interference' from US gov/
state in ICANN's policy making remit defined and inserted in ICANN
bylaws. The moment the conditions of these criteria are met, first
a process of change of physical location and therefore
jurisdiction of the authoritative root file sets in. For this a
backup physical as well legal (PTI) system would already be ready
in another country (in my argument, I used the possibility of
Singapore, since it has an existing ICANN office) and when the
criteria are deemed to have been met, a switch over to the backup
system gets made right away... There of course would be
significant technical and legal issues to be taken care of for
keeping the backup ready to be switched on with minimum
disruption, but that is what is required to be done. This system
should technically and legally be already in place, and fully
tested for a switch over. <br>
<br>
The biggest advantage of such a backup is that, like any good
check and balance system, it is extremely (repeat, extremly)
unlikely to ever need to get kicked in. It simply acts as a
deterrent. For instance, any court (or other US state agency)
taking cognizance of an issue whose judicial resolution implicates
ICANN global policy remit would be made aware of the fact of this
'backup' system and ICANN's obligation to take resort to it, the
moment any decision of the US state causes incursion on ICANN
global policy authority. The chances are, the relevant court, or
any other US state agency, will take the hint.<br>
<br>
Yes, the US state can force the ICANN board to not take the backup
route but that problem, it faced, too can be solved by an
automatic shift to a back ICANN already registered, say in
Singapore, which automatically takes up the ICANN policy authority
(and thus becomes the real ICANN) the moment the said criteria are
met. The same ICANN board now meets in Singapore as and under the
Singapore registered ICANN legal entity, and things take on from
there... (And with the shift, say to Singapore, another backup in
another country gets made ready.......)<br>
<br>
The proposal was extensively presented to the ISOC list last
month. There may be more elements that I missed stating above,
leaving some gaps. Rushing out for a meeting... Will add later
on..... parminder </font><br>
<br>
<br>
<br>
<br>
<blockquote
cite="mid:BL2PR07MB2404AF77AF152B248ED73058A12C0@BL2PR07MB2404.namprd07.prod.outlook.com"
type="cite">
<div class="WordSection1">
<div style="border:none;border-left:solid blue 1.5pt;padding:0in
0in 0in 4.0pt">
<div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dr.
Milton L. Mueller<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Professor,
School of Public Policy<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Georgia
Institute of Technology<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>