<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Whatever folks wish.<br>
SP<br>
<br>
<div class="moz-cite-prefix">On 16-04-21 5:21 PM, Edward Morris
wrote:<br>
</div>
<blockquote cite="mid:c1f5c57fc84f4a46920a059d737b2d6a@toast.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<span style="font-family: Arial, Helvetica, Sans-Serif; font-size:
12px">
<div>Thanks for your editing Stephanie! It makes the letter much
more effective. I'd like to get this done ASAP as well but I
do have problems referring to only one organisation and a
specific policy as a reference marker, particularly the
IETF's.</div>
<div> </div>
<div>There are several aspects of the IETF policy I don't agree
with (such as possible banning of offenders) and I believe
that the policy itself would be illegal for a California
public benefit corporation to adopt. Without dragging folks
into a tedious legal analysis, I would note that the
Declaration of Rights of the California Constitution has been
held to apply to private firms if expressed in the affirmative
(such as article 1, section 2, which refers to free speech;
the affirmative expression of California speech rights
differentiating it from the negative expression of such rights
in the first amendment of the US Constitution) (<em>Prunegard
Shopping </em><i>Center </i>being the defining case
extending such rights to private firms and facilities) and
combined with California's expansive long arm statute (CA Civ
Pro §410.10) could invalidate such a policy. While I did not
oppose including the IETF policy and process when our proposed
submission included multiple reference markers, including one
developed internally, I am uncomfortable issuing a statement
referencing only one policy because that could be perceived as
a direct endorsement of Council. That the policy
referenced may be illegal is also be a problem.</div>
<div> </div>
<div>Stephanie, would an alteration to your bullet point, such
as the one that follows, be acceptable?:</div>
<div> </div>
<div>Given ICANN's rather unique, open, volunteer,
multi-stakeholder character as an institution, would it be
useful to consider how other comparable organisations, such as
the IETF, have dealt with establishing similar policies?</div>
<div> </div>
<div>I'd be fine with that.</div>
<div> </div>
<div>Thanks for considering,</div>
<div> </div>
<div>Ed</div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div style="-webkit-touch-callout: none; -webkit-user-select:
none; -khtml-user-select: none;-moz-user-select:
none;-ms-user-select: none;-o-user-select: none;user-select:
none;"> </div>
<div> </div>
<hr align="center" size="2" width="100%">
<div><span style="font-family: tahoma,arial,sans-serif;
font-size: 10pt;"><b>From</b>: "Jennifer Gore Standiford"
<a class="moz-txt-link-rfc2396E" href="mailto:JStandiford@web.com"><JStandiford@web.com></a><br>
<b>Sent</b>: Thursday, April 21, 2016 9:43 PM<br>
<b>To</b>: "Stephanie Perrin"
<a class="moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@mail.utoronto.ca"><stephanie.perrin@mail.utoronto.ca></a>,
<a class="moz-txt-link-rfc2396E" href="mailto:egmorris1@toast.net">"egmorris1@toast.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:egmorris1@toast.net"><egmorris1@toast.net></a>, "James M.
Bladel" <a class="moz-txt-link-rfc2396E" href="mailto:jbladel@godaddy.com"><jbladel@godaddy.com></a>, "Marilia Maciel"
<a class="moz-txt-link-rfc2396E" href="mailto:mariliamaciel@gmail.com"><mariliamaciel@gmail.com></a>, <a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org">"council@gnso.icann.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a><br>
<b>Cc</b>: "Paul McGrady" <a class="moz-txt-link-rfc2396E" href="mailto:policy@paulmcgrady.com"><policy@paulmcgrady.com></a>,
"Carlos Raúl Gutiérrez G." <a class="moz-txt-link-rfc2396E" href="mailto:crg@isoc-cr.org"><crg@isoc-cr.org></a><br>
<b>Subject</b>: RE: [council] For Discussion: GNSO Letter to
Akram Atallah re: ICANN Harassment Policy</span>
<div> </div>
<style type="text/css"><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:"Times New Roman \;color\:\#333333";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
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";
color:black;}
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";
color:black;}
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.im
{mso-style-name:im;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1726677827;
mso-list-template-ids:-1906040434;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1960842276;
mso-list-type:hybrid;
mso-list-template-ids:-1724349430 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Thanks
Stephanie. Your additional bullet point below is
acceptable to me. Does anyone else have additional
thoughts? It would be great to close this out quickly. </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"
style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Stephanie Perrin
[<a class="moz-txt-link-freetext" href="mailto:stephanie.perrin@mail.utoronto.ca">mailto:stephanie.perrin@mail.utoronto.ca</a>]<br>
<b>Sent:</b> Thursday, April 21, 2016 4:23 PM<br>
<b>To:</b> Jennifer Gore Standiford;
<a class="moz-txt-link-abbreviated" href="mailto:egmorris1@toast.net">egmorris1@toast.net</a>; James M. Bladel; Marilia
Maciel; <a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a><br>
<b>Cc:</b> Paul McGrady; Carlos Raúl Gutiérrez G.<br>
<b>Subject:</b> Re: [council] For Discussion: GNSO
Letter to Akram Atallah re: ICANN Harassment Policy</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="margin-bottom:12.0pt">I caught a
couple of typos Jenn, and I would like to propose one
addition....many of our members agree with Avri's
suggestion (which I had included in the appendix, list of
other resources) that we talk to the IETF, and look at
their policy which they have recently completed. So I
added another bullet for your consideration, Changes
marked in <b>Bold</b>. <br>
Given the rather thorough trashing my late suggestions
have already received, please feel free to completely
ignore this contribution. Just trying to help....<br>
Stephanie Perrin</p>
<div>
<p class="MsoNormal"
style="margin-bottom:0in;margin-bottom:.0001pt">On
16-04-21 1:10 PM, Jennifer Gore Standiford wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="color:#1F497D">Hello
All, </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Again, I
greatly appreciate the efforts by the council members
regarding the draft letter to Akram on the subject of
Harassment. After reaching what seems to be an
agreement to exclude the attachment, I believe the
pendulum has swung too far the other way by removing
key content contained within James’ drafted letter.
Please see a revised version of his letter below
(with no attachment). I urge my peers to reach an
agreement soon, so that the GNSO offers a voice on
this issue while the topic remains relevant. -
Jennifer</span></p>
<p class="MsoPlainText"><span style="color:#1F497D"> </span></p>
<p class="MsoPlainText"><span style="color:#1F497D">Akram
Atallah</span></p>
<p class="MsoPlainText"><span style="color:#1F497D">COO
and interim CEO, ICANN</span></p>
<p class="MsoPlainText"><span style="color:#1F497D"> </span></p>
<p class="MsoPlainText"><span style="color:#1F497D">Dear
Akram </span></p>
<p class="MsoPlainText"><span style="color:#1F497D"> </span></p>
<p class="MsoPlainText"><span style="color:#1F497D">On
behalf of the GNSO Council, we would like to thank you
for your recent blog post (“Conduct at ICANN
Meetings”). Members of the Council, and all of the
GNSO Stakeholder Groups and Constituencies, </span></p>
<p class="MsoPlainText"><span style="color:#1F497D">share
the goal of ensuring that all ICANN community members
(shall)<b>are able to</b> participate and contribute
within an environment that does not tolerate
discrimination and<b> remains </b>free of harassment.
Without passing judgment on any specific incident, we
are encouraged by the commitment from Staff and the
Board to engage the community on this subject. When
considering a policy to address this area, we
respectfully ask for consideration regarding these key
questions: </span></p>
<p class="MsoPlainText"
style="margin-left:.5in;text-indent:-.25in;mso-list:l1
level1 lfo2"><!--[if !supportLists]--><span
style="font-family:Symbol"><span
style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman""> </span></span></span><!--[endif]--><span
style="color:#1F497D">Would a policy enhance the
current ‘Expected Standards of Behavior’ or remain
independent? </span></p>
<p class="MsoPlainText"
style="margin-left:.5in;text-indent:-.25in;mso-list:l1
level1 lfo2"><!--[if !supportLists]--><span
style="font-family:Symbol"><span
style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman""> </span></span></span><!--[endif]--><span
style="color:#1F497D">How would reporting procedures
be defined and<b> who</b> would be included in the
reporting structure i.e. ICANN Staff, Office of the
Ombudsman, or other entity? </span></p>
<p class="MsoPlainText"
style="margin-left:.5in;text-indent:-.25in;mso-list:l1
level1 lfo2"><!--[if !supportLists]--><span
style="font-family:Symbol"><span
style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman""> </span></span></span><!--[endif]--><span
style="color:#1F497D">What mechanism would be in place
to <b>enforce</b> the policy and protect those
involved <b>in</b> known incidents? </span></p>
</blockquote>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo3"><b>Given ICANN's rather unique, open,
volunteer, multi-stakeholder character as an
institution, would it be useful to consider how other
comparable organizations have dealt with reporting and
enforcement? We understand that the IETF has recently
gone through a similar exercise, and it might be
useful to reach out to them for ideas, both for
process and substance. The new policy is here </b><b><a
moz-do-not-send="true"
href="https://www.ietf.org/blog/2016/04/team-to-help-regarding-harassment-concerns/"><a class="moz-txt-link-freetext" href="https://www.ietf.org/blog/2016/04/team-to-help-regarding-harassment-concerns/">https://www.ietf.org/blog/2016/04/team-to-help-regarding-harassment-concerns/</a></a></b><b>
</b></li>
</ul>
<p class="MsoNormal"
style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><b><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:#1F497D"> </span></b><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif""> </span></p>
<p class="MsoPlainText"><span style="color:#1F497D">We call
upon the GNSO community to engage and participat<b>e,</b>
as we anticipate additional topics and questions will
arise from these efforts. It is worth noting that other
groups have begun work in this area (Statement from NCUC
Executive Committee). We urge ICANN staff to
incorporate these initial questions during the
commencement of this exercise. <b> We</b> all agree that
a new policy must ensure a healthy environment for all.
</span></p>
<p class="MsoPlainText"><span style="color:#1F497D"> </span></p>
<p class="MsoPlainText"><span style="color:#1F497D">Thank
you</span></p>
<p class="MsoPlainText"><span style="color:#1F497D"> </span></p>
<p class="MsoPlainText"><span style="color:#1F497D">Donna
Austin, GNSO Vice-Chair</span></p>
<p class="MsoPlainText"><span style="color:#1F497D">James
Bladel, GNSO Chair</span></p>
<p class="MsoPlainText"><span style="color:#1F497D">Heather
Forrest, GNSO Vice-Chair</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-serif"">
<a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>
[<a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">mailto:owner-council@gnso.icann.org</a>]
<b>On Behalf Of </b>Edward Morris<br>
<b>Sent:</b> Wednesday, April 20, 2016 11:13 PM<br>
<b>To:</b> James M. Bladel; Marilia Maciel<br>
<b>Cc:</b> Paul McGrady; Carlos Raúl Gutiérrez G.;
Stephanie Perrin; <a moz-do-not-send="true"
href="mailto:council@gnso.icann.org">
council@gnso.icann.org</a><br>
<b>Subject:</b> Re: [council] For Discussion: GNSO
Letter to Akram Atallah re: ICANN Harassment Policy</span></p>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">Hi
everybody,</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">I
must admit I'm not very happy with the way this
conversation has gone. To be clear, I'm not too
pulsed by the policy disagreements. I am a bit
perturbed, though, at the timing of many of the
contributions. We're better than this.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">Let
me first extend my thanks and appreciation to
Jennifer for her leadership and hard work on this
effort. In the four plus years I have been involved
with ICANN I can not recall ever having worked with
someone whose passion, knowledge, competence and
expertise I have come to so admire. I am honoured
and humbled to serve on the same Council as she.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">I
would also like to thank James, for his tireless
effort to try to bring this matter to a conclusion.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">The
small group proposal was posted to the Council list
on 6 April. Stephanie, to her credit, was the only
Councillor to indicate widespread dissatisfaction
with the small group proposal between the time it
was posted and our call on the 14th: the expected
date of agreement and dispatch. I appreciate the
preambles of many of those who weighed in late on
the matter acknowledging the work of the small
group who put together the initial proposal, but I'm
not a big fan of those who weigh in last minute to
criticise work they themselves chose not to
participate in or object to in a timely manner. This
matter obviously needed conversation but because of
the lateness of most of the objections we didn't
have time for that. We need to do better in the
future and I'm sure we will.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">There
is a proposed GNSO public comment on the FY17 budget
and operating plan a few of us have worked on that
is still out for work. There is a hard deadline of
30 April for submission. I believe we've set a
deadline a few days earlier for objections,
contributions and comments. It's still a skeleton
paper and could use more meat. Contributions are not
only welcome but are needed. I only ask you, my
colleagues, to do your best to please voice any
objections sooner rather than later. It's not good
for the quality of discussion nor respectful to
those of us who put together the initial documents
to jump in with wholesale objections at deadline.
Thank you for your consideration.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">As
for the matter at hand:</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">1.
There was never any attempt to create or signify
GNSO policy in the initial proposal. Rather we were
trying to include "reference markers" to
possible policies. One was created by the small
team, improved upon with suggestions by others.
There were references to other external policies
that we thought staff and board might want to
consider. I have disagreements, some substantial,
with each of the reference markers save the one we
created. I did not object to their inclusion in the
letter because I recognised what they were: markers,
not concrete proposals.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">2.
I support the approach of the Business Constituency
in a more specific form. My preference would be for
the Board to ask ICANN Legal to draft a conference
harassment policy, post the proposed policy for
public comment and then have the Board act
accordingly. I have complete confidence John Jeffrey
and his team could and would produce a substantive
policy proposal that we all could and would support.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">3.
I do not support the creation of a CCWG in this
matter. Please see point 2 for my procedural
preference.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">4.
I commend Amr for a very creative and substantive
approach to the overall culture where certain forms
of harassment have IMHO been made somewhat
acceptable. Although I would prefer that ICANN legal
develop an initial conference policy, I do believe
Amr has several ideas that could in compliment
really help us attack this problem.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">5.
I still prefer the initial proposal of the small
team, mark 2 (as improved upon by James and staff),
to any proposal that has since been produced. I
recognise that there have been a number of
objections, unwarranted in my view, to that approach
and that we are unlikely at this time to achieve
momentum in that direction. On the other hand,
I should note that I find Paul's most recent
proposal, while appreciating his effort, to be a
bit too generic and lacking enough substance for me
to be able to support </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">As
a compromise I am willing to accept and propose we
go forward with James suggestion earlier today to
proceed with the letter, minus the key points. I
note that this approach seemed to meet with the
approval of several Councillors (Jennifer, Keith,
Amr, Marilia) and I add my support to theirs. It's
time to get this letter out.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">Respectfully,</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">Ed</span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div style="margin-bottom:10.0pt">
<div class="MsoNormal"
style="margin-bottom:0in;margin-bottom:.0001pt;text-align:center"
align="center">
<hr align="center" size="2" width="100%"></div>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-serif"">From</span></b><span
style="font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-serif"">:
"Marilia Maciel" <<a moz-do-not-send="true"
href="mailto:mariliamaciel@gmail.com">mariliamaciel@gmail.com</a>><br>
<b>Sent</b>: Thursday, April 21, 2016 1:07 AM<br>
<b>To</b>: "James M. Bladel" <<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>><br>
<b>Cc</b>: "Paul McGrady" <<a
moz-do-not-send="true"
href="mailto:policy@paulmcgrady.com"><a class="moz-txt-link-abbreviated" href="mailto:policy@paulmcgrady.com">policy@paulmcgrady.com</a></a>>,
"Carlos Raúl Gutiérrez G." <<a
moz-do-not-send="true" href="mailto:crg@isoc-cr.org"><a class="moz-txt-link-abbreviated" href="mailto:crg@isoc-cr.org">crg@isoc-cr.org</a></a>>,
"Stephanie Perrin" <<a moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>>,
"<a moz-do-not-send="true"
href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br>
<b>Subject</b>: Re: [council] For Discussion: GNSO
Letter to Akram Atallah re: ICANN Harassment Policy</span></p>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">Hi
James and all, </span></p>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">I
would rather support your original letter. It was
concise, but made the relevant points that need to
be made. Due to personal problems I have been null
on this discussions and I publicly apologise to
the colleagues that carried the piano -
particularly Jennifer and Ed. I think Jennifer put
forward an excellent proposal and I personally
disagree with the points that were made that ended
watering it to the text that we have in front of
us. What we are discussing is relevant to GNSO
constituencies and I believe we are in no way out
of our remit here. However, I do understand my
comment is not timely. Let's just not weaken the
message any further. And we absolutely need a
separate policy on harassment. </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">Thank
you</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">Marília</span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">
</span></p>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">On
Wed, Apr 20, 2016 at 7:34 PM, James M. Bladel <<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>>
wrote: </span></p>
<p class="MsoNormal"><br>
<span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">Hi
Paul -<br>
<br>
This is a reasonable and perhaps minimalist
response, but does it strip<br>
away too much substance?<br>
<br>
Also, with the removal of the middle section, I
recommend some minor edits<br>
(below).<br>
<br>
Thoughts from the others on this? There is no firm
deadline for a<br>
response, but we need to bring this work to a
sensible conclusion that<br>
everyone can support.<br>
<br>
Thanks‹<br>
<br>
J.<br>
_____________<br>
<br>
Akram Atallah<br>
COO and interim CEO, ICANN<br>
<br>
Dear Akram <br>
<br>
On behalf of the GNSO Council, we would like to
thank you for your recent<br>
blog post (³Conduct at ICANN Meetings²) . Members
of the Council, and all<br>
of the GNSO Stakeholder Groups and Constituencies,
share the goal of<br>
ensuring that all members of the community can
participate in and<br>
contribute to ICANN, in an environment where
harassment and discrimination<br>
are not tolerated.<br>
<br>
Without passing judgment on any specific incident,
we are encouraged by<br>
the commitment from Staff and the Board to engage
the community on this<br>
subject in a manner which results in a suitable
policy designed to ensure<br>
the our mutual goal. We look forward to
participating the process to<br>
develop such a policy, and expect that members of
the GNSO community will<br>
also be engaged in this effort within their own
Stakeholder Groups and<br>
Constituencies. Some have already undertaken work
in their own groups (by<br>
way of example the ³Statement from NUCU Executive
Committee² which can be<br>
found here [link]). We urge the Board and Staff
to consider these<br>
materials in any community undertaking to develop
new policy addressing<br>
this issue.<br>
<br>
Please keep us informed of your work and how we
may help.<br>
<br>
Thank you<br>
<br>
<br>
Donna Austin, GNSO Vice-Chair<br>
James Bladel, GNSO Chair<br>
Heather Forrest, GNSO Vice-Chair<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 4/20/16, 13:17 , "<a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>
on behalf of Paul<br>
McGrady" <<a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>
on behalf of </span></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""><a
moz-do-not-send="true"
href="mailto:policy@paulmcgrady.com"><a class="moz-txt-link-abbreviated" href="mailto:policy@paulmcgrady.com">policy@paulmcgrady.com</a></a>>
wrote:<br>
<br>
><br>
>Thanks James and all. I think dropping
the specific recommendations<br>
>documents makes a lot of sense. Here is a
proposed revised cover to<br>
>Akram:<br>
><br>
>Akram Atallah<br>
>COO and interim CEO, ICANN<br>
><br>
>Dear Akram <br>
><br>
>On behalf of the GNSO Council, we would
like to thank you for your recent<br>
>blog post (³Conduct at ICANN Meetings²) .
Members of the Council, and<br>
>all of the GNSO Stakeholder Groups and
Constituencies, share the goal of<br>
>ensuring that all members of the community
can participate in and<br>
>contribute to ICANN, in an environment
where harassment and<br>
>discrimination are not tolerated. We
expect that members of the GNSO<br>
>community will be engaged in this effort
within their own Constituencies,<br>
>Advisory Committees, etc. and note that
some have already undertaken work<br>
>in their own groups (by way of example the
³Statement from NUCU Executive<br>
>Committee² which can be found here
[link]). We urge the Board and Staff<br>
>to consider these materials in any
community undertaking to develop new<br>
>policy addressing this issue.<br>
><br>
>Without passing judgment on any specific
incident, we are encouraged by<br>
>the commitment from Staff and the Board to
engage the community on this<br>
>subject in a manner which results in a
suitable policy designed to ensure<br>
>the our mutual goal. We look forward to
participating the process to<br>
>develop such a policy. Please keep us
informed of your work and how we<br>
>may help.<br>
><br>
><br>
>Thank you<br>
><br>
><br>
>Donna Austin, GNSO Vice-Chair<br>
>James Bladel, GNSO Chair<br>
>Heather Forrest, GNSO Vice-Chair<br>
><br>
><br>
><br>
>-----Original Message-----<br>
>From: <a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>
[mailto:<a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>]<br>
>On Behalf Of Carlos Raúl Gutiérrez G.<br>
>Sent: Tuesday, April 19, 2016 05:45 PM<br>
>To: <a moz-do-not-send="true"
href="mailto:policy@paulmcgrady.com">policy@paulmcgrady.com</a><br>
>Cc: Stephanie Perrin; <a
moz-do-not-send="true"
href="mailto:council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></a><br>
>Subject: Re: [council] For Discussion:
GNSO Letter to Akram Atallah re:<br>
>ICANN Harassment Policy<br>
><br>
><br>
>I want to restate my +1 to Paul´s comments
very specifically on the way<br>
>he has phrased some issues questions<br>
><br>
>> I guess I have my doubts in general
about this being the role of the<br>
>> GNSO Council.<br>
><br>
>me too<br>
><br>
>> Clearly, this is an important issue
which affects all members of the<br>
>> ICANN community, and not just members
of the GNSO.<br>
><br>
>exactly<br>
><br>
>> Wouldn't a simple letter (1) making
note of the event, (2) making note<br>
>> of the lack of a clear policy, and
(3) asking the Board to launch a<br>
>> CCWG to address this issue (if the
Board believes that it and Staff<br>
>> together cannot or should not for
some reason), be sufficient? I just<br>
>> don't see how the Council should be
in the business of making specific<br>
>> policy recommendations without a
policy process.<br>
><br>
>see under ³picket fence²<br>
><br>
>> The Council is not a legislative body
- our role is to play traffic<br>
>> cop to grass roots movements, right?<br>
><br>
>thats the way I see it and why I added my
+1<br>
>><br>
>><br>
>> Thanks, and sorry if I am missing
something here!<br>
><br>
>I miss clear guidelines from the
Corporation on engagement rules for<br>
>participants in f2f meetings (like the
ones we have in adobe connect<br>
>rooms).<br>
><br>
>Carlos Raul Gutierrez<br>
><br>
><br>
>><br>
>><br>
>> Best,<br>
>> Paul<br>
>><br>
>><br>
>><br>
>>> -------- Original Message
--------<br>
>>> Subject: Fwd: Re: [council] RE:
For Discussion: GNSO Letter to Akram<br>
>>> Atallah re: ICANN Harassment
Policy<br>
>>> From: Stephanie Perrin<br>
>>> <[<a moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>](mailto:<a
moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.uto"><a class="moz-txt-link-abbreviated" href="mailto:stephanie.perrin@mail.uto">stephanie.perrin@mail.uto</a></a><br>
>>> <a moz-do-not-send="true"
href="http://ronto.ca" target="_blank">ronto.ca</a>)><br>
>>> Date: Wed, April 06, 2016 1:31 pm<br>
>>> To: "[<a moz-do-not-send="true"
href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>](mailto:<a
moz-do-not-send="true"
href="mailto:council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></a>)"<br>
>>> <[<a moz-do-not-send="true"
href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>](mailto:<a
moz-do-not-send="true"
href="mailto:council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></a>)><br>
>>><br>
>>><br>
>>><br>
>>> and one more time....<br>
>>> SP<br>
>>><br>
>>> -------- Forwarded Message
--------<br>
>> Subject:<br>
>> Re: [council] RE: For Discussion:
GNSO Letter to Akram Atallah re:<br>
>> ICANN Harassment Policy<br>
>> Date:<br>
>> Wed, 6 Apr 2016 16:28:01 -0400<br>
>> From:<br>
>> Stephanie Perrin<br>
>> [<<a moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>>](mailto:<a
moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.uto"><a class="moz-txt-link-abbreviated" href="mailto:stephanie.perrin@mail.uto">stephanie.perrin@mail.uto</a></a><br>
>> <a moz-do-not-send="true"
href="http://ronto.ca" target="_blank">ronto.ca</a>)<br>
>> To:<br>
>> Jennifer Gore Standiford<br>
>> [<<a moz-do-not-send="true"
href="mailto:JStandiford@web.com">JStandiford@web.com</a>>](mailto:<a
moz-do-not-send="true"
href="mailto:JStandiford@web.com"><a class="moz-txt-link-abbreviated" href="mailto:JStandiford@web.com">JStandiford@web.com</a></a>),
James M. Bladel<br>
>> [<<a moz-do-not-send="true"
href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>](mailto:<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>),
Austin, Donna<br>
>> [<<a moz-do-not-send="true"
href="mailto:Donna.Austin@neustar.biz">Donna.Austin@neustar.biz</a>>](mailto:<a
moz-do-not-send="true"
href="mailto:Donna.Austin@neustar.biz"><a class="moz-txt-link-abbreviated" href="mailto:Donna.Austin@neustar.biz">Donna.Austin@neustar.biz</a></a>),
Phil<br>
>> Corwin [<<a moz-do-not-send="true"
href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a>>](mailto:<a
moz-do-not-send="true"
href="mailto:psc@vlaw-dc.com"><a class="moz-txt-link-abbreviated" href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a></a>),
GNSO Council List<br>
>> [<<a moz-do-not-send="true"
href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>>](mailto:<a
moz-do-not-send="true"
href="mailto:council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></a>)<br>
>><br>
>>><br>
>>> I am sorry to be late with my
feedback. This is a great effort so<br>
>>> far, but I must say I find it a
wee bit over the top. Let me explain<br>
>>> why:<br>
>>><br>
>>> * The list of offensive
(inappropriate of unwanted) conduct is<br>
>>> exhaustive but not necessarily
helpful. "at a minimum" needs to go,<br>
>>> as Phil has pointed out. The
problem in harassment policies in my<br>
>>> view arises in the matter of how
to determine "offensive" now<br>
>>> "inappropriate", particularly
across cultures. It would be more<br>
>>> helpful to expand on this,
explaining the cross-cultural nature of<br>
>>> ICANN and give guidance on how to
conduct oneself<br>
>>> _tentatively_.....eg. if you are
Dutch and in the habit of greeting<br>
>>> people with three kisses, ask
first. I don't think we want to shut<br>
>>> down normal gestures of
familiarity and affection, but maybe we<br>
>>> do....it is worth a discussion.
The other part that needs to go<br>
>>> unless you want us all to be tied
into legal quandries is this: "or<br>
>>> any other category protected by
any applicable governing law". What<br>
>>> are the laws of Finland on public
deportment, discrimination, etc.<br>
>>> ? Where do we go next, how do I
check the laws there? I don't find<br>
>>> this helpful. If you are going to
include language like this, we will<br>
>>> have to have the already burdened
Constituency Travel send out<br>
>>> advisories: eg. When in Turkey,
do not make jokes about Ataturk as<br>
>>> it is forbidden by law, etc.
etc.<br>
>> * There needs to be a section
discussing the rights of the accused,<br>
>> and their rights to confidentiality.
It is my view that we need a<br>
>> privacy policy more than a harassment
policy, because I feel that<br>
>> inappropriate conduct is in fact
already covered by our acceptable<br>
>> conduct policy, but here we are
anyway. The accused has a right to<br>
>> have investigations conducted
properly, and in confidence in my view,<br>
>> so how that is going to take place,
who does them, when the accuser is<br>
>> permitted to go public,etc. needs
quite a bit of work.<br>
>>><br>
>>> * "By participating in an ICANN
conference, you agree to prohibit<br>
>>> harassment....."<br>
>> I actually think we should not demand
that anyone who agrees to<br>
>> participate in an ICANN conference
should have to agree to take on the<br>
>> role of enforcer of a harassment
policy. Further on this:<br>
>>><br>
>>> * "You shall report any
actions that you believe may violate<br>
>>> our policy no matter how slight
the actions might seem".<br>
>> This is not necessary. Anyone who
experiences harassment ought to be<br>
>> capable of determining themselves
whether there was abuse, let us not<br>
>> invite people to interfere with other
people's jokes unless those<br>
>> jokes are offending them, the
listener. In other words, I take no<br>
>> offence at Michele N calling me a
crazy tree-hugger, and I really<br>
>> don't want to be dragged into Chris
Lahatte's office to discuss it<br>
>> just because someone overheard it and
felt I ought to be offended.<br>
>> Now if they are offended, (eg. they
are a tree-hugger and are offended<br>
>> at the suggestion that I ought to be
considered in that group) they<br>
>> can make their own complaint and
leave me out of it. In a policy such<br>
>> as this, one has to be quite careful
about how wide one opens the<br>
>> door.<br>
>>><br>
>>> However, thanks to all who worked
on this, it is very difficult to<br>
>>> craft a good harassment policy
and enforcement mechanism, and my hat<br>
>>> is off to you on efforts so far.
I would also like to apologize to<br>
>>> anyone whom I have either touched
or kissed hello over the three<br>
>>> years I have been attending
ICANN. I meant no harm, I spent too much<br>
>>> time in Montreal (where we kiss
everybody only twice) and I will<br>
>>> strive to be more guarded in
future.<br>
>>><br>
>>> I spent a year working in our
central agency in the Canadian<br>
>>> Government, working on the ethics
code and a limited time also on<br>
>>> evaluating workplace wellness
(including harassment) policies and<br>
>>> implementation in the
departments. I like the Canadian approach,
and<br>
>>> offer you the link here:<br>
>>> [](<a moz-do-not-send="true"
href="http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/index-eng.asp%29%5b"
target="_blank">http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/index-eng.asp)[</a><br>
>>><br>
>>><a moz-do-not-send="true"
href="http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/index-eng.asp%5d%28http:/"
target="_blank">http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/index-eng.asp](http:/</a><br>
>>>/<a moz-do-not-send="true"
href="http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/index-eng.asp"
target="_blank">www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/index-eng.asp</a>).<br>
>>> In particular, the tools that
help evaluate whether an act<br>
>>> constitutes harassment I think
are useful:<br>
>>> [](<a moz-do-not-send="true"
href="http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/mibh-sjh-eng.as"
target="_blank">http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/mibh-sjh-eng.as</a><br>
>>><br>
>>>p)[<a moz-do-not-send="true"
href="http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/mibh-sjh-eng.asp%5d%28"
target="_blank">http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/mibh-sjh-eng.asp](</a><br>
>>><a moz-do-not-send="true"
href="http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/mibh-sjh-eng.asp"
target="_blank">http://www.tbs-sct.gc.ca/psm-fpfm/healthy-sain/prh/mibh-sjh-eng.asp</a>).<br>
>>> They put an emphasis on the
activity needing to be repeated, or one<br>
>>> action to be extreme...this may
be more applicable in a workplace<br>
>>> environment but I think the tests
are nevertheless relevant.<br>
>>><br>
>>> Cheers Stephanie Perrin<br>
>>><br>
>>> On 2016-04-06 15:00, Jennifer
Gore Standiford wrote:<br>
>>>> James and Colleagues,<br>
>><br>
>> Thanks to Donna and Phil for their
constructive feedback. With that,<br>
>> please review and provide any
additional feedback based on the</span></p>
</div>
</div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">>>
revised draft ŒICANN Conference Harassment Key
Points for<br>
>> Consideration¹.<br>
>><br>
>> The attached addresses the following
feedback received thus far, in<br>
>> particular:<br>
>><br>
>> Are Dr Crocker and the other Board
members covered under the ICANN<br>
>> staff policy on Sexual Harassment or
would they be covered under a<br>
>> community ICANN attendee policy?<br>
>> Included the following sentence: ŒThe
term ³ICANN Conference<br>
>> Attendees² includes event registered and
non-registered participants,<br>
>> sponsors, contractors, consultants, staff
and board members.¹<br>
>><br>
>> This very extensive list of potential
offenses being non-exclusive<br>
>> (indicated by the words ³At a minimum²
that start the document)<br>
>> Removed term ³ At a minimum²<br>
>><br>
>> The use of the modifier ³Offensive² at
the start of sections 1-4, in<br>
>> that this subjective standard inevitably
raises the question<br>
>> ³offensive to whom²? In this regard, I
think there must be some<br>
>> element of intent to harass or demean in
the behavior subject to<br>
>> sanction, and that any policy should
recognize that the cultural<br>
>> diversity of ICANN meeting attendees may
lead to situations where<br>
>> remarks that are not intended to offend
may nonetheless do so.<br>
>> Replaced the word Œ offensive¹ with
Œunwanted¹ or Œinappropriate¹<br>
>><br>
>> A need to strictly define, and limit, the
³prompt, appropriate<br>
>> remedial action² that ICANN staff may
take if they determine that<br>
>> harassment has occurred (as well as
whether ICANN staff are the<br>
>> appropriate parties to undertake such
investigations, and whether the<br>
>> investigatory and judgmental/sanctioning
roles should be separate).<br>
>> Change verbiage to state ŒICANN staff is
required toŠ¹ instead of<br>
>> Œmay¹<br>
>><br>
>> Contradictory language regarding whether
an individual who believes<br>
>> that he/she has witnessed harassment
should report it, or must report<br>
>> it.<br>
>> Change the verbiage to sake of
consistency. Opted for Œshould/shall¹<br>
>> vs. Œrequired/will¹ </span></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">>><br>
>> The outstanding questions that James
has outline should remain<br>
>> included in the GNSO letter to ensure
each item is addressed.<br>
>><br>
>> Thanks<br>
>> Jennifer<br>
>><br>
>><br>
>> **From:** James M. Bladel<br>
>> [[mailto:<a moz-do-not-send="true"
href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>](mailto:<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>)]<br>
>>>> **Sent:** Wednesday, April
06, 2016 1:57 PM<br>
>>>> **To:** Jennifer Gore
Standiford; Austin, Donna; Phil Corwin; GNSO<br>
>>>> Council List<br>
>>>> **Subject:** Re: For
Discussion: GNSO Letter to Akram Atallah re:<br>
>>>> ICANN Harassment Policy<br>
>><br>
>> Thanks Jennifer, Phil and Donna for
weighing in.<br>
>><br>
>> Perhaps the concern is that we¹ve
called this document a ³draft²<br>
>> but it too closely resembles a
finished policy. I believe (and I<br>
>> think Jennifer¹s note confirms) that
this was intended to start a<br>
>> dialogue in whatever subsequent group
addresses this work, and a<br>
>> mechanism for relaying GNSO ideas,
questions and concerns in to that<br>
>> effort.<br>
>><br>
>> I appreciate the discussion, and hope
that we can all get to a place<br>
>> where we¹re either comfortable with
the draft, or we amend it, or<br>
>> substitute it with something else.<br>
>><br>
>> Thanks‹<br>
>><br>
>><br>
>> **From:** Jennifer Standiford<br>
>> <[<a moz-do-not-send="true"
href="mailto:JStandiford@web.com">JStandiford@web.com</a>](mailto:<a
moz-do-not-send="true"
href="mailto:JStandiford@web.com"><a class="moz-txt-link-abbreviated" href="mailto:JStandiford@web.com">JStandiford@web.com</a></a>)><br>
>>>> **Date:** Wednesday, April 6,
2016 at 12:46<br>
>>>> **To:** "Austin, Donna"<br>
>>>> <[](mailto:<a
moz-do-not-send="true"
href="mailto:Donna.Austin@neustar.biz"><a class="moz-txt-link-abbreviated" href="mailto:Donna.Austin@neustar.biz">Donna.Austin@neustar.biz</a></a>)[<a
moz-do-not-send="true"
href="mailto:Donna.Austin@neustar.biz"><a class="moz-txt-link-abbreviated" href="mailto:Donna.Austin@neustar.biz">Donna.Austin@neustar.biz</a></a>](mailt<br>
>>>> <a moz-do-not-send="true"
href="mailto:o%3ADonna.Austin@neustar.biz">o:Donna.Austin@neustar.biz</a>)>,
Phil Corwin<br>
>>>> <[<a
moz-do-not-send="true"
href="mailto:psc@vlaw-dc.com"><a class="moz-txt-link-abbreviated" href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a></a>](mailto:<a
moz-do-not-send="true"
href="mailto:psc@vlaw-dc.com"><a class="moz-txt-link-abbreviated" href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a></a>)>,
James Bladel<br>
>>>> <[<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>](mailto:<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>)>,
GNSO Council<br>
>>>> List <[<a
moz-do-not-send="true"
href="mailto:council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></a>](mailto:<a
moz-do-not-send="true"
href="mailto:council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></a>)><br>
>>>> **Subject:** RE: For
Discussion: GNSO Letter to Akram Atallah re:<br>
>>>> ICANN Harassment Policy<br>
>><br>
>> Hi Phil and Colleagues,<br>
>><br>
>> Just a friendly reminder the attached
document that was put forth in<br>
>> the GNSO Letter to Akram was referred
to as a draft. James also<br>
>> included several questions that
remain unanswered that will need to be<br>
>> address in addition to the points
that you and Donna have raised. As<br>
>> for Donna¹s specific question, I
would anticipate that ICANN<br>
>> Conference Participants would be a
defined term that would include all<br>
>> ICANN staff and board members.<br>
>><br>
>> Jennifer<br>
>><br>
>> **From:**<br>
>> [<a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>](mailto:<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a></a>)<br>
>> [[mailto:<a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>](mailto:<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.icann"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.icann">owner-council@gnso.icann</a></a><br>
>> .org)]<br>
>> **On Behalf Of** Austin, Donna<br>
>>>> **Sent:** Wednesday, April
06, 2016 1:36 PM<br>
>>>> **To:** Phil Corwin; James M.
Bladel; GNSO Council List<br>
>>>> **Subject:** [council] RE:
For Discussion: GNSO Letter to Akram<br>
>>>> Atallah re: ICANN Harassment
Policy<br>
>><br>
>> Hi Phil<br>
>><br>
>> It¹s a good point and also raises
another one for me. Are Dr Crocker<br>
>> and the other Board members covered
under the ICANN staff policy on<br>
>> Sexual Harassment or would they be
covered under a community ICANN<br>
>> attendee policy?<br>
>><br>
>> Donna<br>
>><br>
>> **From:**[](mailto:<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a></a>)[<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.ic"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.ic">owner-council@gnso.ic</a></a><br>
>> <a moz-do-not-send="true"
href="http://ann.org" target="_blank">ann.org</a>](mailto:<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a></a>)<br>
>> [[mailto:<a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>](mailto:<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.icann"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.icann">owner-council@gnso.icann</a></a><br>
>> .org)]<br>
>> **On Behalf Of** Phil Corwin<br>
>>>> **Sent:** Wednesday, 6 April
2016 9:33 AM<br>
>>>> **To:** James M. Bladel<br>
>>>> <[](mailto:<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>)[<a
moz-do-not-send="true"
href="mailto:jbladel@godaddy.com"><a class="moz-txt-link-abbreviated" href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a></a>](mailto:<a
moz-do-not-send="true"
href="mailto:jbladel@">jbladel@</a><br>
>>>> <a moz-do-not-send="true"
href="http://godaddy.com" target="_blank">godaddy.com</a>)>;<br>
>>>> GNSO Council List<br>
>>>> <[<a
moz-do-not-send="true"
href="mailto:council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></a>](mailto:<a
moz-do-not-send="true"
href="mailto:council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></a>)><br>
>>>> **Subject:** [council] RE:
For Discussion: GNSO Letter to Akram<br>
>>>> Atallah re: ICANN Harassment
Policy<br>
>><br>
>> Thinking about this a bit more how
would this incident be treated<br>
>> under any proposed Harassment Policy?<br>
>><br>
>> [](<a moz-do-not-send="true"
href="http://domainincite.com/18772-icann-53-launches-with-risky-caitlyn-"
target="_blank">http://domainincite.com/18772-icann-53-launches-with-risky-caitlyn-</a><br>
>> jenner-joke)[<a
moz-do-not-send="true"
href="http://domainincite.com/18772-icann-53-launches-with-risk"
target="_blank"><a class="moz-txt-link-freetext" href="http://domainincite.com/18772-icann-53-launches-with-risk">http://domainincite.com/18772-icann-53-launches-with-risk</a></a><br>
>> y-caitlyn-jenner-joke](<a
moz-do-not-send="true"
href="http://domainincite.com/18772-icann-53-launches"><a class="moz-txt-link-freetext" href="http://domainincite.com/18772-icann-53-launches">http://domainincite.com/18772-icann-53-launches</a></a><br>
>> -with-risky-caitlyn-jenner-joke)<br>
>><br>
>> Some found it offensive, and an
apology was issued by Chairman<br>
>> Crocker. Is that sufficient or would
reporting and investigation be<br>
>> required?<br>
>><br>
>><br>
>><br>
>> **Philip S. Corwin, Founding
Principal** **Virtualaw LLC**<br>
>> **1155 F Street, NW**<br>
>> **Suite 1050**<br>
>> **Washington, DC 20004**<br>
>> **<a moz-do-not-send="true"
href="tel:202-559-8597">202-559-8597</a>/Direct**<br>
>> **<a moz-do-not-send="true"
href="tel:202-559-8750">202-559-8750</a>/Fax**<br>
>> **<a moz-do-not-send="true"
href="tel:202-255-6172">202-255-6172</a>/Cell**<br>
>> ** **<br>
>> **Twitter: @VlawDC**<br>
>><br>
>> **_"Luck is the residue of design" --
Branch Rickey_**<br>
>><br>
>> **From:** Phil Corwin<br>
>>>> **Sent:** Wednesday, April
06, 2016 12:07 PM<br>
>>>> **To:** 'James M. Bladel';
GNSO Council List<br>
>>>> **Subject:** RE: For
Discussion: GNSO Letter to Akram Atallah re:<br>
>>>> ICANN Harassment Policy<br>
>><br>
>> Colleagues:<br>
>><br>
>> I support in principle sending a
letter to Akram on this subject and<br>
>> establishing clearer, enforceable
policies regarding sexual and other<br>
>> forms of harassment that may take
place at ICANN meetings.<br>
>><br>
>> However, while I am strongly opposed
to any form of such harassment, I<br>
>> have some concerns about the proposed
draft Harassment Policy,<br>
>> relating to:<br>
>> · This very extensive list of
potential offenses being<br>
>> non-exclusive (indicated by the words
³At a minimum² that start the<br>
>> document) · The use of the
modifier ³Offensive² at the start<br>
>> of sections 1-4, in that this
subjective standard inevitably raises<br>
>> the question ³offensive to whom²? In
this regard, I think there must<br>
>> be some element of intent to harass
or demean in the behavior subject<br>
>> to sanction, and that any policy
should recognize that the cultural<br>
>> diversity of ICANN meeting attendees
may lead to situations where<br>
>> remarks that are not intended to
offend may nonetheless do so.<br>
>> · A need to strictly define,
and limit, the ³prompt,<br>
>> appropriate remedial action² that
ICANN staff may take if they<br>
>> determine that harassment has
occurred (as well as whether ICANN staff<br>
>> are the appropriate parties to
undertake such investigations, and<br>
>> whether the investigatory and
judgmental/sanctioning roles should be<br>
>> separate).<br>
>> · Contradictory language
regarding whether an individual who<br>
>> believes that he/she has witnessed
harassment should report it, or<br>
>> must report it.<br>
>><br>
>> I look forward to engaging in a
discussion of these matters on our<br>
>> call of April 14th.<br>
>><br>
>> Best regards, Philip<br>
>><br>
>><br>
>> **Philip S. Corwin, Founding
Principal** **Virtualaw LLC**<br>
>> **1155 F Street, NW**<br>
>> **Suite 1050**<br>
>> **Washington, DC 20004**<br>
>> **202-559-8597/Direct**<br>
>> **202-559-8750/Fax**<br>
>> **202-255-6172/Cell**<br>
>> ** **<br>
>> **Twitter: @VlawDC**<br>
>><br>
>> **_"Luck is the residue of design" --
Branch Rickey_**<br>
>><br>
>> **From:**[](mailto:<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a></a>)[<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.ic"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.ic">owner-council@gnso.ic</a></a><br>
>> <a moz-do-not-send="true"
href="http://ann.org" target="_blank">ann.org</a>](mailto:<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a></a>)<br>
>> [[mailto:<a moz-do-not-send="true"
href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>](mailto:<a
moz-do-not-send="true"
href="mailto:owner-council@gnso.icann"><a class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.icann">owner-council@gnso.icann</a></a><br>
>> .org)]<br>
>> **On Behalf Of** James M. Bladel<br>
>>>> **Sent:** Monday, April 04,
2016 7:46 PM<br>
>>>> **To:** GNSO Council List<br>
>>>> **Subject:** [council] For
Discussion: GNSO Letter to Akram Atallah<br>
>>>> re: ICANN Harassment Policy<br>
>><br>
>> Council Colleagues ‹<br>
>><br>
>> Attached and copied below, please
find a draft letter from the Council<br>
>> to Akram Atallah, in response to his
recent blog post (³Conduct at<br>
>> ICANN Meetings²<br>
>></span></p>
</div>
</div>
<p class="MsoNormal"><span class="im"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">>>[](<a
moz-do-not-send="true"
href="https://www.icann.org/news/blog/conduct-at-ICANN-meetings"><a class="moz-txt-link-freetext" href="https://www.icann.org/news/blog/conduct-at-ICANN-meetings">https://www.icann.org/news/blog/conduct-at-ICANN-meetings</a></a>)[<a
moz-do-not-send="true" href="https://www"><a class="moz-txt-link-freetext" href="https://www">https://www</a></a></span></span><br>
<span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""><span
class="im">>>.<a moz-do-not-send="true"
href="http://icann.org/news/blog/conduct-at-ICANN-meetings%5d%28https:/www.icann.org/new"
target="_blank">icann.org/news/blog/conduct-at-ICANN-meetings](https://www.icann.org/new</a></span><br>
<span class="im">>>s/blog/conduct-at-ICANN-meetings)).</span><br>
<span class="im">>></span> </span></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">>>
In this note, I set out to make some
high-level points that support<br>
>> further work in this area, without
weighing in on any specific<br>
>> indecent. Also, the letter
references a statement from the NCUC ExCom<br>
>> (³Statement from NCUC Executive
Committee²<br>
>> [](<a moz-do-not-send="true"
href="http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html"
target="_blank">http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html</a><br>
>> )[<a moz-do-not-send="true"
href="http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html"
target="_blank">http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html</a>]<br>
>> (<a moz-do-not-send="true"
href="http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html"
target="_blank">http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html</a>))<br>
>> and the ICANN Harassment Policy
drafted by our volunteers (attached),<br>
>> and urges any future effort to
consider these materials.<br>
>><br>
>> If possible, please review these
documents prior to our next call on<br>
>> 14 APR. We can collect edits and
then decide if/how we want to<br>
>> proceed.<br>
>><br>
>> Thank you,<br>
>><br>
>> J.<br>
>><br>
>><br>
>> * * *<br>
>><br>
>> Akram Atallah<br>
>> COO and interim CEO, ICANN<br>
>><br>
>> Dear Akram <br>
>><br>
>> On behalf of the GNSO Council, we
would like to thank your for your<br>
>> recent blog post (³Conduct at ICANN
Meetings²). Members of the<br>
>> Council, and all of the GNSO
Stakeholder Groups and Constituencies,<br>
>> share the goal of ensuring that all
members of the community can<br>
>> participate in and contribute to
ICANN, in an environment where<br>
>> harassment and discrimination are not
tolerated.<br>
>><br>
>> Without passing judgment on any
specific incident, we are encouraged<br>
>> by the commitment from Staff and the
Board to engage the community on<br>
>> this subject.<br>
>> In support of this, volunteers on the
Council have prepared a draft<br>
>> (³ICANN Conference Harassment
Policy², attached). Several questions<br>
>> remain open, however, including:<br>
>><br>
>> ? Whether this Policy would
enhance, or be distinct from, the<br>
>> existing Expected Standards of
Behavior policy ? Whether<br>
>> complaints would be reported to ICANN
Staff, or the Office of the<br>
>> Ombudsman, or some other entity or
group ? How the policy will<br>
>> be enforced, and ? Other
topics and questions that will arise<br>
>> from this work.<br>
>><br>
>> We expect that members of the GNSO
community will be engaged in this<br>
>> effort, and note that some have
already undertaken work in their own<br>
>> groups (³Statement from NUCU
Executive Committee²). We urge this<br>
>> group to consider these materials in
any community undertaking to<br>
>> develop new policy addressing this
issue.<br>
>><br>
>> Thank you<br>
>><br>
>><br>
>> Donna Austin, GNSO Vice-Chair<br>
>> James Bladel, GNSO Chair<br>
>> Heather Forrest, GNSO Vice-Chair<br>
>><br>
>> [](<a moz-do-not-send="true"
href="https://www.icann.org/news/blog/conduct-at-icann-meetings%29%5bhttps:/"
target="_blank">https://www.icann.org/news/blog/conduct-at-icann-meetings)[https://</a><br>
>> <a moz-do-not-send="true"
href="http://www.icann.org/news/blog/conduct-at-icann-meetings%5d%28https:/www.icann.o"
target="_blank">
www.icann.org/news/blog/conduct-at-icann-meetings](https://www.icann.o</a><br>
>>
rg/news/blog/conduct-at-icann-meetings)<br>
>><br>
>> [](<a moz-do-not-send="true"
href="http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html"
target="_blank">http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html</a><br>
>> )[<a moz-do-not-send="true"
href="http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html"
target="_blank">http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html</a>]<br>
>> (<a moz-do-not-send="true"
href="http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html"
target="_blank">http://lists.ncuc.org/pipermail/ncuc-discuss/2016-March/018488.html</a>)<br>
>><br>
>> * * *<br>
>> No virus found in this message.<br>
>>>> Checked by AVG -<br>
>>>> [<a moz-do-not-send="true"
href="http://www.avg.com" target="_blank">www.avg.com</a>](<a
moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__ww"><a class="moz-txt-link-freetext" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__ww">https://urldefense.proofpoint.com/v2/url?u=http-3A__ww</a></a><br>
>>>> <a moz-do-not-send="true"
href="http://w.avg.com" target="_blank">w.avg.com</a>&d=CwMFAg&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr5<br>
>>>>
6eryGQiPHEqv4TL7JH87w&m=GTJBGbCRyivgpW19dk4dofA96i5L2FtmkxBrrkb_voc&<br>
>>>>
s=Wc6g-4Lo0XrpvCus6DBuVDgfsaHZUFkJkS6hjLLPAak&e=)<br>
>>>> Version: 2016.0.7497 / Virus
Database: 4545/11942 - Release Date:<br>
>>>> 04/02/16<br>
>><br>
>>><br>
>>><br>
>>><br>
><br>
><br>
><br>
<br>
</span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">
</span></p>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif"">--
</span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;line-height:115%;font-family:"Arial","sans-serif"">Marília
Maciel</span></b></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;line-height:115%;font-family:"Arial","sans-serif";color:#444444">Pesquisadora
Gestora - Centro de Tecnologia e
Sociedade - FGV Direito Rio</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;line-height:115%;font-family:"Arial","sans-serif";color:#444444">Researcher
and Coordinator - Center for
Technology & Society - FGV Law
School</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;line-height:115%;font-family:"Arial","sans-serif";color:#444444"><a
moz-do-not-send="true"
href="http://direitorio.fgv.br/cts"><a class="moz-txt-link-freetext" href="http://direitorio.fgv.br/cts">http://direitorio.fgv.br/cts</a></a></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;line-height:115%;font-family:"Arial","sans-serif";color:#444444">DiploFoundation
associate - <a moz-do-not-send="true"
href="http://www.diplomacy.edu"
target="_blank">www.diplomacy.edu</a></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;line-height:115%;font-family:"Arial","sans-serif";color:#444444">PoliTICs
Magazine Advisory Committee - <a
moz-do-not-send="true"
href="http://www.politics.org.br/"><a class="moz-txt-link-freetext" href="http://www.politics.org.br/">http://www.politics.org.br/</a></a></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;line-height:115%;font-family:"Arial","sans-serif""> </span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"
style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif""> </span></p>
</div>
</div>
</span>
</blockquote>
<br>
</body>
</html>