<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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">As discussed on today’s BC call, we submitted 4 process questions to ICANN today, regarding the proposed models for GDPR compliance. (see attached and below)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks to volunteers who quickly drafted these questions: Margie Milam, Mary Ellen Callahan, Alex Deacon, Tim Chen, and Faisal Shah.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We will also be drafting comments on the models before 29-Jan, and these will be circulated for BC member review.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">Date: </span></b><span style="color:black">Thursday, January 18, 2018 at 6:09 PM<br>
<b>To: </b>"gdpr@icann.org" <gdpr@icann.org><br>
<b>Subject: </b>Process questions from the Business Constituency (BC), regarding model for GDPR compliance<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal">The BC appreciates the opportunity to provide comment on ICANN’s proposed models for compliance with the European Union’s General Data Protection Regulation (GDPR). We thank the community for the immense efforts in responding to ICANN’s
call for Community-Proposed Models for GDPR Compliance and ICANN org for this opportunity to submit comment and begin a more robust discussion on this important topic.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Our feedback will be divided into two discrete areas: First, procedural questions, to be followed by a separate submission regarding substantive observations and comments on ICANN’s proposed models.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The BC would appreciate ICANN org’s detailed replies to these questions, which will help clarify our understanding of how ICANN arrived at
<a href="https://www.icann.org/en/system/files/files/interim-models-gdpr-compliance-12jan18-en.pdf">
these proposals</a> and enable and inform more precise feedback from us: <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">1. In publishing its <a href="https://www.icann.org/en/system/files/files/interim-models-gdpr-compliance-12jan18-en.pdf">ICANN-Proposed Compliance Models for Community Discussion</a>, ICANN org states:<span style="font-family:"MS Mincho",serif">
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">“We are seeking your input on the proposals. From that input either variations or modifications to one of these models will be identified at the end of January for the path forward. To ensure we reach this goal,
we need your feedback by 29 January 2018.” <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">From this, it is unclear whether the ICANN community is meant to provide feedback to ICANN’s three models only, or also to the additional five community-proposed models for GDPR compliance. The BC would like
additional clarity on whether there will be any evaluation of the five community-proposed models through this current process. If not, will these be reviewed and considered by both ICANN and the community?
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">2. Contrary to stated ICANN processes and procedures ICANN org has opened a short window of time for comments (17 days), and comments don’t appear to be publicly displayed. Will ICANN both extend the comment deadline and make comments
publicly accessible? <span style="font-family:"MS Mincho",serif">
</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">3. As ICANN org states, “one of these models will be identified at the end of January for the path forward.” Comments are due January 29, so is ICANN assuming it will take only 2 days to thoroughly consider community input before it makes
a final decision?<span style="font-family:"MS Mincho",serif">
</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">4. In describing the approach for developing its proposed interim compliance model, ICANN org states that:<span style="font-family:"MS Mincho",serif">
</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i>“[t]he selected model will not replace the multistakeholder policy development and implementation activities that are underway, including ... updates to ICANN’s Procedure for Handling WHOIS Conflicts with Privacy
Law …”</i><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">The BC requests additional clarification on what development and/or implementation activities are underway for this cited policy. And, more importantly, we request an explanation as to why no part of this policy
has been followed by ICANN to-date in addressing compliance with the GDPR.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The BC looks forward to your prompt response on our questions, preferably in advance of the January 29th deadline for comments on the proposed models.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Sincerely,<o:p></o:p></p>
<p class="MsoNormal">Steve DelBianco<o:p></o:p></p>
<p class="MsoNormal">Vice chair for policy coordination<o:p></o:p></p>
<p class="MsoNormal">ICANN Business Constituency<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>