<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<p>I am pretty much aligned with Kris’ position here, treating the
GDPR as a sort-of baseline as this Working Group does its work. I
would like to step back a bit and put this emerging RDS/GDPR
policy intersection into a wider context.</p>
<p>ICANN’s policies and practices for security and stability of the
Internet, its operational relations with its contracted parties,
and its multistakeholder policy making process will have to come
to terms with the fact that much of the new policy affecting the
Internet will come from the individual and multilateral expression
of national interests and national concerns outside ICANN’s remit.</p>
<p>The old worry that the ITU, the UN, or some other multilateral
organization, might “take over” the management and policy
development for the security and stability of the Internet has to
be replaced by an understanding that the Internet ‘rights” policy
agenda have gone well beyond a focus on the issues that fall
within ICANN’s remit. As policy issues such as GDPR mature,
ICANN’s policy remit will represent a smaller part of the global
Internet policy agenda, and it scope for policy will be affected.
<br>
</p>
<p>This does not mean that ICANN should expand its policy remit. It
does mean that ICANN’s policy process and operational relations,
especially with contracted parties, will have to factor in what is
happening in other national and multilateral policy arenas. It may
also mean that ICANN as a whole may want to participate in some
fashion, as a stakeholder in its own right, in the non-ICANN part
of the global Internet policy agenda. Its various constituencies
are, of course, already involved. <br>
</p>
<p>The current RDS/GDPR policy intersection, and this episode around
ICANN Board conversations with the data privacy people, <b><i>suggest
that ICANN, and its constituencies should open up an internal
dialogue</i></b> around how ICANN can, should, or should not,
handle engagement with policy issues outside ICANN’s remit,
especially when those policies will have impacts on the context in
which ICANN fashions policy within its own remit. <br>
</p>
<p>Sam L<br>
<br>
</p>
<br>
<div class="moz-cite-prefix">On 9/23/2017 8:10 AM, Kris Seeburn
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:FF22049E-21AC-4F0D-92DF-C6D7D98C010D@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Yes Ayden that’s my view as well and many will folllow GDPR as
baseline. Most of the new privacy acts or bills or updated acts
are laying down the same kind of deterrent in place.
<div><br>
</div>
<div>So let’s focus at GDPR as baseline and apply it as general
rule of thumb. <br>
<div>
<div><br>
<div id="AppleMailSignature">Kris</div>
<div><br>
On 23 Sep 2017, at 15:32, Ayden Férdeline <<a
href="mailto:icann@ferdeline.com" moz-do-not-send="true">icann@ferdeline.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>Hi Kris,<br>
</div>
<div><br>
</div>
<div>I think I am largely in agreement with what you are
saying. It is my view, and I think you are saying that
it is yours too, that GDPR will be the most important
influence in the ongoing development and harmonisation
of global privacy standards. So GDPR is certainly
something that we as a Working Group need to be paying
attention to.<br>
</div>
<div><br>
</div>
<div>After all, over 100 countries now have data
protection laws, and given that many of these were
modelled after the European Union’s 1995 Data
Protection Directive, a desire to emulate best
practices could very well see these laws updated,
inspired, or influenced by GDPR in the near future...<br>
</div>
<div><br>
</div>
<div>Best wishes,<br>
</div>
<div><br>
</div>
<div class="protonmail_signature_block">
<div class="protonmail_signature_block-user">
<div>Ayden Férdeline<br>
</div>
<div><a href="http://www.linkedin.com/in/ferdeline"
title="http://www.linkedin.com/in/ferdeline"
moz-do-not-send="true">linkedin.com/in/ferdeline</a><br>
</div>
</div>
<div class="protonmail_signature_block-proton
protonmail_signature_block-empty"><br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>