<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I hate to complicate this discussion, but I feel duty bound to point
out that the first human right many people think of these days with
respect to the domain name registration system is privacy. Freedom
of expression and the openness of the Internet rolls more easily off
the tongue....but if anyone says what about privacy, the WHOIS would
have to be re-examined. This of course conflicts with the marching
orders that the NTIA has had for ICANN since its inception.<br>
Stephanie Perrin<br>
<br>
<div class="moz-cite-prefix">On 2015-07-30 5:59, Erika Mann wrote:<br>
</div>
<blockquote
cite="mid:CADLdTjJfUJPJh_7ByAAXkEqUhTe7S-RJaAJDA1gXttpTjm+6Yg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="ltr">In addition to Avri's points, such a provision
could help as well to ensure that future business models that
relate to more sensitive strings (.gay for example) will
continue to be treated as any other string.
<div><br>
</div>
<div>Erika</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jul 30, 2015 at 11:42 AM, Avri
Doria <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Off the top of my head, I think a first thing we would have
to do would<br>
be to start understanding the impact, if any, of ICANN
operations and<br>
policies on human rights. Some of this work is already
starting in the<br>
human rights working party (HRWP), though that is a rather
informal<br>
beginning. I would also think that some part of the staff
would need to<br>
start taking these issues into consideration. I do not
think that it<br>
would cause any serious changes in the near future but would
make us<br>
more aware as time went on, and would give us a basis for
discussion<br>
both in the HRWP and in the ACSO and Board.<br>
<br>
In terms of the specific things it might limt us from, and
this would<br>
require some analysis on specifc events, might be creating
any kinds of<br>
policies or operations that forced limitation of content,
beyond the<br>
limitations required by law for incitement, on domain named
sites. It<br>
would in fact strengthen our postion in that respect.<br>
<br>
Most important though, it would cover a hole left by the
loss of the<br>
NTIA backstop, on any issue concerning freedom of
expression, free flow<br>
of information or openness of the Internet.<br>
<br>
thanks<br>
avri<br>
<span class=""><br>
On 30-Jul-15 11:07, Drazek, Keith wrote:<br>
> Hi Chris,<br>
><br>
> I'll have to defer to others with more expertise on
this one. It's a<br>
> good question that should be addressed.<br>
><br>
> Best,<br>
> Keith<br>
><br>
> On Jul 30, 2015, at 11:01 AM, Chris Disspain <<a
moz-do-not-send="true" href="mailto:ceo@auda.org.au">ceo@auda.org.au</a><br>
</span><span class="">> <mailto:<a
moz-do-not-send="true" href="mailto:ceo@auda.org.au">ceo@auda.org.au</a>>>
wrote:<br>
><br>
>> Keith,<br>
>><br>
>> This looks interesting. Could we think of an
example of something<br>
>> concrete ICANN would have to do if it made this
commitment? Or<br>
>> something it would not be able to do?<br>
>><br>
>><br>
>><br>
>> Cheers,<br>
>><br>
>><br>
>> Chris<br>
>><br>
>><br>
>>> On 30 Jul 2015, at 18:16 , Drazek, Keith <<a
moz-do-not-send="true"
href="mailto:kdrazek@verisign.com">kdrazek@verisign.com</a><br>
</span><span class="">>>> <mailto:<a
moz-do-not-send="true"
href="mailto:kdrazek@verisign.com">kdrazek@verisign.com</a>>>
wrote:<br>
>>><br>
>>> Hi Avri,<br>
>>><br>
>>> In order to tie your suggestion directly to
the language in<br>
>>> Secretary Strickling's April 2014 written
congressional testimony<br>
>>> (included in a prior email) and to reduce
concerns about scope<br>
>>> creep, would language along these lines be
acceptable to you?<br>
>>><br>
>>>> "Within its mission and in its
operations, ICANN will be committed<br>
>>>> to respect the fundamental human rights
of the exercise of free<br>
>>>> expression and the free flow of
information."<br>
>>><br>
>>> Speaking personally, I could probably support
this formulation. To<br>
>>> be clear, I have not discussed this with the
RySG, but it's<br>
>>> consistent with the requirements outlined by
NTIA so I think it's<br>
>>> certainly worth considering.<br>
>>><br>
>>> I'm not advocating including this in the
Bylaws, but I'm not<br>
>>> objecting to it either. However, if we don't
reach consensus for<br>
>>> adding to the Bylaws, I definitely think this
is worth further<br>
>>> consideration in WS2 and would support an
explicit reference using<br>
>>> this or similar language and timetable for
doing so.<br>
>>><br>
>>> Regards,<br>
>>> Keith<br>
>>><br>
>>>> On Jul 30, 2015, at 8:11 AM, Avri Doria
<<a moz-do-not-send="true" href="mailto:avri@acm.org">avri@acm.org</a><br>
</span><span class="">>>>> <mailto:<a
moz-do-not-send="true" href="mailto:avri@acm.org">avri@acm.org</a>>>
wrote:<br>
>>>><br>
>>>> Within its mission, ICANN will be
committed to respect fundamental<br>
>>>> human rights in its operationsespecially
with regard to the exercise<br>
>>>> of free expression or the free flow of
information.<br>
>>>
_______________________________________________<br>
>>> Accountability-Cross-Community mailing list<br>
>>> <a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
</span>>>> <mailto:<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>><br>
>>> <a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<span class="im HOEnZb">>><br>
><br>
><br>
> _______________________________________________<br>
> Accountability-Cross-Community mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
> <a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br>
<br>
</span><span class="im HOEnZb">---<br>
This email has been checked for viruses by Avast antivirus
software.<br>
<a moz-do-not-send="true"
href="https://www.avast.com/antivirus" rel="noreferrer"
target="_blank">https://www.avast.com/antivirus</a><br>
<br>
</span>
<div class="HOEnZb">
<div class="h5">_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
</body>
</html>