<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Long time ago when I was 18, my friend had bought a car which was a big deal at the time and we were going from her parents' place to the university. My friend got distracted, wanting to show me a house in a street, she hit the traffic light and the traffic light broke collapsing over her car and just went blinking orange, green and red at our shocked faces. It was a bizarre feeling. Of course there was serious panic but also there was a very comical moment. The ePDP document with all the colorful comments and messiness gave me a very similar feeling. <br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Now my main points:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">1. We should not accept IPC addition to the mission. Also can we get rid of at a minimum from this paragraph? We are really working on "scope" and "mission" what does it mean at a minimum? is there a good reason it is there? If you don't remove it there is a risk that anything can be thrown at this document: </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="">
<p class="MsoNormal" style="font-family:Calibri,sans-serif;margin:0cm 0cm 10pt;line-height:115%">"This EPDP Team is being chartered to determine, at <u style="">a minimum</u>, if the Temporary Specification for gTLD Registration Data should become an ICANN Consensus Policy. As part of this determination, the EPDP Team is, <u style="">at a minimum</u>, expected to consider the following elements of the Temporary Specification an<span class="gmail-msoIns" style="text-decoration:underline;color:teal"><ins cite="mailto:Stephanie%20Perrin" datetime="2018-07-07T01:59">d</ins></span> answer the following charter questions:<span style="font-size:11pt"></span></p><p class="MsoNormal" style="font-family:Calibri,sans-serif;margin:0cm 0cm 10pt;line-height:115%"><br></p><p class="MsoNormal" style="font-family:Calibri,sans-serif;margin:0cm 0cm 10pt;line-height:115%">2. Purposes for processing data. I am not so sure why Erika has added this question: </p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:115%;font-size:11pt"><i><span style="background:lime"><br></span></i></p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:115%;font-size:11pt"><i><span style="background:lime">a5) </span><span style="background:yellow">How shall legitimacy of collecting data be defined (at least for data from personal data collected from European users)? (proposed addition from Erika Mann) <span></span></span></i></p>
<p></p><p class="MsoNormal" style="font-family:Calibri,sans-serif;margin:0cm 0cm 10pt;line-height:115%;font-size:11pt">I thought legitimacy will be defined in accordance to purpose. Also the mention of "at least for data collected from European users" worries me. </p><p class="MsoNormal" style="font-family:Calibri,sans-serif;margin:0cm 0cm 10pt;line-height:115%;font-size:11pt"><br></p><p class="MsoNormal" style="margin:0cm 0cm 10pt;line-height:115%;font-size:11pt"><span style="font-family:Calibri,sans-serif">- Susan is suggesting to say should any purposes be "added". Sure, we could add that word but it has to be mentioned that according to ICANN purpose and mission, should any data be added.</span><font face="arial, helvetica, sans-serif"> EDPB specifically says <span style="color:rgb(49,49,49);font-size:16px;word-spacing:1px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">that ICANN should not conflate its purpose with the interest of third party</span></font></p><p class="MsoNormal" style="margin:0cm 0cm 10pt;line-height:115%"><font color="#313131" face="arial, helvetica, sans-serif"><span style="word-spacing:1px"><br></span></font></p><p class="MsoNormal" style="margin:0cm 0cm 10pt;line-height:115%"><font color="#313131" face="arial, helvetica, sans-serif"><span style="word-spacing:1px">3. I see that now even the phase 1, phase 2 has been removed and access has become a part of EPDP. Can we get rid of accreditation and just discuss access at this EPDP? I see that Susan Kawaguchi supports this ...</span></font></p><p class="MsoNormal" style="margin:0cm 0cm 10pt;line-height:115%"><font color="#313131" face="arial, helvetica, sans-serif"><span style="word-spacing:1px">4. Overall we need to have the EDPB recent guidelines into account. On data retention issue for example f<span style="font-family:verdana,sans-serif;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">or example, the EDPB explicitly says ICANN has to justify why each element of data has to be retained for two years. So the question on data retention is not about whether ICANN should adjust data retention requirements but that if it is justifiable for ICANN to require data retention of 2 years and on which elements. </span></span></font></p><p class="MsoNormal" style="margin:0cm 0cm 10pt;line-height:115%"></p><p class="MsoNormal" style="font-size:11pt;font-family:Calibri,sans-serif;margin:0cm 0cm 0.0001pt;line-height:115%"><br></p><p class="MsoNormal" style="font-size:11pt;font-family:Calibri,sans-serif;margin:0cm 0cm 0.0001pt;line-height:115%">5. section J. Please reject all IPC additions.</p><p class="MsoNormal" style="font-size:11pt;font-family:Calibri,sans-serif;margin:0cm 0cm 0.0001pt;line-height:115%"><br></p><p class="MsoNormal" style="font-size:11pt;font-family:Calibri,sans-serif;margin:0cm 0cm 0.0001pt;line-height:115%">6.Lets talk about access and not accreditation if we are not winning to remove access from EPDP. Seems like Susan agrees. </p><p class="MsoNormal" style="font-size:11pt;font-family:Calibri,sans-serif;margin:0cm 0cm 0.0001pt;line-height:115%"><br></p><p class="MsoNormal" style="font-size:11pt;font-family:Calibri,sans-serif;margin:0cm 0cm 0.0001pt;line-height:115%"><br></p><div style="font-size:11pt;font-family:Calibri,sans-serif"><div><div id="gmail-_com_1" class="gmail-msocomtxt">
</div>
</div>
</div>
<p></p>
<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div></div>