<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=us-ascii">
<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:11.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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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;}
--></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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attached and set out below is the RySG ePDP Team’s feedback on the proposed approach.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-*-<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#333333">The Registries Stakeholder Group (RySG) ePDP Team (“RySG”) submits its feedback on the two draft approaches to Phase II of the EPDP. The RySG appreciates the work by Janis Karklins and ICANN Staff reflected
in these approaches. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#333333"><o:p> </o:p></span></p>
<p class="MsoNormal">The RySG disagrees with the characterization of the EPDP Team's objective on several grounds. First, the EPDP Team's objective is to develop policy recommendations, not necessarily "rules and requirements." Second, those policy recommendations
pertain to "a standardized model for lawful disclosure of non-public Registration Data," as set forth in Phase I, Recommendation 3. Third, the current statement of the objective presupposes that data SHALL be shared with third parties, which is incorrect and
inconsistent with GDPR. <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><o:p> </o:p></p>
<p class="MsoNormal">The RySG agrees that the development of policy recommendations for a standardized model for lawful disclosure of non-public Registration Data should be agnostic to the modalities of that model. The distinction between a centralized and
decentralized model, which apparently has disappeared from the recent draft, is an important one and the RySG believes it is critical that the EPDP Team consider both.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The RySG agrees that the EPDP Team as a whole should engage with ICANN Org on the development of policy questions that will help inform the discussions with DPAs. However, although ICANN’s engagement with the DPAs may lead to further clarity,
the EPDP should not defer policy development pending consultation and engagement with the DPAs/EDPB. We should proceed with our task, implementing the data protection principles of both Privacy by Default and Privacy by Design. The EPDP should, when appropriate,
rely upon the legal constructs whereby we can engage the DPAs as part of our policy development process (e.g. Art 36 prior consultations and Data Protection Impact Assessments under Section 3 of the GDPR.)
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The RySG appreciates the urgency in completing this process, but the effects of enhanced workloads and tightened timelines do not result in a refined end product, as was patently clear from the closing stages of Phase I. The RySG does not
support parallel work streams. The proposed working method increases the workloads of the team members who must participate in both workstreams, and provides a false impression of covering more ground.
<span style="color:#3C4043;background:white;mso-highlight:white">The proposed parallel work streams will lose the expertise of non-participating EPDP Team members, expedite the onset of Team fatigue, and ultimately be counterproductive.</span>
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Many Phase 1 items earmarked for WS 2 will materially affect the direction, scope and considerations of WS 1. The 2 streams contain some large interdependencies (e.g Legal v Natural), which will likely lead to reopening or re-assessment
of work items. Such reopening or re-assessment will lead to frustration and delay. Rather than achieve the goal of completing Phase II work sooner the two phased approach is likely to cause delays to the overall timeline.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Further, the ICANN Board's recent decision to not adopt Recommendation 1, Purpose 2 effectively means that the EPDP Team will need to revisit it. Any change that results from re-opening the discussion of Purpose 2 is expected to impact
both work streams and thus impact the overall schedule.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It is unclear why the quote from the European Commission’s May 3, 2019 letter is a newly added element to the proposed work approach.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The RySG supports using clear terminology in this process to set reasonable expectations in the outcome and to ensure clear and efficient communication and work. The RySG supports ensuring that the focus of Phase II release of non-public
Registration Data be considered “DISCLOSURE,” consistent with Recommendation 18 of the Phase 1 final report, whereby a clear distinction between “Access” and “Disclosure” was drawn by the team.
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"> <o:p></o:p></p>
<p class="MsoNormal">The RySG recognizes the need for timelines, but those timelines must be realistic for the task -- not arbitrary and based on external pressures. The proposed approach does not seem unreasonable at this early stage, but seems target-based
rather than based on any actual apparent assessment or even any measurable assumptions. We would like to better understand the underlying data and assumptions that led to this timeline.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><o:p> </o:p></p>
<p class="MsoNormal">The RySG is very supportive of setting a realistic target date, so long as such a timeline exists with built in “check-in” points during the intervening period. Such “check-ins” should provide the opportunity for the team to objectively
reassess practical considerations of any experienced difficulties, review progress, and consider any additional complications, additions or other factors. Such check-ins should then result in a reasonable readjustment, where necessary, of our timeline.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With regard to the timeline, it is not clear why the timelines for the two WS 1 bullets -- “Deliberation on issues outlined on Slide 4” and “Coordination with Org on UAM questions” do not end simultaneously and why the latter ends 3 months
before the former. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-*-<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Kristina Rosette<o:p></o:p></p>
<p class="MsoNormal">Senior Corporate Counsel, IP – Domains<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:rosettek@amazon.com">rosettek@amazon.com</a> | 703.407.1354<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>