<html xmlns:v="urn:schemas-microsoft-com:vml" 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="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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.m-5002598658179029118m5493105137021472549apple-converted-space
{mso-style-name:m_-5002598658179029118m_5493105137021472549apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:17316676;
mso-list-template-ids:-1671386308;}
@list l0:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1211915252;
mso-list-template-ids:-406144140;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks for the clarification, Alex. I understand better now how the Whois conflicts with law procedure got dragged into the discussion.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">That being said, I don’t think I can agree with your position. You state that “all obligations are subject to applicable law” but you are afraid that explicitly
stating that language somehow empowers “one party” to decide for themselves what applicable laws require? I think that logically, that’s a non sequitur, and practically, the fear is completely unfounded. ICANN compliance can go after anyone who doesn’t comply
with their contracts. A registrar or registry who thought ICANN obligations forced them to break the law would have to go through some kind of a process to demonstrate how applicable law prevented them from doing so. That process would not necessarily have
to be the old, and defunct Whois conflicts with law procedure. I don’t see how including that language allows anyone to circumvent anything.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">--MM<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Alex Deacon [mailto:alex@colevalleyconsulting.com]
<br>
<b>Sent:</b> Tuesday, August 21, 2018 6:23 PM<br>
<b>To:</b> Mueller, Milton L <milton@gatech.edu><br>
<b>Cc:</b> Mark Svancarek (CELA) <marksv@microsoft.com>; icann@ferdeline.com; gnso-epdp-team@icann.org<br>
<b>Subject:</b> Re: [Gnso-epdp-team] ICANN Procedure for Handling WHOIS Conflicts with Privacy Law<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:black">Hi Milton, </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;background:white">To be clear the point of my comment on the call this morning wasn't that the WHOIS conflicts procedure was somehow relevant to our ePDP, but that we need to rework the text currently in Temp Spec
Appendix C.1 so what ends up in our final report so it doesn't create uncertainty or a mechanism to sidestep/avoid existing policy. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black;background:white">"IPC agrees with the bulk of this section but strongly disagrees with the lead in language to this section, which makes the obligations subject to applicable laws.
All obligations are subject to applicable laws, but for the sake of certainty, it is important that the obligations be clear and certain, and not subject to any one party’s view of what applicable laws require. There is an existing consensus policy and Process
to govern conflicts between WHOIS obligations and National Data Protection Laws, and that will govern dealing with any conflict between those laws and such obligations. The language above appears to allow circumvention of that policy and process, and creates
uncertainty. </span><span style="font-family:"Arial",sans-serif;color:black">Therefore, in Section 1 the phrase “except as required by applicable laws and regulations” should be deleted, as it is unnecessary."</span><o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;background:white">Alex</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Aug 21, 2018 at 2:36 PM Mueller, Milton L <<a href="mailto:milton@gatech.edu" target="_blank">milton@gatech.edu</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Actually Mark, Ayden is correct and yours is a misreading. You are confusing the RAA’s Data Retention Waiver Process with the Handling Whois Conflicts
with Law procedure. They are, as your colleague says, “similar” in intent, but they are not the same. One is in the RAA, the other is not. So Ayden and I are correct, the Whois process has never been used; and your colleague is correct, the other procedure
has been used 35 times. </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Having established some facts, it might be useful to back up and ask what this discussion is about and why it is relevant. In my opinion, this discussion
is only relevant because some people seem to be suggesting that the Whois Conflicts with Law procedure can somehow rescue ICANN from the need to implement or revise the temp spec. If that is not your argument, and I have misinterpreted the significance of
this discussion, then we can all save a lot of effort if you can explain why you think either the Whois Conflict w Law Procedure or the Data Retention Waiver Process are relevant to our ePDP.
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">--MM</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> Gnso-epdp-team [mailto:<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank">gnso-epdp-team-bounces@icann.org</a>]
<b>On Behalf Of </b>Mark Svancarek (CELA) via Gnso-epdp-team<br>
<b>Sent:</b> Tuesday, August 21, 2018 5:16 PM<br>
<b>To:</b> Ayden Férdeline <<a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a>>;
<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-epdp-team] ICANN Procedure for Handling WHOIS Conflicts with Privacy Law<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I think that’s a misreading, sorry. It seems that35 waivers have been granted in 5 years.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Here’s a clarification from Steve (posting on his behalf since he’s an alternate):<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
If we read a little further into that <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fen%2Fsystem%2Ffiles%2Ffiles%2Fwhois-privacy-conflicts-procedure-03may17-en.pdf&data=02%7C01%7Cmarksv%40microsoft.com%7Cc160deec3036483229ce08d607aa6194%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636704825701106839&sdata=8Zfl0MG%2F6e3J%2F1ewA7EcBULz%2BB%2B0ITF8v3zzM90JT5k%3D&reserved=0" target="_blank">
May-2017 staff report</a>, you’ll see that 35 registrars used a process similar to the Whois Conflicts policy to obtain waivers to contract requirements about retaining registrant data – based on applicable privacy laws (see excerpt from staff report below).<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
It’s unfortunate we diverted today’s discussion the Whois Conflicts Policy, since the wide use of ICANN’s Data Retention Waiver Process is sufficient to explain the point we made about TempSpec Appendix C “Data Processing Requirements”.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
That is, we should rely on ICANN policy and processes to grant a waiver if/when applicable law conflicts with registrant data requirements in Registry and registrar agreements. But look at the first line of TempSpec App C.1 “Principles for Processing”:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in">
“Each Controller will observe the following principles to govern its Processing of Personal Data contained in Registration Data,
<i>except as required by applicable laws or regulations</i>”. (italics added)<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
That TempSpec <i>text</i> could imply that each registrar and registry can decide on its own to ignore any principles for processing – without first obtaining a waiver of the contractual requirement from ICANN.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Here’s that excerpt from that <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fen%2Fsystem%2Ffiles%2Ffiles%2Fwhois-privacy-conflicts-procedure-03may17-en.pdf&data=02%7C01%7Cmarksv%40microsoft.com%7Cc160deec3036483229ce08d607aa6194%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636704825701106839&sdata=8Zfl0MG%2F6e3J%2F1ewA7EcBULz%2BB%2B0ITF8v3zzM90JT5k%3D&reserved=0" target="_blank">
May-2017 staff report</a>, showing that 35 registrars have obtained waivers to contract requirements about retaining registrant data – based on applicable privacy laws:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p style="margin-left:1.0in"><b><i><span style="color:#4C7FBC">The 2013 Registrar Accreditation Agreement (“RAA”) Data Retention Waiver Process
</span></i></b><o:p></o:p></p>
<p style="margin-left:1.0in">Under this <span style="color:#0260BF">Requests process</span>, a registrar may request a compliance waiver of the data retention requirements, by presenting ICANN with a written opinion from a nationally recognized law firm, or
ruling or written guidance from a government body that states that collecting or retaining one or more data elements in the manner required by the specification violates applicable law. A general assertion that the data collection and Data Retention Specification
requirements are unlawful is not sufficient. Rather, the waiver request must specify the applicable law, the specific allegedly offending data collection and/or retention requirement(s), and the manner in which the collection and/or retention violates the
law. <o:p></o:p></p>
<p style="margin-left:1.0in">This specificity helps ICANN to determine the appropriate limitations on the scope and duration of data collection and retention requirements when granting the waiver. This also helps ICANN balance the interests of the registrar,
governments, and the broader Internet community when considering granting such waivers. In addition, if ICANN has previously waived compliance with the requirements for a registrar located in the same jurisdiction and the applying registrar is subject to the
same applicable law, the registrar may request the same waiver. <o:p></o:p></p>
<p style="margin-left:1.0in">The 2013 RAA calls for ICANN and the registrar to discuss data retention waiver requests in good faith in an effort to reach a mutually acceptable resolution. The Data Retention Specification contemplates potential future modifications
to the Whois Procedure in section 2 of the RAA.<span style="font-size:8.0pt">4 </span>
Because each country may interpret its data privacy requirements differently, ICANN is working through each of the submitted requests country-by-country.
<o:p></o:p></p>
<p style="margin-left:1.0in">The complexity and diversity of national privacy laws has resulted in considerable investments of time and resources by ICANN and registrars alike. In countries with data privacy laws applicable to registrars, ICANN has found that
restrictions generally permit the retention of registration data, but only for legitimate purposes, and for a period no longer than is necessary for the purposes for which the data were collected or for which they are further processed. What constitutes a
legitimate purpose and how long data can be retained are complicated questions, and the answers may vary from one country to the next, even within the EU.
<o:p></o:p></p>
<p style="margin-left:1.0in"><span style="background:yellow">As of April 2017, a total of 35 Data Retention Waivers were granted to registrars.</span>
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>Ayden Férdeline<br>
<b>Sent:</b> Tuesday, August 21, 2018 12:56<br>
<b>To:</b> <a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-epdp-team] ICANN Procedure for Handling WHOIS Conflicts with Privacy Law<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This statement seems to support Milton’s claim on today’s call that the WHOIS Conflicts with Privacy Law procedure has never been invoked:<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On 21 Aug 2018, at 20:55, Marika Konings <<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Given that to date no registrar or registry operator has formally invoked the Whois Procedure<o:p></o:p></p>
</div>
</blockquote>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Kind regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Ayden Férdeline<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On 21 Aug 2018, at 20:55, Marika Konings <<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Dear All,<span class="m-5002598658179029118m5493105137021472549apple-converted-space"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Per the action item from today’s meeting, please find attached the staff assessment and next steps report on the Revised ICANN Procedure for Handling WHOIS Conflicts with Privacy
Law which was published in May 2017. As there were specific questions in relation to the origin of the procedure, I’ve excerpted the background section from this document below. As noted, the GNSO Council has already agreed to form an Implementation Advisory
Group to review the procedure and adopted a charter for this effort in February of this year (see<span class="m-5002598658179029118m5493105137021472549apple-converted-space"> </span><a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgnso.icann.org%2Fen%2Fcouncil%2Fresolutions%23201802&data=02%7C01%7Cmarksv%40microsoft.com%7C2158f84e56f24e1e26a108d607a03173%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636704781952399814&sdata=WJqXY9ZS9EFT1m1avYwLzQHbT3o6l2AAon%2BU%2FoeY7j0%3D&reserved=0" target="_blank"><span style="color:#954F72">https://gnso.icann.org/en/council/resolutions#201802</span></a>).
However, due to workload issues and the pending EPDP, the Council delayed the call for volunteers and agreed during its most recent meeting to decide when the call for volunteers should be launched following the publication of the Initial Report on the Temporary
Specification by the EPDP Team. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Caitlin, Berry and Marika<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">============================<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>Background</b><span class="m-5002598658179029118m5493105137021472549apple-converted-space"> </span>(from<span class="m-5002598658179029118m5493105137021472549apple-converted-space"> </span><a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fen%2Fsystem%2Ffiles%2Ffiles%2Fwhois-privacy-conflicts-procedure-03may17-en.pdf&data=02%7C01%7Cmarksv%40microsoft.com%7C2158f84e56f24e1e26a108d607a03173%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636704781952399814&sdata=Gk6O8uK6dnajSzeV8xv%2F3rUx6fm5RXETNHjWMVjm%2FCg%3D&reserved=0" target="_blank"><span style="color:#954F72">https://www.icann.org/en/system/files/files/whois-privacy-conflicts-procedure-03may17-en.pdf</span></a>).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">In November 2005, the GNSO concluded<span class="m-5002598658179029118m5493105137021472549apple-converted-space"> </span><a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgnso.icann.org%2Fen%2Fissues%2Fwhois-privacy%2Fcouncil-rpt-18jan06.htm&data=02%7C01%7Cmarksv%40microsoft.com%7C2158f84e56f24e1e26a108d607a03173%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636704781952409822&sdata=Vc7EwlUp9RjKtSOSRtAvcXfXuQhAzpduNwCo9bRHZA4%3D&reserved=0" target="_blank"><span style="color:#954F72">a
policy development process</span></a><span class="m-5002598658179029118m5493105137021472549apple-converted-space"> </span>(PDP) on Whois conflicts with privacy law which recommended that “In order to facilitate reconciliation of any conflicts between local/national
mandatory privacy laws or regulations and applicable provisions of the ICANN contract regarding the collection, display and distribution of personal data via the gTLD Whois service, ICANN should:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
Develop and publicly document a Procedure for dealing with the situation in which a registrar or registry can credibly demonstrate that it is legally prevented by local/national privacy laws or regulations from fully complying with applicable provisions of
its ICANN contract regarding the collection, display and distribution of personal data via Whois.<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
Create goals for the procedure which include:<o:p></o:p></li></ol>
<ol start="2" type="1">
<ol start="1" type="a">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
Ensuring that ICANN staff is informed of a conflict at the earliest appropriate juncture;<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
Resolving the conflict, if possible, in a manner conducive to ICANN's Mission, applicable Core Values, and the stability and uniformity of the Whois system;<span class="m-5002598658179029118m5493105137021472549apple-converted-space"> </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
Providing a mechanism for the recognition, if appropriate, in circumstances where the conflict cannot be otherwise resolved, of an exception to contractual obligations to those registries/registrars to which the specific conflict applies with regard to collection,
display and distribution of personally identifiable data via Whois; and<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
Preserving sufficient flexibility for ICANN staff to respond to particular factual situations as they arise”.<o:p></o:p></li></ol>
</ol>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The ICANN Board of Directors adopted the recommendations in May 2006 and directed staff to develop such a Procedure. A draft Procedure was posted for public comment, and input was
specifically solicited from the Governmental Advisory Committee (GAC). The GAC recommended adding a provision, which was included as section 1.4 in the procedure, urging a registrar or registry to work with relevant national governments to ensure adherence
to domestic and international law, as well as applicable international conventions.<span class="m-5002598658179029118m5493105137021472549apple-converted-space"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">If the Whois requirements require changes that ICANN determines prevent compliance with contractual Whois obligations, ICANN may refrain, on a provisional basis, from taking enforcement
action for non-compliance, while ICANN prepares a public report and recommendation and submits it to the ICANN Board for a decision. Given that to date no registrar or registry operator has formally invoked the Whois Procedure, and yet numerous concerns have
arisen from contracted parties and the wider community, ICANN launched a review in 2014, as provided in the Whois Procedure’s final clause.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><i>Marika Konings</i></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i>Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i>Email:<span class="m-5002598658179029118m5493105137021472549apple-converted-space"> </span></i><a href="mailto:marika.konings@icann.org" target="_blank"><i><span style="color:#0563C1">marika.konings@icann.org</span></i></a><i> </i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i> </i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i>Follow the GNSO via Twitter @ICANN_GNSO</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i>Find out more about the GNSO by taking our </i><a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flearn.icann.org%2Fcourses%2Fgnso&data=02%7C01%7Cmarksv%40microsoft.com%7C2158f84e56f24e1e26a108d607a03173%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636704781952409822&sdata=IwV%2FoVI35K1EpCsySXi%2ByVQChRcCkxVZFMjmgqyureM%3D&reserved=0" target="_blank"><i><span style="color:#0563C1">interactive
courses</span></i></a><i> and visiting the </i><a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgnso.icann.org%2Fsites%2Fgnso.icann.org%2Ffiles%2Fgnso%2Fpresentations%2Fpolicy-efforts.htm%23newcomers&data=02%7C01%7Cmarksv%40microsoft.com%7C2158f84e56f24e1e26a108d607a03173%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636704781952419826&sdata=oJHiPRaRApE8LTrNGVIfVKoEUFwgo1xunGCxfTFi4q8%3D&reserved=0" target="_blank"><i><span style="color:#0563C1">GNSO
Newcomer pages</span></i></a><i>. </i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><whois-privacy-conflicts-procedure-03may17-en.pdf><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Gnso-epdp-team mailing list<br>
<a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">___________<o:p></o:p></p>
<div>
<p class="MsoNormal"><b>Alex Deacon</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Cole Valley Consulting<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:alex@colevalleyconsulting.com" target="_blank">alex@colevalleyconsulting.com</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">+1.415.488.6009<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>