<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Texte brut Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.TextebrutCar
{mso-style-name:"Texte brut Car";
mso-style-priority:99;
mso-style-link:"Texte brut";
font-family:Consolas;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
p.PlainText, li.PlainText, div.PlainText
{mso-style-name:"Plain Text";
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
p.BalloonText, li.BalloonText, div.BalloonText
{mso-style-name:"Balloon Text";
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:568229265;
mso-list-type:hybrid;
mso-list-template-ids:-335375538 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:38.25pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:74.25pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:110.25pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:146.25pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:182.25pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:218.25pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:254.25pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:290.25pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:326.25pt;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</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]-->
</head>
<body lang=FR link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Phil,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I also was watching
the senate hearing, and confirm that Fadi said that ICANN would remain subject
to US jurisdiction. I also confirm that this is a very important point.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>It is important
because the NTIA announcement of the stewardship transition calmed very much people
who were always complaining that it is unfair that a single country control the
Internet, a global network. Now that we have this achievement, it would be a
pity to loose it because we want to put in our bylaws that ICANN will remain
acting under the US jurisdiction.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I know and agree that
the US jurisdiction is one of the best for the not for profit corporation. I
don’t say that we need to move ICANN to another jurisdiction, but I think we
don’t have to make it a condition.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>We need a stable and
predictable legal environment, and we also need to build trust and make people
stop complaining. So being diplomatic in our work is really necessary for a
successful and sustainable transition.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#17365D'>--------------------------------------------------------------------------------<o:p></o:p></span></p>
<p class=MsoNormal><b><span lang=EN-US style='color:#17365D'>Tijani BEN JEMAA<o:p></o:p></span></b></p>
<p class=MsoNormal><span lang=EN-US style='color:#17365D'>Executive Director<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#17365D'>Mediterranean
Federation of Internet Associations </span><span lang=EN-US style='font-size:
12.0pt;color:#17365D'>(<b>FMAI</b>)</span><span lang=EN-US style='font-size:
13.0pt;color:#17365D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#17365D'>Phone: + 216 41 649 605<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#17365D'>Mobile: + 216 98 330 114<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#17365D'>Fax: + 216 70 853 376<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#17365D'>--------------------------------------------------------------------------------<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span
style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De :</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
accountability-cross-community-bounces@icann.org
[mailto:accountability-cross-community-bounces@icann.org] <b>De la part de</b>
Phil Corwin<br>
<b>Envoyé :</b> mercredi 4 mars 2015 23:29<br>
<b>À :</b> Pedro Ivo Ferraz da Silva; 'Steve DelBianco'; Accountability
Cross Community<br>
<b>Cc :</b> ACCT-Staff; ccwg-accountability4@icann.org<br>
<b>Objet :</b> Re: [CCWG-ACCT] RES: [ST-WP] Additional Stress Tests to
discuss<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText><span lang=EN-US>Pedro:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>This is a very important point. I was in
the room at the Senate Commerce hearing last week, and also at another event at
the US Chamber of Commerce two days later. At both events Fadi stressed that
ICANN would remain subject to US “jurisdiction" post-transition, not just
maintain its nominal HQ in the US. As you correctly point out, there is a big
“difference between "headquarter location" and "legal
presence/legal jurisdiction".<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Choice of legal jurisdiction is a very
important point for multiple reasons, among them:<o:p></o:p></span></p>
<p class=MsoPlainText style='margin-left:38.25pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo2'><![if !supportLists]><span lang=EN-US
style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span lang=EN-US>Stable and
predictable legal regime for contracted parties. As all of ICANN’s authority
vis-à-vis registries and registrars is based on its contracts with them,
reliable and predictable contract enforcement is a key consideration. The
US is generally regarded as having one of the best legal systems in the world.<o:p></o:p></span></p>
<p class=MsoPlainText style='margin-left:38.25pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo2'><![if !supportLists]><span lang=EN-US
style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span lang=EN-US>Design of
both the IANA and ICANN accountability measures. Both the CWG and the CCWG are
going to engage independent legal counsel to advise them on the design of
accountability measures within the context of California public benefits
corporation law. If the legal context changes those accountability measures may
not fit properly within it; they may become less effective or even unworkable.<o:p></o:p></span></p>
<p class=MsoPlainText style='margin-left:38.25pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo2'><![if !supportLists]><span lang=EN-US
style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span lang=EN-US>Security
concerns. As a US corporation, ICANN is forbidden by OFAC regulations form
engaging in any transactions with entities classified as criminal or terrorist.
This consideration is particularly potent for the Administration and Congress.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>As to your point that “The community
should be given the ability to decide, in the future, which jurisdiction better
serves the purpose of ICANN acting in accordance to the global public
interest.” , that is not necessarily foreclosed, at some future date, depending
on what mechanisms are provided for Bylaws amendments. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>But for the immediate future those
engaged in this transition exercise should have some idea whether ICANN’s
continued legal existence as a non-profit California corporation is acceptable
to other nations or whether it will become the new “irritant” (as described by
Secretary Strickling) that replaces the IANA counterparty status as cause for
complaint and basis for calls for further alterations in its structure and
status.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>This is central to the issue of whether
the transition we are designing will be stable for the foreseeable future or
will just be a short-term transitional stage from which new initiatives for
change are launched not long after the ink dries.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Regards,<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Philip<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Philip S. Corwin, Founding Principal<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Virtualaw LLC<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>1155 F Street, NW<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Suite 1050<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Washington, DC 20004<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>202-559-8597/Direct<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>202-559-8750/Fax<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>202-255-6172/cell<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Twitter: @VlawDC<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US> <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>"Luck is the residue of
design" -- Branch Rickey<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>-----Original Message-----<br>
From: accountability-cross-community-bounces@icann.org
[mailto:accountability-cross-community-bounces@icann.org] On Behalf Of Pedro
Ivo Ferraz da Silva<br>
Sent: Wednesday, March 04, 2015 4:55 PM<br>
To: 'Steve DelBianco'; Accountability Cross Community<br>
Cc: ACCT-Staff; ccwg-accountability4@icann.org<br>
Subject: [CCWG-ACCT] RES: [ST-WP] Additional Stress Tests to discuss<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Dear Steve,<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Thank you very much for the update on
the Stress Tests.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>With respect to ST #15, it is very
valuable, but I think we should be very cautious about proposed measures. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>The following option makes sense and
should be further debated: " If ICANN board voted to vacate a legal
presence, the community veto could enable reversal of that decision".<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>However, we anticipate objections to the
alternative solution below: <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>"One proposed measure is to import
AoC provisions into the ICANN bylaws, and dispense with the bilateral AoC with
NTIA. Bylaws would be amended to include AoC commitments 8, requiring it
to maintain legal presence in the US, where it is subject to legal redress by
any aggrieved party."<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Paragraph 8 of the AoC requires US legal
presence most probably due to the present scenario where the US government
(i.e.NTIA) is the steward of the IANA functions. Once that link is no longer
there, and especially because that stewardship is being inherited by the global
multistakeholder community (stressing the word "global") a legal
presence in the US (or in any other specific country) should not be etched in
stone. The community should be given the ability to decide, in the future,
which jurisdiction better serves the purpose of ICANN acting in accordance to
the global public interest.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>During yesterday's call, some colleagues
mentioned ICANN CEO's Testimony in the American Senate last week. What he
stated was literally: " Further, ICANN has its global headquarters in the
United States, and there are no plans for that to change". Although such a
decision/affirmation may be debatable, it is important, once again, to stress
the difference between "headquarter location" and "legal
presence/legal jurisdiction". Under e.g. an international jurisdiction, an
entity could potentially be headquartered anywhere. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Regards,<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Sec. Pedro Ivo Ferraz da Silva<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Division of Information Society<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Ministry of External Relations - brazil<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>T: + 55 61 2030-6609<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>-----Mensagem original-----<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>De: <a
href="mailto:ccwg-accountability4-bounces@icann.org"><span style='color:windowtext;
text-decoration:none'>ccwg-accountability4-bounces@icann.org</span></a> [<a
href="mailto:ccwg-accountability4-bounces@icann.org"><span style='color:windowtext;
text-decoration:none'>mailto:ccwg-accountability4-bounces@icann.org</span></a>]
Em nome de Steve DelBianco Enviada em: segunda-feira, 2 de março de 2015 23:36<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Para: Accountability Cross Community<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Cc: ACCT-Staff; <a
href="mailto:ccwg-accountability4@icann.org"><span style='color:windowtext;
text-decoration:none'>ccwg-accountability4@icann.org</span></a><o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Assunto: [ST-WP] [CCWG-ACCT] Additional
Stress Tests to discuss<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>For tomorrow’s call, we applied 4 more
of our stress tests against the draft package of proposed accountability
measures. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Stress Tests #1 and 2 (together), #24,
and #15, are shown below and in the attached draft document. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Stress Test:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
#1. Change authority for the IANA Root Zone ceases to function, in part or in
whole. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
#2. Delegation authority for the IANA Root Zone ceases to function, in part or
in whole.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Consequence: interference with existing policy relating to IANA Root Zone
and/or prejudice to the security and stability of one or several TLDs.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Existing Accountability Measures:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Under the present IANA contract, NTIA can revoke ICANN’s authority to perform
IANA functions and re-assign to different entity/entities. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
After NTIA relinquishes the IANA contract, this measure will no longer be
available.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Proposed Accountability Measures:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
The CWG planning the IANA stewardship transition might design mechanisms and
structures that enable separation, such that the IANA functions could be
readily revoked and re-assigned.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
To manage the revocation of IANA functions, the CWG might also propose an
emergency backup provider and procedures, pending re-assignment of the IANA
functions.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Preliminary Conclusions:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
This threat is directly related to the transition of IANA stewardship<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Existing measures would be inadequate after NTIA terminates the IANA contract.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
At this point, CWG’s recommendations are still in development.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>———————————————————<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Stress Test:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
#24. An incoming Chief Executive institutes a “strategic review” that arrives
at a new, extended mission for ICANN. The Board, having just hired the new CEO,
approves the new mission and strategy without community consensus.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Consequence: Community ceases to see ICANN as the community’s own mechanism for
discharging limited technical functions, and views ICANN as an independent, sui
generis entity with its own agenda, not necessarily supported by the community.
Ultimately, community questions why ICANN’s original functions should remain
controlled by a body that has acquired a much broader and less widely supported
mission.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Existing Accountability Measures:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
As long as NTIA controls the IANA contract, ICANN could risk losing IANA
functions if it were to expand scope too broadly. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
The Community has some input in ICANN budgeting and Strat Plan, and could
register objections to plans and spending on extending ICANN’s mission.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
California’s Attorney General has jurisdiction over non-profit entities acting
outside Bylaws or Articles of Incorporation.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Proposed Accountability Measures:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
One proposed measure is empowering the community to veto ICANN’s proposed annual
budget. This measure could block a proposal by ICANN to increase its
expenditure on extending its mission beyond what the community supported.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
If the ICANN board voted to approve the CEO’s plans, one proposed measure would
give the community standing to veto a board decision.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Another proposed measure is empowering the community to challenge a board
decision, referring it to an Independent Review Panel (IRP) with the power to
issue a binding decision. [What would be the standard used
for this review?]<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Preliminary Conclusions:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
This threat is directly related to the transition of IANA stewardship<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Existing measures would be inadequate after NTIA terminates the IANA contract.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Proposed measures in combination are adequate.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>———————————————————<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Stress Test:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
#15. ICANN terminates its legal presence in a nation where Internet users or
domain registrants are seeking legal remedies for ICANN’s failure to enforce
contracts, or other actions. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Consequence: affected parties could be prevented from seeking legal redress for
commissions or omissions by ICANN.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Existing Accountability Measures:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
As long as NTIA controls the IANA contract, ICANN could risk losing IANA
functions if it were to move in order to avoid legal jurisdiction. <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Paragraph 8 of the AoC requires ICANN to remain headquartered in the US, but
the AoC can be terminated by ICANN at any time. As long as NTIA
controls the IANA contract, ICANN feels pressure to maintain the AoC.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Proposed Accountability Measures:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
One proposed measure is to give the community standing to veto a board
decision. If ICANN board voted to vacate a legal presence, the community
veto could enable reversal of that decision.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
One proposed measure is to import AoC provisions into the ICANN bylaws, and
dispense with the bilateral AoC with NTIA. Bylaws would be amended to
include AoC commitments 8, requiring it to maintain legal presence in the US,
where it is subject to legal redress by any aggrieved party.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
If ICANN’s board proposed to amend the AoC provisions added to the bylaws,
another proposed measure would empower the community to veto that proposed
bylaws change.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Preliminary Conclusions:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
This threat is directly related to the transition of IANA stewardship<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Existing measures would be inadequate after NTIA terminates the IANA contract.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>
Proposed measures improve upon existing measures, and may be adequate.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>_______________________________________________<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Accountability-Cross-Community mailing
list <a href="mailto:Accountability-Cross-Community@icann.org"><span
style='color:windowtext;text-decoration:none'>Accountability-Cross-Community@icann.org</span></a><o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><a
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"><span
style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/accountability-cross-community</span></a><o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>-----<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>No virus found in this message.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Checked by AVG - <a
href="http://www.avg.com"><span style='color:windowtext;text-decoration:none'>www.avg.com</span></a><o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Version: 2015.0.5751 / Virus Database:
4299/9218 - Release Date: 03/03/15<o:p></o:p></span></p>
</div>
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="http://www.avast.com/">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection <a href="http://www.avast.com/">Antivirus avast!</a> est active.
</p>
</td>
</tr>
</table>
<br />
</body>
</html>