<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>+ 1 David and well said. <br>
</p>
<p>Matthew<br>
</p>
<br>
<div class="moz-cite-prefix">On 07/10/2016 14:10, McAuley, David
wrote:<br>
</div>
<blockquote
cite="mid:35A914B1BE398440838C7AFFD79D34A201ED4381@BRN1WNEXMBX01.vcorp.ad.vrsn.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@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: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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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">Coming out of last week’s sub-team call
Niels asked if I would write down my understanding of the term
“applicable law” that appears in Bylaw (Core Value)
1.2(b)(viii). This is the Bylaw for which we are endeavoring
to create a Framework of Interpretation.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The term “applicable law” appears in two of
this Bylaw’s three sentences and constitutes, in my opinion,
an important limitation to ICANN’s undertaking.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My understanding of the concept of
applicable law refers to that body of law that binds ICANN at
any given time and in any given circumstance. It could consist
of statutes, rules, regulations and the like, as well as
decisional orders/rulings of courts having appropriate
jurisdiction, that take effect through the power of a
legitimate governmental entity.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It is a changeable concept inasmuch as
laws, regulations, etc. change over time. It can be fairly
long-lasting, such as California corporate-governance rules
impacting ICANN, or it can be fairly short-term in effect: if
ICANN chooses to organize a meeting of its board, staff and
community in Hyderabad then the board, staff, and community
must observe Indian travel regulations affecting visitors.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Applicable law can work disparate impacts
on ICANN around the globe: for example, if ICANN employs
personnel in Singapore, Turkey, Uruguay, Belgium, etc. then it
must observe appropriate (and potentially conflicting)
personnel laws in those various places. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Applicable law is thus be a large body of
law that eludes our ability to catalogue, but it is
ascertainable in the context of a specific question or issue.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That is how I personally understand the
term – it might make sense to ask the ICANN legal department
to weigh in on this given the importance of the term to ICANN
in this Bylaw.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">But I stressed the importance of this one
limitation (among others) on our call because it appears to be
central to this Bylaw. It exists and is repeated, it cannot be
ignored or written away. And if we were to interpret this
Bylaw in a manner requiring ICANN to respect rights beyond
those found in applicable law we would, in effect, be asking
ICANN to write law – to go well beyond its expertise. For an
organization with such a limited technical role that would be
a mistake, in my opinion.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David McAuley<o:p></o:p></p>
<p class="MsoNormal">International Policy Manager<o:p></o:p></p>
<p class="MsoNormal">Verisign Inc.<o:p></o:p></p>
<p class="MsoNormal">703-948-4154<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ws2-hr mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ws2-hr@icann.org">Ws2-hr@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/ws2-hr">https://mm.icann.org/mailman/listinfo/ws2-hr</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--------------
Matthew Shears
Global Internet Policy and Human Rights
Center for Democracy & Technology (CDT)
+ 44 771 2472987</pre>
</body>
</html>