<div dir="ltr">Who within ICANN is taking the lead on this? The CEO must be getting someone to do these drafts which are full of holes. You can make a bad argument but it should be tight.<div>best</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 13, 2018 at 1:55 PM, Stephanie Perrin <span dir="ltr"><<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.utoronto.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">I think we are all
scratching our heads trying to figure out the strategy here
Dorothy...it is certainly true that the Governmental Advisory
Committee (GAC) continues to push for status quo, and
obviously the business community including the intellectual
property constituency...but at some point ICANN needs to wake
up and smell the coffee. I am busy working on our next letter
to the Article 29 Working Party, with our reflections on
recent proposals, and in response to their excellent letter.
Any suggestions would be welcome....I am wondering if a list
of proposed questions to ICANN might be a good idea. In the
meantime, Michele Neylon of the Registrars Stakeholders Group
has written an excellent blog that pretty much sums up the
situation, available here
<a class="m_-5024156065813537578moz-txt-link-freetext" href="https://blacknight.blog/game-over-for-public-whois-article-29-gives-icann-the-advice-it-asked-for.html" target="_blank">https://blacknight.blog/game-<wbr>over-for-public-whois-article-<wbr>29-gives-icann-the-advice-it-<wbr>asked-for.html</a>
.</font></font></p><span class="HOEnZb"><font color="#888888">
<p><font size="+1"><font face="Lucida Grande">Stephanie Perrin</font></font></p>
</font></span><p><font size="+1"><font face="Lucida Grande">PS I agree with Colin
and Michael that the bit about fake news is offensive, and
will deal with it. We included a fairly lengthy piece on
protection of journalists and political speakers (as well as
others) in our March letter but the idea that WHOIS actually
protects against fake news is backwards and needs to be
addressed.</font></font><br>
</p><div><div class="h5">
<div class="m_-5024156065813537578moz-cite-prefix">On 2018-04-13 08:45, dorothy g wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">They have well-qualified people on the staff. It
seems they are not leveraging their resources or the good will
of the stakeholder groups. For example, Stephanie has given
excellent analysis. Perhaps there is something going on here, a
wider power play that we do not grasp?
<div>best</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Apr 13, 2018 at 12:30 PM,
Michael Karanicolas <span dir="ltr"><<a href="mailto:mkaranicolas@gmail.com" target="_blank">mkaranicolas@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Yes - the inclusion of that last bullet is
particularly egregious, when you consider that anti-fake
news laws are used as a hammer around the world to <a href="https://cpj.org/reports/2017/12/journalists-prison-jail-record-number-turkey-china-egypt.php" target="_blank">silence critical
journalists</a>. Very disturbing to see them pointing to
that as something they feel driven to help facilitate.
<div><br>
</div>
<div>The idea of them suing for a moratorium is also
pretty ludicrous. There was a two year implementation
period - whose fault is it that this was left to the
last minute?</div>
<span class="m_-5024156065813537578HOEnZb"><font color="#888888">
<div><br>
</div>
<div>Michael</div>
</font></span></div>
<div class="m_-5024156065813537578HOEnZb">
<div class="m_-5024156065813537578h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Apr 13, 2018 at 9:00
AM, Collin Kurre <span dir="ltr"><<a href="mailto:collin@article19.org" target="_blank">collin@article19.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">This is a topic
that has the potential to draw the attention of
actors with little to no knowledge about ICANN’s
structure and remit. With that in mind, one of
the (many) things that I find problematic about
this response the imprecision in language,
particularly in the bulleted list
of “potentially adverse scenarios”.
<div><br>
</div>
<div>Take the last point for example: that a
fragmented WHOIS would “make it significantly
harder to identify fake news and impact the
ability to take action against bad actors.”
Who is the agent of action here, real or
perceived? What is the role of WHOIS and ICANN
in determining or rectifying fake news? The
lack of clarity could easily be interpreted as
an invitation to actors seeking to leverage
the DNS for content regulation. </div>
<div><br>
</div>
<div>Disappointing to see such a knee-jerk
response to Article 29’s thorough
contribution.</div>
<div><br>
</div>
<div>Best,</div>
<div>Collin Kurre</div>
<div>
<div class="m_-5024156065813537578m_-4989555253122485841h5"><br>
<div>
<blockquote type="cite">
<div>On Apr 12, 2018, at 11:06 PM,
farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" target="_blank">farzaneh.badii@GMAIL.COM</a>>
wrote:</div>
<br class="m_-5024156065813537578m_-4989555253122485841m_7134828716629748691Apple-interchange-newline">
<div>
<div dir="ltr">
<div class="gmail_default" style="font-family:verdana,sans-serif">And
here is ICANN's response to
Article 29 WP. </div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">Farzaneh<br>
</div>
<br>
<div class="gmail_quote"><br>
<div class="gmail_default" style="font-family:verdana,sans-serif">----</div>
<br>
<div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
<div class="m_-5024156065813537578m_-4989555253122485841m_7134828716629748691m_5524904452103774945WordSection1"><br>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Please
see our <a href="https://www.icann.org/news/announcement-2018-04-12-en" target="_blank">most recent announcement</a> r<wbr>egarding
the <a href="https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-11apr18-en.pdf" target="_blank">letter</a> from
the Article 29 Working
Party. The letter was
published on our <a href="https://www.icann.org/resources/pages/correspondence" target="_blank">main
Correspondence page</a>,
and linked to our <a href="https://www.icann.org/dataprotectionprivacy" target="_blank">Data
Protection/Privacy page</a>.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">------------------------------<wbr>----</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><b>ICANN
Receives Data
Protection/Privacy
Guidance from Article 29
Working Party</b></p>
<p class="MsoNormal">LOS
ANGELES – 12 April 2018 –
The Internet Corporation for
Assigned Names and Numbers
("ICANN") today announced
that it has received a
<a href="https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-11apr18-en.pdf" target="_blank">
letter from the Article 29
Working Party (WP29)</a>
[PDF, 400 KB] that provides
guidance on the European
Union's General Data
Protection Regulation (GDPR)
and its impact on the
collection, retention and
publication of domain name
registration data and the
WHOIS system. ICANN
organization’s response to
the letter from the Article
29 Working Party will be
published shortly
<a href="https://www.icann.org/resources/pages/correspondence" target="_blank">here</a>.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">“We
appreciate the guidance
provided by the Article 29
Working Party on this
important issue and have
accepted an invitation to
meet with the WP29
Technology Subgroup in
Brussels on 23 April for
further discussions,” said
Göran Marby, ICANN president
and CEO. “However, we are
disappointed that the letter
does not mention our request
for a moratorium on
enforcement of the law until
we implement a model.
Without a moratorium on
enforcement, WHOIS will
become fragmented and we
must take steps to mitigate
this issue. As such, we are
studying all available
remedies, including legal
action in Europe to clarify
our ability to continue to
properly coordinate this
important global information
resource. We will provide
more information in the
coming days.”</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">A
moratorium on enforcement
action by DPAs would
potentially allow for the
introduction of an
agreed-upon accreditation
model and for the registries
and registrars to implement
the accreditation model in
conjunction with the
measures in the agreed final
interim compliance model. It
will also allow for
reconciliation between the
advice ICANN has received
from its Governmental
Advisory Committee (GAC) and
the Article 29 Working
Party. Unless there is a
moratorium, we may no longer
be able to give instructions
to the contracted parties
through our agreements to
maintain WHOIS. Without
resolution of these issues,
the WHOIS system will become
fragmented until the interim
compliance model and the
accreditation model are
implemented.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">A
fragmented WHOIS would no
longer employ a common
framework for generic
top-level domain (gTLD)
registration directory
services. Registries and
registrars would likely
implement varying levels of
access to data depending on
their interpretations of the
law.</p>
<p class="MsoNormal">“In
parallel, we will carefully
consider this advice, along
with all of the input we
have received from the
multistakeholder community,
before making changes to the
current iteration of the
<a href="https://www.icann.org/en/system/files/files/gdpr-compliance-interim-model-08mar18-en.pdf" target="_blank">
proposed interim model</a>,”
Marby continued. “As a part
of this, we will explore all
options as we continue
dialogues with DPAs and the
interested parties that
comprise the
multistakeholder community.”</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">It’s
important to balance the
right to privacy with the
need for information. While
ICANN recognizes the
importance of the GDPR and
its goal of protecting
personal data, parts of the
ICANN community have noted
the negative impact of a
fragmented WHOIS. For
example, it will hinder the
ability of law enforcement
to get important information
and the anti-spam community
to help ensure the Internet
protects end-users. It will
also:</p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="margin-left:0in">Protect
the identity of criminals
who may register hundreds
of domain names
specifically for use in
cyberattacks;</li>
<li class="MsoNormal" style="margin-left:0in">Hamper
the ability of consumer
protection agencies who
track the traffic patterns
of illicit businesses;</li>
<li class="MsoNormal" style="margin-left:0in">Stymie
trademark holders from
protecting intellectual
property; and</li>
<li class="MsoNormal" style="margin-left:0in">Make
it significantly harder to
identify fake news and
impact the ability to take
action against bad actors.</li>
</ul>
<p class="MsoNormal"> </p>
<p class="MsoNormal">These are
just a few examples from a
long list of potentially
adverse scenarios.</p>
<p class="MsoNormal">Marby
also requested that the DPAs
include ICANN in any
proceedings relating to
WHOIS, and asks that it be
included in all discussions
and actions of the privacy
regulators with the other
WHOIS data controllers. He
also said that ICANN org is
continuing its efforts to
prepare for implementation
of a new model. Additional
information on ICANN’s data
protection/privacy
activities, including legal
analyses, proposed
compliance models, and
community feedback is
published
<a href="https://www.icann.org/dataprotectionprivacy" target="_blank">here</a>.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We
encourage the community to
provide feedback and
continue our dialogues on
future activities. You may
share your views with us via
email at
<a href="mailto:gdpr@icann.org" target="_blank">gdpr@icann.org</a>.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"> <br>
</span></p>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
So-ac-sg-cleaders mailing list<br>
<a href="mailto:So-ac-sg-cleaders@icann.org" target="_blank">So-ac-sg-cleaders@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/so-ac-sg-cleaders</a><br>
<br>
</div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div></div></div>
</blockquote></div><br></div>