<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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
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:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
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.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Thanks for this Anne. The working group’s steadfast refusal to do the work necessary to understand – rather than assume – what the applicable laws are, has been very disheartening. I just don’t think it is a good idea to build work based on willful ignorance rather than information and I remain befuddled at why such a learned crowd seems fully prepared to skip this important step.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Paul<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> ws2-hr-bounces@icann.org [mailto:ws2-hr-bounces@icann.org] <b>On Behalf Of </b>Aikman-Scalese, Anne<br><b>Sent:</b> Wednesday, September 28, 2016 4:55 PM<br><b>To:</b> 'Nigel Roberts' <nigel@channelisles.net>; ws2-hr@icann.org<br><b>Cc:</b> Paul D. McGrady (pmcgrady@winston.com) <pmcgrady@winston.com><br><b>Subject:</b> [Ws2-hr] Applicable Law - that is applicable to ICANN and requires it to protect free expression internally<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoPlainText>Nigel, I have a question about your quote from this e-mail. The quote is:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span style='color:#C00000'>" There is no applicable law, for example, that protects individuals and organisations against breaches of their right to free expression."<o:p></o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>You seem to be saying that on expiration of the IANA contract, ICANN has a lesser duty under applicable law in relation to freedom of expression since it will be " <span style='color:#C00000'>a private company that no longer has any formal connection to the US Government." </span>I see your point in that all the Federal Acquisition Regulation obligations contained in the IANA contract go by the wayside. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>One reason I ask about this is due to the U.S. Labor Law in relation to freedom of speech/expression that I think quite clearly governs ICANN’s employment practices – at least in the U.S. For example, we have a case decided by the U.S. Supreme Court that held that Abercrombie & Fitch could not turn down employment to a woman who wore a hijab to her interview because its dress code called for a “classic East Coast collegiate style”. The Supreme Court held the decision was apparently motivated by a desire to avoid accommodating the young woman’s religious practice. The vote was 8 to 1. So this case, decided in June of 2015, is definitely “applicable law” in relation to ICANN’s business practices and definitely requires ICANN to avoid “breaching” individual rights to freedom of expression. (EEOC v. Abercrombie & Fitch)<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I think this is a discussion that gets to the heart of Paul McGrady’s repeated requests that we focus on the issue of “applicable law”. Where it gets much harder is when we discuss how ICANN may be obligated not because of its role as an employer, but rather because of its role as the Awarder in Chief of registry contracts.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>If anyone is interested in applicable law that governs ICANN employee reasonable accommodation for freedom of expression in the U.S., (not sure about outside the U.S.), the following link may be helpful:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><a href="https://www.eeoc.gov/eeoc/newsroom/wysk/workplace_religious_accommodation.cfm">https://www.eeoc.gov/eeoc/newsroom/wysk/workplace_religious_accommodation.cfm</a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Anne<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Anne E. Aikman-Scalese<o:p></o:p></p><p class=MsoPlainText>Of Counsel<o:p></o:p></p><p class=MsoPlainText>520.629.4428 office<o:p></o:p></p><p class=MsoPlainText>520.879.4725 fax<o:p></o:p></p><p class=MsoPlainText><a href="mailto:AAikman@lrrc.com">AAikman@lrrc.com</a><o:p></o:p></p><p class=MsoPlainText>_______________________________<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Lewis Roca Rothgerber Christie LLP<o:p></o:p></p><p class=MsoPlainText>One South Church Avenue, Suite 700<o:p></o:p></p><p class=MsoPlainText>Tucson, Arizona 85701-1611<o:p></o:p></p><p class=MsoPlainText>lrrc.com<o:p></o:p></p><p class=MsoPlainText>-----Original Message-----<br>From: <a href="mailto:ws2-hr-bounces@icann.org">ws2-hr-bounces@icann.org</a> [<a href="mailto:ws2-hr-bounces@icann.org">mailto:ws2-hr-bounces@icann.org</a>] On Behalf Of Nigel Roberts<br>Sent: Tuesday, September 27, 2016 11:20 PM<br>To: <a href="mailto:ws2-hr@icann.org">ws2-hr@icann.org</a><br>Subject: Re: [Ws2-hr] Proposed agenda meeting September 27 - 19:00 UTC<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Paul is correct.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I also must take issue with Greg. The construction of the by law so as to restrict ICANN to only respect human rights where an applicable DOMESTIC law requires it to, is wrong, and is the exact reason I argued, in the minority, against the phrase.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There is no applicable law,, for example, that protects individuals and organisations against breaches of their right to free expression.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>If there is, tell me what it is, and where I can read and construe it.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>In particular, please tell me the section of that law that makes it applicable to a private company that no longer has any formal connection to the US Government.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On 27/09/16 21:05, Paul Rosenzweig wrote:<o:p></o:p></p><p class=MsoPlainText>> I guess you folks leave me confused. Certainly, all human rights are due to be respected. But if the FoI is to have any use at all, doesn't it have to deal with actual use case scenarios that are applicable to ICANN? There are human rights prohibitions against torture, that ICANN must respect -- but the chances of that particular human right having any relevance to anything that ICANN will ever do is vanishingly small, no? Why would we construct an FoI that is so amorphous that it accommodates that possibility if in doing so we lose adequate guidance for the HR issues that are more likely to be relevant?<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Can we not agree that human rights are universal and indivisible but that some of them are more likely of applicability to ICANN's operations than others? Or is that really so controversial a statement that it can't be made?<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Paul<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Paul Rosenzweig<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:paul.rosenzweig@redbranchconsulting.com"><span style='color:windowtext;text-decoration:none'>paul.rosenzweig@redbranchconsulting.com</span></a><o:p></o:p></p><p class=MsoPlainText>> O: +1 (202) 547-0660<o:p></o:p></p><p class=MsoPlainText>> M: +1 (202) 329-9650<o:p></o:p></p><p class=MsoPlainText>> VOIP: +1 (202) 738-1739<o:p></o:p></p><p class=MsoPlainText>> <a href="http://www.redbranchconsulting.com"><span style='color:windowtext;text-decoration:none'>www.redbranchconsulting.com</span></a><o:p></o:p></p><p class=MsoPlainText>> My PGP Key: <a href="http://redbranchconsulting.com/who-we-are/public-pgp-key/"><span style='color:windowtext;text-decoration:none'>http://redbranchconsulting.com/who-we-are/public-pgp-key/</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> -----Original Message-----<o:p></o:p></p><p class=MsoPlainText>> From: <a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr-bounces@icann.org</span></a> [<a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>mailto:ws2-hr-bounces@icann.org</span></a>] On <o:p></o:p></p><p class=MsoPlainText>> Behalf Of Daniel Appelman<o:p></o:p></p><p class=MsoPlainText>> Sent: Tuesday, September 27, 2016 2:59 PM<o:p></o:p></p><p class=MsoPlainText>> To: Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com"><span style='color:windowtext;text-decoration:none'>AAikman@lrrc.com</span></a>>; 'Bastiaan Goslings' <o:p></o:p></p><p class=MsoPlainText>> <<a href="mailto:bastiaan.goslings@ams-ix.net"><span style='color:windowtext;text-decoration:none'>bastiaan.goslings@ams-ix.net</span></a>>; Greg Shatan <<a href="mailto:gregshatanipc@gmail.com"><span style='color:windowtext;text-decoration:none'>gregshatanipc@gmail.com</span></a>><o:p></o:p></p><p class=MsoPlainText>> Cc: <a href="mailto:ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>> Subject: Re: [Ws2-hr] Proposed agenda meeting September 27 - 19:00 UTC<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Thanks for your thoughts, Anne. I never advocated excluding any human rights from the framework, of course. But none of the comments thus far have convinced me that they are all equally relevant for ICANN.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> -----Original Message-----<o:p></o:p></p><p class=MsoPlainText>> From: Aikman-Scalese, Anne [<a href="mailto:AAikman@lrrc.com"><span style='color:windowtext;text-decoration:none'>mailto:AAikman@lrrc.com</span></a>]<o:p></o:p></p><p class=MsoPlainText>> Sent: Tuesday, September 27, 2016 11:53 AM<o:p></o:p></p><p class=MsoPlainText>> To: Daniel Appelman; 'Bastiaan Goslings'; Greg Shatan<o:p></o:p></p><p class=MsoPlainText>> Cc: <a href="mailto:ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>> Subject: RE: [Ws2-hr] Proposed agenda meeting September 27 - 19:00 UTC<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Dan,<o:p></o:p></p><p class=MsoPlainText>> I think that in the FOI-HR, it would be a mistake to single out which Human Rights we think have to be considered (to the exclusion of others) in ICANN's processes and business relationships. I think the Framework must leave the freedom for ICANN, in its various processes, to consider and balance all international human rights. To exclude some would be dangerous - and just plain wrong, since, a Nigel pointed out in the call I had to miss, there is, in connection with any such human rights evaluation, a balancing act to be performed.<o:p></o:p></p><p class=MsoPlainText>> Anne<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Anne E. Aikman-Scalese<o:p></o:p></p><p class=MsoPlainText>> Of Counsel<o:p></o:p></p><p class=MsoPlainText>> 520.629.4428 office<o:p></o:p></p><p class=MsoPlainText>> 520.879.4725 fax<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:AAikman@lrrc.com"><span style='color:windowtext;text-decoration:none'>AAikman@lrrc.com</span></a><o:p></o:p></p><p class=MsoPlainText>> _______________________________<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Lewis Roca Rothgerber Christie LLP<o:p></o:p></p><p class=MsoPlainText>> One South Church Avenue, Suite 700<o:p></o:p></p><p class=MsoPlainText>> Tucson, Arizona 85701-1611<o:p></o:p></p><p class=MsoPlainText>> lrrc.com<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> -----Original Message-----<o:p></o:p></p><p class=MsoPlainText>> From: Daniel Appelman [<a href="mailto:dappelman@mh-llp.com"><span style='color:windowtext;text-decoration:none'>mailto:dappelman@mh-llp.com</span></a>]<o:p></o:p></p><p class=MsoPlainText>> Sent: Tuesday, September 27, 2016 11:50 AM<o:p></o:p></p><p class=MsoPlainText>> To: Aikman-Scalese, Anne; 'Bastiaan Goslings'; Greg Shatan<o:p></o:p></p><p class=MsoPlainText>> Cc: <a href="mailto:ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>> Subject: RE: [Ws2-hr] Proposed agenda meeting September 27 - 19:00 UTC<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Anne: So does that first statement also mean that in your opinion it is not true that some human rights are more RELEVANT to ICANN's activities and mission than others? And is that the consensus of the WG?<o:p></o:p></p><p class=MsoPlainText>> I do agree with the statements in your second and third paragraphs, btw.<o:p></o:p></p><p class=MsoPlainText>> Dan<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> -----Original Message-----<o:p></o:p></p><p class=MsoPlainText>> From: <a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr-bounces@icann.org</span></a> [<a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>mailto:ws2-hr-bounces@icann.org</span></a>] On <o:p></o:p></p><p class=MsoPlainText>> Behalf Of Aikman-Scalese, Anne<o:p></o:p></p><p class=MsoPlainText>> Sent: Tuesday, September 27, 2016 11:34 AM<o:p></o:p></p><p class=MsoPlainText>> To: 'Bastiaan Goslings'; Greg Shatan<o:p></o:p></p><p class=MsoPlainText>> Cc: <a href="mailto:ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>> Subject: Re: [Ws2-hr] Proposed agenda meeting September 27 - 19:00 UTC<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> It is not true that "some human rights are more important than others". I agree with those who have noted that continued attempts to "cherry-pick" among human rights are inappropriate and not in scope for the task. This is clear from the document stating the conclusions from WS1 and that document was already agreed on by the subteam in a prior meeting.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> I also wish to re-emphasize that the primary role in which ICANN may <o:p></o:p></p><p class=MsoPlainText>> have a positive impact on human rights is in its primary business <o:p></o:p></p><p class=MsoPlainText>> relationships. These are the contractual obligations with registries <o:p></o:p></p><p class=MsoPlainText>> and registrars. Again, these are matters which must ultimately be <o:p></o:p></p><p class=MsoPlainText>> addressed via PDP so in developing an FOI-HR, we must take that into <o:p></o:p></p><p class=MsoPlainText>> account and understand that we are developing an FOI-HR that will be <o:p></o:p></p><p class=MsoPlainText>> applied in the PDP process (as well as other processes within ICANN.)<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> As I understand it, there is no "applicable law" that will require application of the FOI-HR to the PDP process. That would be wholly voluntary. Some may feel this is beyond scope and mission as to what the Bylaw requires. Would like to know others thoughts on this point.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Anne<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Anne E. Aikman-Scalese<o:p></o:p></p><p class=MsoPlainText>> Of Counsel<o:p></o:p></p><p class=MsoPlainText>> 520.629.4428 office<o:p></o:p></p><p class=MsoPlainText>> 520.879.4725 fax<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:AAikman@lrrc.com"><span style='color:windowtext;text-decoration:none'>AAikman@lrrc.com</span></a><o:p></o:p></p><p class=MsoPlainText>> _______________________________<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Lewis Roca Rothgerber Christie LLP<o:p></o:p></p><p class=MsoPlainText>> One South Church Avenue, Suite 700<o:p></o:p></p><p class=MsoPlainText>> Tucson, Arizona 85701-1611<o:p></o:p></p><p class=MsoPlainText>> lrrc.com<o:p></o:p></p><p class=MsoPlainText>> -----Original Message-----<o:p></o:p></p><p class=MsoPlainText>> From: <a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr-bounces@icann.org</span></a> [<a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>mailto:ws2-hr-bounces@icann.org</span></a>] On <o:p></o:p></p><p class=MsoPlainText>> Behalf Of Bastiaan Goslings<o:p></o:p></p><p class=MsoPlainText>> Sent: Tuesday, September 27, 2016 11:20 AM<o:p></o:p></p><p class=MsoPlainText>> To: Greg Shatan<o:p></o:p></p><p class=MsoPlainText>> Cc: <a href="mailto:ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>> Subject: Re: [Ws2-hr] Proposed agenda meeting September 27 - 19:00 UTC<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> I do not think we need to establish _which_ human rights ICANN should respect (more). The way I interpret the core value is that the applicability of (‘internationally recognised') rights is determined by ‘applicable law’. ‘As required’.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Furthermore, the core value does not speak of ‘commit’ or a ‘commitment’ - because it is a core value. Together with the other values, and that could be a balancing act, it ‘should also guide the decisions and actions of ICANN’.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> (The ‘also’ refers to the commitments in section 1.2)<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> -Bastiaan<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>>> On 27 Sep 2016, at 19:56, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com"><span style='color:windowtext;text-decoration:none'>gregshatanipc@gmail.com</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> You seem to assume that the Framework will deal with rights at the granular level. I don't think it needs to or should. The question is "What human rights is ICANN committed to respect?" I don't think the answer should be "Some of them."<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> On Tue, Sep 27, 2016 at 1:50 PM, Daniel Appelman <<a href="mailto:dappelman@mh-llp.com"><span style='color:windowtext;text-decoration:none'>dappelman@mh-llp.com</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText>>> Some human rights are obviously more applicable to ICANN than others. ICANN’s framework should focus on those in particular. If that’s “cherry-picking” then I don’t understand how anyone could object to it. Why would the framework even bother with human rights that are inapplicable to ICANN’s mission and activities? It’s just not logical.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> From: <a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr-bounces@icann.org</span></a> [<a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>mailto:ws2-hr-bounces@icann.org</span></a>] On <o:p></o:p></p><p class=MsoPlainText>>> Behalf Of Greg Shatan<o:p></o:p></p><p class=MsoPlainText>>> Sent: Tuesday, September 27, 2016 10:42 AM<o:p></o:p></p><p class=MsoPlainText>>> To: Schweighofer Erich<o:p></o:p></p><p class=MsoPlainText>>> Cc: <a href="mailto:ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>>> Subject: Re: [Ws2-hr] Proposed agenda meeting September 27 - 19:00 <o:p></o:p></p><p class=MsoPlainText>>> UTC<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> A response on Erich's last point:<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> WS2-HR should focus on the freedom of communication worldwide, subject to usual safeguard clauses + the international human rights treaty obligations.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> This sounds suspiciously like "cherry-picking" (i.e., picking and choosing among human rights obligation), and I am firmly opposed to that. Also while human rights treaty obligations are relevant (and we need to determine what we are referring to as such) they do not bind ICANN, except to the extent they have been adopted and codified by applicable laws. The Bylaw doesn't take us further than that.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> It is not cherry-picking, it is a suggestion which human rights are relevant to be considered. Free communication should be the main concern.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> You are right that human rights treaties formally do not bind ICANN but that sound not good in practice. We have to substitute this by self-commitment, as we do now.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> We've been using the term cherry-picking to mean just that -- picking and choosing, menu-style, from the list of human rights and deciding that some are going to be considered and some won't. Whatever you call it, I'm opposed to it. I'm not opposed to choosing among human rights conventions and instruments; indeed, we must do that. But within, e.g., the UDHR, we should not be picking, we need to take it whole as a document. The extent of ICANN's commitment to human rights is stated in the Bylaw, -- to respect internationally recognized human rights as required by applicable law. This is critical in three ways: (1) ICANN's commitment is one of "respecting" (and not protecting or enforcing) human rights (and we need to define what "respect" means in the context of ICANN, which unfortunately does not align with Ruggie's idea of respect for business enterprises); (2) ICANN must look to "internationally recognized human rights" -- no more and no less; and (3) ICANN's co!<o:p></o:p></p><p class=MsoPlainText>mmitment<o:p></o:p></p><p class=MsoPlainText>i<o:p></o:p></p><p class=MsoPlainText>s limited to what is "required by applicable law." ICANN could go further of course (e.g., it could ensure there are gluten free food options at every ICANN meeting and event), but that is not a Bylaws issue and thus not a Framework of Interpretation issue.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Greg<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> On Tue, Sep 27, 2016 at 12:14 PM, Schweighofer Erich <<a href="mailto:erich.schweighofer@univie.ac.at"><span style='color:windowtext;text-decoration:none'>erich.schweighofer@univie.ac.at</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> My clarifications „inline“. Sorry for quick drafting and being unclear.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Erich Schweighofer<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Von: Greg Shatan [<a href="mailto:gregshatanipc@gmail.com"><span style='color:windowtext;text-decoration:none'>mailto:gregshatanipc@gmail.com</span></a>]<o:p></o:p></p><p class=MsoPlainText>>> Gesendet: Dienstag, 27. September 2016 17:35<o:p></o:p></p><p class=MsoPlainText>>> An: Schweighofer Erich<o:p></o:p></p><p class=MsoPlainText>>> Cc: Niels ten Oever; <a href="mailto:ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>>> Betreff: Re: [Ws2-hr] Proposed agenda meeting September 27 - 19:00 <o:p></o:p></p><p class=MsoPlainText>>> UTC<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> I agree in part and disagree in part:<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> On Tue, Sep 27, 2016 at 6:05 AM, Schweighofer Erich <<a href="mailto:erich.schweighofer@univie.ac.at"><span style='color:windowtext;text-decoration:none'>erich.schweighofer@univie.ac.at</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> ...<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> The more I read about Ruggie Principles I am convinced that they do not really fit for ICANN.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> <o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> I tend to agree with this.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> The hard legal core of ICANN's obligations is much less, even depending on the various jurisdictions.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> I'm not sure what this means. If it means that there are Ruggie <o:p></o:p></p><p class=MsoPlainText>>> obligations that don't fit ICANN, then I agree. Otherwise, this <o:p></o:p></p><p class=MsoPlainText>>> needs further explanation.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Yes – Ruggie do not fit properly. ICANN is essential for a global communication platform and must respect related human rights –the “hard core”, subject to the interpretation in the various jurisdictions.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> ICANN is inclusive, e.g. also flexible.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Again not sure what this means. If this means that ICANN must be <o:p></o:p></p><p class=MsoPlainText>>> inclusive of, e.g., New gTLD applicants and ccTLD operators <o:p></o:p></p><p class=MsoPlainText>>> (governments and otherwise), whether or not they comply with human <o:p></o:p></p><p class=MsoPlainText>>> rights provision, then I agree. ICANN can't be a human rights filter <o:p></o:p></p><p class=MsoPlainText>>> for the Internet. If this means something else, it needs further <o:p></o:p></p><p class=MsoPlainText>>> explanation. <o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> It means that we cannot oblige new gTLD applicants or ccTLD operators to comply with human rights above the national interpretation of human rights obligations. There are other fora to discuss compliance with human rights standards.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> WS2-HR should focus on the freedom of communication worldwide, subject to usual safeguard clauses + the international human rights treaty obligations.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> This sounds suspiciously like "cherry-picking" (i.e., picking and choosing among human rights obligation), and I am firmly opposed to that. Also while human rights treaty obligations are relevant (and we need to determine what we are referring to as such) they do not bind ICANN, except to the extent they have been adopted and codified by applicable laws. The Bylaw doesn't take us further than that.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> It is not cherry-picking, it is a suggestion which human rights are relevant to be considered. Free communication should be the main concern.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> You are right that human rights treaties formally do not bind ICANN but that sound not good in practice. We have to substitute this by self-commitment, as we do now.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> In an ethical code of ICANN, we can go much further, and here we can re-use Ruggie to some extent.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> An "ethical code of ICANN" is far, far beyond the mandate and scope of this subgroup. Our task is to provide a framework for interpreting the Bylaw.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> It is good to work on an idealistic world but we have to realistic, too.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> That I can agree with.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> <o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Best, Erich Schweighofer<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Greg<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> -----Ursprüngliche Nachricht-----<o:p></o:p></p><p class=MsoPlainText>>> Von: <a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr-bounces@icann.org</span></a> [<a href="mailto:ws2-hr-bounces@icann.org"><span style='color:windowtext;text-decoration:none'>mailto:ws2-hr-bounces@icann.org</span></a>] Im <o:p></o:p></p><p class=MsoPlainText>>> Auftrag von Niels ten Oever<o:p></o:p></p><p class=MsoPlainText>>> Gesendet: Dienstag, 27. September 2016 11:18<o:p></o:p></p><p class=MsoPlainText>>> An: <a href="mailto:ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>>> Betreff: [Ws2-hr] Proposed agenda meeting September 27 - 19:00 UTC<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Dear all,<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Please find underneath and attached the proposed agenda for the call of September 27, 19:00 UTC.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Comments and suggestions are welcome.<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> 1. Administrivia<o:p></o:p></p><p class=MsoPlainText>>> Roll call, absentees, SoIs, etc<o:p></o:p></p><p class=MsoPlainText>>> 2. Analysis of Ruggie Principles for ICANN - discussion on UN Guiding <o:p></o:p></p><p class=MsoPlainText>>> Principles 15, 13, 19 3. AOB<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Best,<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Niels<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> --<o:p></o:p></p><p class=MsoPlainText>>> Niels ten Oever<o:p></o:p></p><p class=MsoPlainText>>> Head of Digital<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> Article 19<o:p></o:p></p><p class=MsoPlainText>>> <a href="http://www.article19.org"><span style='color:windowtext;text-decoration:none'>www.article19.org</span></a><o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> PGP fingerprint 8D9F C567 BEE4 A431 56C4<o:p></o:p></p><p class=MsoPlainText>>> 678B 08B5 A0F2 636D 68E9<o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> _______________________________________________<o:p></o:p></p><p class=MsoPlainText>>> Ws2-hr mailing list<o:p></o:p></p><p class=MsoPlainText>>> <a href="mailto:Ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>Ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>>> <a href="https://mm.icann.org/mailman/listinfo/ws2-hr"><span style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/ws2-hr</span></a><o:p></o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>><o:p> </o:p></p><p class=MsoPlainText>>> _______________________________________________<o:p></o:p></p><p class=MsoPlainText>>> Ws2-hr mailing list<o:p></o:p></p><p class=MsoPlainText>>> <a href="mailto:Ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>Ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>>> <a href="https://mm.icann.org/mailman/listinfo/ws2-hr"><span style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/ws2-hr</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> _______________________________________________<o:p></o:p></p><p class=MsoPlainText>> Ws2-hr mailing list<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:Ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>Ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>> <a href="https://mm.icann.org/mailman/listinfo/ws2-hr"><span style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/ws2-hr</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> ________________________________<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.<o:p></o:p></p><p class=MsoPlainText>> _______________________________________________<o:p></o:p></p><p class=MsoPlainText>> Ws2-hr mailing list<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:Ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>Ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>> <a href="https://mm.icann.org/mailman/listinfo/ws2-hr"><span style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/ws2-hr</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> ________________________________<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.<o:p></o:p></p><p class=MsoPlainText>> _______________________________________________<o:p></o:p></p><p class=MsoPlainText>> Ws2-hr mailing list<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:Ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>Ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>> <a href="https://mm.icann.org/mailman/listinfo/ws2-hr"><span style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/ws2-hr</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> _______________________________________________<o:p></o:p></p><p class=MsoPlainText>> Ws2-hr mailing list<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:Ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>Ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText>> <a href="https://mm.icann.org/mailman/listinfo/ws2-hr"><span style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/ws2-hr</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>Ws2-hr mailing list<o:p></o:p></p><p class=MsoPlainText><a href="mailto:Ws2-hr@icann.org"><span style='color:windowtext;text-decoration:none'>Ws2-hr@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText><a href="https://mm.icann.org/mailman/listinfo/ws2-hr"><span style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/ws2-hr</span></a><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:gray'><br>This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. </span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p></o:p></span></p></div></body></html>