<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=us-ascii">
<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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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;}
/* List Definitions */
@list l0
{mso-list-id:253587160;
mso-list-type:hybrid;
mso-list-template-ids:-2133983226 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">While I did not volunteer to work on analyzing which Ruggie Principles to incorporate into an ICANN respect-for-HR bylaw, I do want to help in that work and so offer these comments.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">My primary concern is that we stay within the scope of the Bylaw we are interpreting (Bylaw Section 1.2(b)(viii)) irrespective of which HR compilation we are considering and despite several calls on list to be expansive. I recognize the
reason and passion of others who might want us to be bold, but I respectfully disagree and believe we must remain strictly true to the Bylaw provision.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">In my personal view, that means, partially paraphrasing the Bylaw, staying within the scope of ICANN’s mission and other Core Values and concerning ourselves strictly with internationally recognized human rights as required by applicable
law. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">How that might affect consideration of the Ruggie Principles, IMO, would generally involve these points:<o:p></o:p></p>
<p class="MsoListParagraphCxSpFirst"> <o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Placing within the FoI an overarching statement regarding whichever, if any, of the Ruggie Principles sections we choose to recognize that to the extent they might conflict with ICANN’s mission and other Core Values then the mission
and other core values take precedence. I think such a statement would be applicable with respect to any other internationally recognized compilation of HR we might choose to cite.
<o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle"> <o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Under the General Principles, I think that subsection (b) (and similarly subsection 23.(a) under Corporate Responsibility) gets it exactly right with respect to business enterprises (“required to comply with all applicable laws and to
respect human rights”), and that subsection (c) (“need for rights and obligations to be matched to appropriate and effective remedies when breached”) would apply to ICANN insofar as remedies are available at law.
<o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle"> <o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>It seems that no duties that States are meant to observe under Section I as well as subsections 25 – 27 of Section III should apply to ICANN.<o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle"> <o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Under Section II on corporate respect for HR, commentary under paragraph 12 makes a point that is consistent with the new Bylaw (“The responsibility of business enterprises to respect human rights is distinct from issues of legal liability
and enforcement, which remain defined largely by national law provisions in relevant jurisdictions”); but makes it hard to understand the extent of “internationally recognized” HR – is it the minimum in paragraph 12 or the more broad language in the commentary.
It will be good to hear from Prof. Ruggie – and also from Paul Twomey when he is again available.
<o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle"> <o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The provisions in Section II on Corporate Responsibility make the overarching limitation mentioned in #1 above very important as some of these provisions could be taken to require ICANN to go beyond its mission (e.g., subsection 13.(b)
which could require ICANN to seek “ … to prevent or mitigate adverse human rights impacts that are directly linked to [its] operations … even if [it has] not contributed to those impacts.”) I think we may need to go through each of these in detail on the calls
if we wish to adopt them. <o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle"> <o:p></o:p></p>
<p class="MsoListParagraphCxSpLast" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Finally, with respect to grievance mechanisms in subsection 28 and beyond, I believe we will need to tailor any such mechanisms to fit within our existing mechanisms of Ombudsman, Request for Reconsideration, and IRP as they may be modified
in WS2 and decide the applicability of each level to HR. <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>
</body>
</html>