<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: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 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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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]-->
</head>
<body lang="DE-CH" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Good idea. Many thanks, Greg!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Kind regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Jorge
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Greg Shatan [mailto:gregshatanipc@gmail.com]
<br>
<b>Gesendet:</b> Dienstag, 23. August 2016 20:21<br>
<b>An:</b> Cancio Jorge BAKOM <Jorge.Cancio@bakom.admin.ch><br>
<b>Cc:</b> Karen Mulberry <karen.mulberry@icann.org>; ws2-jurisdiction@icann.org; Thomas Rickert <thomas@rickert.net>; acct-staff@icann.org<br>
<b>Betreff:</b> Re: [Ws2-jurisdiction] Staff paper on jurisdiction posted<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">Jorge,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">We will copy the staff paper and use that second instance as an editable document for our work.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">Greg<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Aug 23, 2016 at 12:41 PM, <<a href="mailto:Jorge.Cancio@bakom.admin.ch" target="_blank">Jorge.Cancio@bakom.admin.ch</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Thanks for this info, Karen.<br>
<br>
Perhaps if the doc is put to edit/comment modus, we may benefit from it as a basis.<br>
<br>
best<br>
<br>
Jorge<br>
<br>
Von meinem iPhone gesendet<br>
<br>
Am 23.08.2016 um 18:32 schrieb Karen Mulberry <<a href="mailto:karen.mulberry@icann.org">karen.mulberry@icann.org</a><mailto:<a href="mailto:karen.mulberry@icann.org">karen.mulberry@icann.org</a>>>:<br>
<br>
Jorge,<br>
<br>
The Subgroup is free to use the information as it wishes, the intention was to provide some background from WS1 discussions and references to the subgroup as it starts its work.<br>
<br>
Karen Mulberry<br>
Multistakeholder Strategy and Strategic Initiatives<br>
ICANN<br>
<br>
<br>
<br>
From: "<a href="mailto:Jorge.Cancio@bakom.admin.ch">Jorge.Cancio@bakom.admin.ch</a><mailto:<a href="mailto:Jorge.Cancio@bakom.admin.ch">Jorge.Cancio@bakom.admin.ch</a>>" <<a href="mailto:Jorge.Cancio@bakom.admin.ch">Jorge.Cancio@bakom.admin.ch</a><mailto:<a href="mailto:Jorge.Cancio@bakom.admin.ch">Jorge.Cancio@bakom.admin.ch</a>>><br>
Date: Tuesday, August 23, 2016 at 10:22 AM<br>
To: Karen Mulberry <<a href="mailto:karen.mulberry@icann.org">karen.mulberry@icann.org</a><mailto:<a href="mailto:karen.mulberry@icann.org">karen.mulberry@icann.org</a>>>, "<a href="mailto:ws2-jurisdiction@icann.org">ws2-jurisdiction@icann.org</a><mailto:<a href="mailto:ws2-jurisdiction@icann.org">ws2-jurisdiction@icann.org</a>>"
<<a href="mailto:ws2-jurisdiction@icann.org">ws2-jurisdiction@icann.org</a><mailto:<a href="mailto:ws2-jurisdiction@icann.org">ws2-jurisdiction@icann.org</a>>><br>
Cc: ACCT-Staff <<a href="mailto:acct-staff@icann.org">acct-staff@icann.org</a><mailto:<a href="mailto:acct-staff@icann.org">acct-staff@icann.org</a>>>, "Thomas Rickert (<a href="mailto:thomas@rickert.net">thomas@rickert.net</a><mailto:<a href="mailto:thomas@rickert.net">thomas@rickert.net</a>>)"
<<a href="mailto:thomas@rickert.net">thomas@rickert.net</a><mailto:<a href="mailto:thomas@rickert.net">thomas@rickert.net</a>>><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Subject: AW: Staff paper on jurisdiction posted<br>
<br>
Thanks for this information.<br>
<br>
I wonder whether we are allowed to make comments to the staff document. A change/edit modus would probably be helpful.<br>
<br>
As a general remark, I feel that staff comments/opinions should be clearly labeled as such and distinguished from what was agreed in the ws1 paper (i.e. Annex 12), where we said basically the following:<br>
<br>
In the summary (points 2 and 5)<br>
<br>
“Addressing jurisdiction-related questions, namely: “Can ICANN’s accountability be<br>
enhanced depending on the laws applicable to its actions?” The CCWG-Accountability<br>
anticipates focusing on the question of applicable law for contracts and dispute<br>
settlements.“<br>
<br>
And in the “topic development” (starting at point 25):<br>
<br>
“25 Jurisdiction<br>
26 Jurisdiction directly influences the way ICANN’s accountability processes are structured and<br>
operationalized. The fact that ICANN is incorporated under the laws of the U.S. State of<br>
California grants the corporation certain rights and implies the existence of certain accountability<br>
mechanisms. It also imposes some limits with respect to the accountability mechanisms it can<br>
adopt.<br>
27 The topic of jurisdiction is, as a consequence, very relevant for the CCWG-Accountability.<br>
ICANN is a nonprofit public benefit corporation incorporated in California and subject to<br>
applicable California state laws, applicable U.S. federal laws and both state and federal court<br>
jurisdiction. ICANN is subject to a provision in paragraph eight1 of the Affirmation of<br>
Commitments, signed in 2009 between ICANN and the U.S. Government.<br>
28 ICANN’s Bylaws (Article XVIII) also state that its principal offices shall be in California.<br>
29 The CCWG-Accountability has acknowledged that jurisdiction is a multi-layered issue and has<br>
identified the following "layers”:<br>
· Place and jurisdiction of incorporation and operations, including governance of internal<br>
affairs, tax system, human resources, etc.<br>
· Jurisdiction of places of physical presence.<br>
· Governing law for contracts with registrars and registries and the ability to sue and be<br>
sued in a specific jurisdiction about contractual relationships.<br>
· Ability to sue and be sued in a specific jurisdiction for action or inaction of staff and for<br>
redress and review of Board action or inaction, including as relates to IRP outcomes and<br>
other accountability and transparency issues, including the Affirmation of Commitments.<br>
· Relationships with the national jurisdictions for particular domestic issues (ccTLDs<br>
managers, protected names either for international institutions or country and other<br>
geographic names, national security, etc.), privacy, freedom of expression.<br>
· Meeting NTIA requirements.<br>
30 At this point in the CCWG-Accountability’s work, the main issues that need to be investigated<br>
within Work Stream 2 relate to the influence that ICANN´s existing jurisdiction may have on the<br>
actual operation of policies and accountability mechanisms. This refers primarily to the process<br>
for the settlement of disputes within ICANN, involving the choice of jurisdiction and of the<br>
applicable laws, but not necessarily the location where ICANN is incorporated:<br>
· Consideration of jurisdiction in Work Stream 2 will focus on the settlement of dispute<br>
jurisdiction issues and include:<br>
o Confirming and assessing the gap analysis, clarifying all concerns regarding the<br>
multi-layer jurisdiction issue.<br>
o Identifying potential alternatives and benchmarking their ability to match all<br>
CCWG-Accountability requirements using the current framework.<br>
o Consider potential Work Stream 2 recommendations based on the conclusions of<br>
this analysis.<br>
31 A specific Subgroup of the CCWG-Accountability will be formed to undertake this work.”<br>
<br>
As I commented also in another subgroup, I feel that we should start exactly where we left the different issues in ws1 (i.e. the final report), and not try to reword, selectively quote and/or reorder what was decided then.<br>
<br>
Hope this is helpful<br>
<br>
Regards<br>
<br>
Jorge<br>
<br>
<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">Von: <a href="mailto:ws2-jurisdiction-bounces@icann.org">ws2-jurisdiction-bounces@icann.org</a><mailto:<a href="mailto:ws2-jurisdiction-bounces@icann.org">ws2-jurisdiction-bounces@icann.org</a>> [mailto:<a href="mailto:ws2-jurisdiction-bounces@icann.org">ws2-jurisdiction-bounces@icann.org</a>]
Im Auftrag von Karen Mulberry<br>
Gesendet: Dienstag, 23. August 2016 17:56<br>
An: <a href="mailto:ws2-jurisdiction@icann.org">ws2-jurisdiction@icann.org</a><mailto:<a href="mailto:ws2-jurisdiction@icann.org">ws2-jurisdiction@icann.org</a>><br>
Cc: ACCT-Staff <<a href="mailto:acct-staff@icann.org">acct-staff@icann.org</a><mailto:<a href="mailto:acct-staff@icann.org">acct-staff@icann.org</a>>>; Thomas Rickert (<a href="mailto:thomas@rickert.net">thomas@rickert.net</a><mailto:<a href="mailto:thomas@rickert.net">thomas@rickert.net</a>>)
<<a href="mailto:thomas@rickert.net">thomas@rickert.net</a><mailto:<a href="mailto:thomas@rickert.net">thomas@rickert.net</a>>><br>
Betreff: [Ws2-jurisdiction] Staff paper on jurisdiction posted<br>
<br>
I wanted to let you know that the staff paper on Jurisdiction has been posted at <a href="https://community.icann.org/x/khWOAw" target="_blank">https://community.icann.org/x/khWOAw</a><br>
<br>
Karen Mulberry<br>
Multistakeholder Strategy and Strategic Initiatives<br>
ICANN<br>
<br>
<br>
_______________________________________________<br>
Ws2-jurisdiction mailing list<br>
<a href="mailto:Ws2-jurisdiction@icann.org">Ws2-jurisdiction@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-jurisdiction" target="_blank">https://mm.icann.org/mailman/listinfo/ws2-jurisdiction</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>