<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><a href="https://www.icann.org/news/blog/data-protection-privacy-issues-icann61-wrap-up-and-next-steps">https://www.icann.org/news/blog/data-protection-privacy-issues-icann61-wrap-up-and-next-steps</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Data Protection/Privacy Issues: ICANN61 Wrap-up and Next Steps<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b> ICANN Blog<o:p></o:p></b></p>
<p class="MsoNormal"><b> Author: Göran Marby, President and CEO, ICANN<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I want to thank everyone from across the community who participated in discussions around the ICANN61 meeting on the European Union's General Data Protection Regulation (GDPR) and its impact on registration directory services, as well as
ICANN's contracts. Your contributions have helped advance our work to come into compliance with the law.</p>
<p class="MsoNormal">As I noted during ICANN61, we have provided representatives of the Article 29 Working Party with an initial approach to our plan of action, by sharing our "Interim Model for Compliance with ICANN Agreements and Policies in Relation to the
European Union's General Data Protection Regulation, (or the "<a href="https://www.icann.org/en/system/files/files/gdpr-compliance-interim-model-08mar18-en.pdf">Cookbook</a>") [PDF, 922 KB]. The Cookbook provides explanation and rationale for the developing
plan of action. The Cookbook also highlighted and requests guidance on some of the key points of divergence within our community. We will continue to seek guidance on those points of divergence and we will add new information we have gained from the discussions
in San Juan in next versions and in our communications with the data protection authorities (DPAs).</p>
<p class="MsoNormal">At the end of March we anticipate having our next interaction with Article 29 representatives since sending them the proposed model. This next stage is critical to determine what appears in the public WHOIS, including what is collected,
escrowed and transferred from registrants to registrars and registries. There are open questions about several elements in the Proposed Interim Model and it's important we determine what are the best ways to answer those in a final model.</p>
<p class="MsoNormal">In presenting our plan of action, we want to ensure that access is not lost if an accreditation model is not implemented in time for the GDPR's 25 May 2018 enforcement deadline. We will also highlight again, the importance of additional
time to implement our solution. We are very aware of the need for additional time beyond May 2018 to implement a compliance model by which accredited users with a legitimate purpose may gain access to non-public WHOIS data. Feedback may also allow further
refinement of the accreditation model.</p>
<p class="MsoNormal">We will share any information that we gain from our next meeting with you by posting it to our Data Protection/Privacy Issues correspondence
<a href="https://www.icann.org/resources/pages/data-protection-correspondence-2017-12-08-en">
page</a>.</p>
<p class="MsoNormal">I am grateful for the contribution and spirit of collaboration that I have seen within so many constituencies and stakeholder groups. As noted in my previous
<a href="https://www.icann.org/news/blog/data-protection-privacy-issues-update-more-details-published-on-icann-proposed-interim-model">
blog</a>, ICANN org is committed to finding a single, unified solution for use by all parties. The full community's engagement in this public discussion will help ensure all viewpoints are reflected as we develop a plan of action and a final interim model.
In addition, as I noted several times during ICANN61, you can also reach out directly to your DPAs, in particular where you can provide additional information relating to these points of divergence and the impact of not having a plan of action in place by
the upcoming May deadlines.</p>
<p class="MsoNormal">We urge those working in parallel on the accreditation model, as well as those working with our Global Domains Division on technical implementation and a timeline, to continue to share their work through the
<a href="mailto:gdpr@icann.org">gdpr@icann.org</a> address, and with each other, while heeding the advice that may come from relevant stakeholders. To ensure a unified WHOIS, it is important we work together as ICANN settles on a final model.</p>
<p class="MsoNormal">We welcome all feedback on the Proposed Interim Model, the development of an implementation timeline, as well as the accreditation process. Please send your input to
<a href="mailto:gdpr@icann.org">gdpr@icann.org</a> and be sure to review comments received from others in the community
<a href="https://www.icann.org/resources/pages/gdpr-legal-analysis-2017-11-17-en">
here</a>. This is a fast-moving topic, so be sure to follow our Data Protection/Privacy Issues
<a href="https://www.icann.org/dataprotectionprivacy">page</a> for the latest updates.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt">David A. Olive<br>
Senior Vice President<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:9.0pt">Policy Development Support</span><span style="font-size:9.0pt;font-family:"PMingLiU",serif"><br>
</span><span style="font-size:9.0pt">Internet Corporation for Assigned Names and Numbers (ICANN)<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>