<p dir="ltr">Dear all,</p>
<p dir="ltr">Thanks (Lisa) for this comprehensive report, well done. I wish I was at ICANN58.</p>
<p dir="ltr">Following the conclusion and as per action item #1 I would suggest that such report be broadcast out in an attached file instead. My feeling is that putting everything inside an e-mail like this make it long and then too difficult to comment and reply. In a well structured file report, we can have sections and chapters and make it easier for navigation, so whenever we want to comment something we just recall the section and paragraph accordingly.</p>
<p dir="ltr">Maybe It as an accepted way (agreed) way to send the full report in an email within this WG, or maybe my siggestion is already taken into account, If so I apologise and will update. Otherwise, I am sure that comments (even inline) won't always be easy and is not an usable option for long e-mails.</p>
<p dir="ltr">Best Regards<br>
@__f_f__<br>
<a href="http://about.me/farell">about.me/farell</a> <br>
________________________________.<br>
Mail sent from my mobile phone. Excuse for brievety.</p>
<div class="gmail_quote">Le 21 mars 2017 05:45, "Lisa Phifer" <<a href="mailto:lisa@corecom.com">lisa@corecom.com</a>> a écrit :<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div class="m_3827200018119411458WordSection1"><p class="MsoNormal">Dear all – (Apologies, this reformatted email replaces previous Outlook-mangled message)<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Below please find notes from the two RDS PDP WG F2F meetings at ICANN58. <u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">To recap action items:<u></u><u></u></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><b><span style="color:#333333">Action Item #1: </span></b><span style="color:#333333">Staff to investigate additional techniques to draw WG member attention to Action Items and Poll Invitations.<u></u><u></u></span></p><p class="MsoNormal" style="background:white"><b><span style="color:#333333">Action Item #2: </span></b><span style="color:#333333">WG members assigned to ask questions of data commissioners on Monday.<u></u><u></u></span></p><p class="MsoNormal" style="background:white"><b><span style="color:#333333">Action Item #3: </span></b><span style="color:#333333">Test by polling the three above-proposed updates to the draft Statement of Purpose. Staff to launch the poll after the conclusion of RDS PDP WG F2F meetings.<br><b>Action Item #4: </b>All WG members to participate in the poll before COB Saturday 26 March. Poll results to be reviewed during the 28 March WG meeting.<u></u><u></u></span></p><p class="MsoNormal" style="background:white"><b><span style="color:#333333">Action Item #5: </span></b><span style="color:#333333">Peter Kimpian to gather answers to the 19 WG questions from the panelists and provide them (if possible) prior to the next WG call on 28 March 2017. <u></u><u></u></span></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><b>This week’s poll link:</b> <em><span style="font-family:"Calibri","sans-serif";color:#333333;background:white"><a href="https://www.surveymonkey.com/r/D6SP37R" target="_blank"><span style="color:#3b73af">https://www.surveymonkey.com/<wbr>r/D6SP37R</span></a> (closes COB 26 March)<b><u></u><u></u></b></span></em></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Best regards,<u></u><u></u></p><p class="MsoNormal">Lisa<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><b><span style="color:#333333">Notes - RDS PDP WG Meetings at ICANN58<u></u><u></u></span></b></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><i><span style="color:#333333">These high-level notes are designed to help PDP WG members navigate through the content of these meetings and are not meant as a substitute for the transcripts and/or recordings. The MP3, transcript, and Adobe Connect recording are provided separately and are posted on the wiki <span style="background:white">here:<u></u><u></u></span></span></i></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><i><span style="color:#333333;background:white">Saturday 11 March: </span></i><a href="http://sched.co/9npN" target="_blank"><i><span style="color:#3b73af;background:white">http://sched.co/9npN</span></i></a><i><span style="color:#333333;background:white"> <wbr>and </span></i><a href="https://community.icann.org/x/GbLRAw" target="_blank"><i><span style="color:#3b73af;background:white">https://community.icann.<wbr>org/x/GbLRAw</span></i></a><i><span style="color:#333333"><br><span style="background:white">Wednesday 15 March: </span></span></i><a href="http://sched.co/9npc" target="_blank"><i><span style="color:#3b73af;background:white">http://sched.co/9npc</span></i></a><i><span style="color:#333333;background:white"> <wbr>and </span></i><a href="https://community.icann.org/x/HbLRAw" target="_blank"><i><span style="color:#3b73af;background:white">https://community.icann.<wbr>org/x/HbLRAw</span></i></a><i><span style="color:#333333"><u></u><u></u></span></i></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><i><span style="color:#333333;background:white">Many WG members also attended a cross-community discussion with Data Commissioners. The MP3, transcript, and Adobe Connect recording of that session can be found here: </span></i><a href="http://sched.co/9nnl" target="_blank"><i><span style="color:#3b73af;background:white">http://sched.co/9nnl</span></i></a><b><i><span style="color:#333333"><u></u><u></u></span></i></b></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:0in;background:white"><b><span style="color:#333333">Notes - RDS PDP WG Meeting – Saturday 11 March, 2017<u></u><u></u></span></b></p><p class="MsoNormal">1. Introductions<u></u><u></u></p><ul type="disc"><li class="MsoNormal" style="color:#333333;background:white">Please state your name before speaking and remember to mute your microphones when not speaking<u></u><u></u></li><li class="MsoNormal" style="color:#333333;background:white">WG members in attendance introduced themselves<u></u><u></u></li></ul><p class="MsoNormal" style="margin-top:7.5pt;background:white"><span style="color:#333333">2. PDP Work Plan, Progress, and Status<u></u><u></u></span></p><ul type="disc"><li class="MsoNormal" style="color:#333333;background:white">Briefly introduced work plan (<span style="color:windowtext"><a href="https://community.icann.org/x/oIxlAw" target="_blank"><b><span style="color:#3b73af;text-decoration:none">https://community.icann.org/<wbr>x/oIxlAw</span></b></a></span>), recent progress, and current task:<u></u><u></u></li></ul><p class="m_3827200018119411458MsoListParagraph" style="margin-left:1.0in;background:white"><u></u><span style="font-family:"Courier New";color:#333333"><span>o<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:#333333">Task 12.a: Deliberate on Possible Fundamental Requirements for these charter questions:<u></u><u></u></span></p><ul type="disc"><ul type="circle"><ul type="square"><li class="MsoNormal" style="color:#333333;background:white">Users/Purposes: Who should have access to gTLD registration data and why?<u></u><u></u></li><li class="MsoNormal" style="color:#333333;background:white">Data Elements: What data should be collected, stored, and disclosed?<u></u><u></u></li><li class="MsoNormal" style="color:#333333;background:white">Privacy: What steps are needed to protect data and privacy?<u></u><u></u></li></ul></ul><li class="MsoNormal" style="color:#333333;background:white">Review of work plan and overview of progress to date/current status including:<u></u><u></u></li><ul type="circle"><li class="MsoNormal" style="color:#333333;background:white">Focus on “thin” data<u></u><u></u></li><li class="MsoNormal" style="color:#333333;background:white">Deliberation on possible fundamental requirements regarding users/purposes<u></u><u></u></li><li class="MsoNormal" style="color:#333333;background:white">What data elements should be collected, stored and disclosed<u></u><u></u></li><li class="MsoNormal" style="color:#333333;background:white">Privacy and data protection considerations<u></u><u></u></li><li class="MsoNormal" style="color:#333333;background:white">Results of polls used to determine rough consensus among WG members – interim conclusion reached with no final decisions yet made<u></u><u></u></li></ul></ul><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>As per the work plan, initial report on phase 1 of the PDP will use rough consensus to determine 5 fundamental requirements <u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Noted that we are starting with Key Concepts<b> </b>– latest version of this working document is always posted at <a href="https://community.icann.org/x/p4xlAw" target="_blank"><b><span style="color:#3b73af;text-decoration:none">https://community.icann.<wbr>org/x/p4xlAw</span></b></a><u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><strong><span style="font-family:Symbol;font-weight:normal"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span></strong><u></u>Highlighted initial points of rough consensus reached since ICANN57, reflected in that working document. Refer to <a href="https://community.icann.org/download/attachments/64074265/ICANN58-RDS-PDP-WG-Slides-FinalRev.pdf?version=1&modificationDate=1489227048000&api=v2" target="_blank"><b><span style="color:#3b73af;background:white">ICANN58-RDS-PDP-WG-Slides-<wbr>Final.pdf</span></b></a><strong><span style="font-family:"Calibri","sans-serif";color:#333333;background:white;font-weight:normal"> (slides 4-8)</span></strong><strong><span style="font-family:"Calibri","sans-serif";font-weight:normal"><u></u><u></u></span></strong></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Regarding agreement #14, on what basis did the group conclude that existing policies do NOT sufficiently address compliance with laws about purpose? What jurisdiction was assumed? No jurisdiction was assumed, but we know that in some jurisdictions, policy is not compliant, so therefore we need to do more (that is, current policy is not sufficient for all jurisdictions).<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>When was agreement #14 discussed? In the February 14 call, followed by a poll in which 86% agreed with this statement. However, note that some WG members missed that call due to conflicting meetings.<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Request to highlight action items and poll invitations to help WG members notice them amongst all the long email threads (e.g., separate mailing list, actions at top of meeting notes)<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u> <u></u></p><p class="MsoNormal"><b>Action Item #1: </b>Staff to investigate additional techniques to draw WG member attention to Action Items and Poll Invitations, such as including them at the top of emails containing WG meeting notes.<u></u><u></u></p><p class="MsoNormal"><b><u></u> <u></u></b></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Has the WG developed criteria for what makes a purpose legitimate yet? No. So far we have discussed only legitimate purposes for COLLECTION of THIN DATA. However, we still need to get to KEY CONCEPTS around what makes a purpose legitimate (criteria, etc.)<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>It is difficult to reach agreement on purposes without a better feeling for the consequences of identifying purposes as legitimate, primary/secondary, etc. Is this putting the cart before the horse? Hoping to get answers to these questions from data commissioners panel.<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><a href="http://www.theiacp.org/Portals/0/documents/pdfs/2016%20FINAL%20Resolutions.pdf" target="_blank"><span style="color:#3b73af;background:white">International Association of Chiefs of Police (IACP)</span></a> member introduced the IACP’s recent <a href="http://www.theiacp.org/Portals/0/documents/pdfs/2016%20FINAL%20Resolutions.pdf" target="_blank">resolution on WHOIS</a> – was an update to the IACP’s last resolution, issued 5 years ago. The WG chair encouraged the IACP to join the WG and participate in this PDP.<u></u><u></u></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><span style="color:#333333">3. PDP Working Session<u></u><u></u></span></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><span style="color:#333333">a. Finalize WG preparations for Cross-Community session with Data Commissioners<br> </span><a href="https://community.icann.org/download/attachments/64072843/RDSPDP-QuestionsForDataCommissioners-7March2017.pdf?version=1&modificationDate=1488916433480&api=v2" target="_blank"><span style="color:#3b73af;text-decoration:none">RDSPDP-<wbr>QuestionsForDataCommissioners-<wbr>7March2017.pdf</span></a><span style="color:#333333"> <u></u><u></u></span></p><p class="m_3827200018119411458MsoNoSpacing"><u></u> <u></u></p><p class="m_3827200018119411458MsoNoSpacing" style="margin-left:.5in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Overview of 19 questions developed to present during cross-community session with data commissioners (Monday, 13 March)<u></u><u></u></p><p class="m_3827200018119411458MsoNoSpacing" style="margin-left:.5in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Questions sent to Becky Burr who will be moderating the cross-community session<u></u><u></u></p><p class="m_3827200018119411458MsoNoSpacing" style="margin-left:.5in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Working group members assigned to questions for data commissioners – monitor whether or not questions were asked and answered during the session (or perhaps answered without being directly asked)<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-bottom:10.0pt;line-height:115%"><u></u><span style="font-size:10.0pt;line-height:115%;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Discussion with data commissioners will continue during session on Wednesday, 15 March<b><u></u><u></u></b></p><p class="MsoNormal"><b>Action Item #2: WG members assigned to ask questions of data commissioners on Monday:<u></u><u></u></b></p><p class="m_3827200018119411458MsoNoSpacing" style="margin-left:.5in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Tim Chen: Purpose<u></u><u></u></p><p class="m_3827200018119411458MsoNoSpacing" style="margin-left:.5in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Rod Rasmussen: Registration Data Elements<u></u><u></u></p><p class="m_3827200018119411458MsoNoSpacing" style="margin-left:.5in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Alex Deacon: Access to Registration Data for Criminal and Abuse Investigations<u></u><u></u></p><p class="m_3827200018119411458MsoNoSpacing" style="margin-left:.5in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Vicky Sheckler: Personal Privacy/Human Rights<u></u><u></u></p><p class="m_3827200018119411458MsoNoSpacing" style="margin-left:.5in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Kiran Malancharuval: Jurisdiction<u></u><u></u></p><p class="m_3827200018119411458MsoNoSpacing" style="margin-left:.5in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Susan Kawaguchi: Compliance with Applicable Laws<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-bottom:10.0pt;line-height:115%"><u></u><span style="font-size:10.0pt;line-height:115%;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Ayden Ferdeline: Consumer Protection<b><u></u><u></u></b></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><span style="color:#333333">b. Continue deliberation on Purpose: <u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:0in;margin-left:22.5pt;margin-bottom:.0001pt;background:white"><i><span style="color:#333333">Question 2.3: What should the over-arching purpose be of collecting, maintaining, and providing access to gTLD registration (thin) data?</span></i><span style="color:#333333"><u></u><u></u></span></p><ul type="disc"><li class="MsoNormal" style="background:white"><span style="color:#333333">Review results of 7 March Poll on Purpose: <br></span><a href="https://community.icann.org/download/attachments/64074265/SummaryResults-Poll-on-Purpose-from-7MarchCall.pdf?version=1&modificationDate=1489222898000&api=v2" target="_blank"><span style="color:#3b73af;text-decoration:none">SummaryResults-Poll-on-<wbr>Purpose-from-7MarchCall.pdf</span></a><u></u><u></u></li><li class="MsoNormal" style="background:white">Q2: primary point of disagreement is about whether data is authoritative or RDS is authoritative source of data<u></u><u></u></li></ul><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>“Authoritative” has a technical meaning – access to the real database, not a copy of it<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Does authoritative imply a requirement to validate the data? No, there are separate 2013 RAA requirements on validation. <u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Technically it's impossible for the authoritative data to be inaccurate with respect to the underlying repository (unless it is inaccurate on purpose -- e.g. anonymization)<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>From Chat: COMMENT: We debated this at length at the EWG. Recreating the wheel here. Also, per Article 29 WP 76 Opinion 2/2003, the data needs to be accurate, which during the EWG, we deferred to THICK data.<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>The Thick WHOIS WG used this working definition: "Authoritative, with respect to provision of Whois services, shall be interpreted as to signify the single database within a hierarchical database structure holding the data that is assumed to be the final authority regarding the question of which record shall be considered accurate and reliable in case of conflicting records; administered by a single administrative [agent] and consisting of data provided by the registrants of record through their registrars."<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Should we be distinguishing between an 'authoritative source of the gTLD registration data' and 'authoritative gTLD registration data'?<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Statement of purpose should not imply a particular model for storage of data or movement of data between storage locations<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Registration data disseminated through the RDS should be authoritative (in the technical sense). That is, the data should be obtained from the source considered to be authoritative.<u></u><u></u></p><p class="MsoNormal" style="margin-left:.25in"><u></u> <u></u></p><p class="MsoNormal"><strong><span style="font-family:"Calibri","sans-serif";color:#333333;background:white">Proposed WG Agreement #1:</span></strong><span class="m_3827200018119411458apple-converted-space"><i><span style="color:#333333;background:white"> </span></i></span><em><span style="font-family:"Calibri","sans-serif";color:#333333;background:white"> </span></em><span style="color:#333333;background:white">Replace purpose 2) "<em><span style="font-family:"Calibri","sans-serif"">A purpose of RDS is to provide an authoritative source of information about, for example, domain contacts, domain names and name servers for gTLDs, [based on approved policy]" </span></em>with "<em><span style="font-family:"Calibri","sans-serif"">A purpose of RDS is to</span></em><span class="m_3827200018119411458apple-converted-space"><i> </i></span><strong><i><span style="font-family:"Calibri","sans-serif"">facilitate dissemination of authoritatively-sourced</span></i></strong><span class="m_3827200018119411458apple-converted-space"><i> </i></span><em><span style="font-family:"Calibri","sans-serif"">gTLD registration data, such as domain names and their domain contacts and name servers,</span></em><span class="m_3827200018119411458apple-converted-space"><i> </i></span><strong><i><span style="font-family:"Calibri","sans-serif"">in accordance with applicable policy</span></i></strong><em><span style="font-family:"Calibri","sans-serif"">."<u></u><u></u></span></em></span></p><p class="MsoNormal"><span style="color:black"><u></u> <u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Q3: Anything that needs to be added to the statement of purpose?<b><u></u><u></u></b></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Somewhere along the line we seem to have lost the point that the RDS provides the information about the registry's view of the technically-required data for domain name resolution. <b><u></u><u></u></b></p><p class="MsoNormal" style="margin-left:.25in"><b><u></u> <u></u></b></p><p class="MsoNormal"><strong><span style="font-family:"Calibri","sans-serif";color:#333333;background:white">Proposed WG Agreement #2:</span></strong><span class="m_3827200018119411458apple-converted-space"><i><span style="color:#333333;background:white"> </span></i></span><em><span style="font-family:"Calibri","sans-serif";color:#333333;background:white"> </span></em><span style="color:#333333;background:white">Replace purpose 1) "<em><span style="font-family:"Calibri","sans-serif"">A purpose of gTLD registration data is to provide information about the lifecycle of a domain name" </span></em>with "<em><span style="font-family:"Calibri","sans-serif"">A purpose of gTLD registration data is to provide information about the lifecycle of a domain name</span></em><span class="m_3827200018119411458apple-converted-space"><i> </i></span><em><b><span style="font-family:"Calibri","sans-serif"">and its resolution on the Internet</span></b></em><em><span style="font-family:"Calibri","sans-serif"">."<u></u><u></u></span></em></span></p><p class="MsoNormal"><span style="color:black"><u></u> <u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Regarding comment "d" - The RDS is a directory service. Protecting privacy would be a potential feature available.<b><u></u><u></u></b></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Chat proposal to add the following: Purpose of RDS is to support domain name registration and maintenance by providing appropriate access to registration data to enable a reliable mechanism for identifying, establishing and maintaining the ability to contact Registrants.<b><u></u><u></u></b></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>For specific purpose 5, we are conflating issues of purpose and requirements to fulfill a purpose. <b><u></u><u></u></b></p><p class="MsoNormal" style="margin-left:.25in"><b><u></u> <u></u></b></p><p class="MsoNormal"><strong><span style="font-family:"Calibri","sans-serif";color:#333333;background:white">Proposed WG Agreement #3:</span></strong><span class="m_3827200018119411458apple-converted-space"><i><span style="color:#333333;background:white"> </span></i></span><em><span style="font-family:"Calibri","sans-serif";color:#333333;background:white"> </span></em><span style="color:#333333;background:white">Replace purpose 5) "<em><span style="font-family:"Calibri","sans-serif"">A purpose of RDS policy is to facilitate the accuracy of gTLD registration data." w</span></em>ith "<em><span style="font-family:"Calibri","sans-serif"">A purpose of RDS policy is to facilitate</span></em><span class="m_3827200018119411458apple-converted-space"><i> </i></span><strong><i><span style="font-family:"Calibri","sans-serif"">fulfilling requirements</span></i></strong><span class="m_3827200018119411458apple-converted-space"><i> </i></span><em><span style="font-family:"Calibri","sans-serif"">for the accuracy of gTLD registration data."<u></u><u></u></span></em></span></p><p class="MsoNormal"><em><span style="font-family:"Calibri","sans-serif";color:#333333;background:white"><u></u> <u></u></span></em></p><p class="MsoNormal"><b>Action Item #3: </b>Test by polling the three above-proposed updates to the draft Statement of Purpose. Staff to launch the poll after the conclusion of RDS PDP WG F2F meetings. <u></u><u></u></p><p class="MsoNormal"><b><u></u> <u></u></b></p><p class="MsoNormal"><b>Action Item #4: </b>All WG members to participate in the poll before COB Saturday 26 March. Poll results to be reviewed during the 28 March WG meeting.<b><u></u><u></u></b></p><p class="MsoNormal" style="margin-left:.25in;background:white"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>The following agenda items were deferred to next meeting (28 March)<u></u><u></u></p><p class="MsoNormal" style="margin-left:.25in;background:white"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Finalize Statement of Purpose <u></u><u></u></p><p class="MsoNormal" style="margin-bottom:12.0pt;margin-left:.25in;background:white"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Move on to next topic of deliberation by expanding our focus from “thin data” collection to “thin data” access: <i><span style="color:#333333">Question 2.2: For what specific (legitimate) purposes should gTLD registration thin data elements <u>be made accessible</u>?</span></i><u></u><u></u></p><p class="MsoNormal"><span style="color:#333333">4. Confirm action items and proposed decision points<u></u><u></u></span></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><b><span style="color:#333333">Action Item #1: </span></b><span style="color:#333333">Staff to investigate additional techniques to draw WG member attention to Action Items and Poll Invitations.<u></u><u></u></span></p><p class="MsoNormal" style="background:white"><b><span style="color:#333333">Action Item #2: </span></b><span style="color:#333333">WG members assigned to ask questions of data commissioners on Monday.<u></u><u></u></span></p><p class="MsoNormal" style="background:white"><b><span style="color:#333333">Action Item #3: </span></b><span style="color:#333333">Test by polling the three above-proposed updates to the draft Statement of Purpose. Staff to launch the poll after the conclusion of RDS PDP WG F2F meetings.<br><b>Action Item #4: </b>All WG members to participate in the poll before COB Saturday 26 March. Poll results to be reviewed during the 28 March WG meeting.<u></u><u></u></span></p><p class="MsoNormal" style="background:white"><b><span style="color:#333333">Action Item #5: </span></b><span style="color:#333333">Peter Kimpian to gather answers to the 19 WG questions from the panelists and provide them (if possible) prior to the next WG call on 28 March 2017. <u></u><u></u></span></p><p class="MsoNormal" style="background:white"><span style="color:#333333"> <u></u><u></u></span></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><b><span style="color:#333333">Proposed WG Agreement #1:</span></b><i><span style="color:#333333"> </span></i><span style="color:#333333">Replace purpose 2) "<i>A purpose of RDS is to provide an authoritative source of information about, for example, domain contacts, domain names and name servers for gTLDs, [based on approved policy]" </i>with "<i>A purpose of RDS is to <b>facilitate dissemination of authoritatively-sourced</b> gTLD registration data, such as domain names and their domain contacts and name servers, <b>in accordance with applicable policy</b>."</i><u></u><u></u></span></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><b><span style="color:#333333">Proposed WG Agreement #2:</span></b><i><span style="color:#333333"> </span></i><span style="color:#333333">Replace purpose 1) "<i>A purpose of gTLD registration data is to provide information about the lifecycle of a domain name" </i>with "<i>A purpose of gTLD registration data is to provide information about the lifecycle of a domain name <b>and its resolution on the Internet</b>."</i><u></u><u></u></span></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><b><span style="color:#333333">Proposed WG Agreement #3:</span></b><i><span style="color:#333333"> </span></i><span style="color:#333333">Replace purpose 5) "<i>A purpose of RDS policy is to facilitate the accuracy of gTLD registration data." w</i>ith "<i>A purpose of RDS policy is to facilitate <b>fulfilling requirements</b> for the accuracy of gTLD registration data."</i><u></u><u></u></span></p><p class="MsoNormal"><b><u></u> <u></u></b></p><p class="m_3827200018119411458p4" style="margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;background:white"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333">Meeting Materials:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333"> <strong><span style="font-family:"Calibri","sans-serif""> </span></strong></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><a href="https://community.icann.org/x/GbLRAw" target="_blank">https://community.icann.org/<wbr>x/GbLRAw</a><strong><span style="font-family:"Calibri","sans-serif";color:#333333"><u></u><u></u></span></strong></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><a href="https://community.icann.org/download/attachments/64072843/RDSPDP-QuestionsForDataCommissioners-7March2017.pdf?version=1&modificationDate=1488916433480&api=v2" target="_blank"><span style="color:#3b73af">RDSPDP-<wbr>QuestionsForDataCommissioners-<wbr>7March2017.pdf</span></a><span style="color:#333333"> and <br></span><a href="https://community.icann.org/download/attachments/64072843/RDSPDP-QuestionsForDataCommissioners-7March2017.docx?version=1&modificationDate=1488916450802&api=v2" target="_blank"><span style="color:#3b73af">RDSPDP-<wbr>QuestionsForDataCommissioners-<wbr>7March2017.docx</span></a><u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:#333333"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><strong><span style="font-family:"Calibri","sans-serif";color:#333333;font-weight:normal">11MarchMeeting-Handout: </span></strong><a href="https://community.icann.org/download/attachments/64074265/ICANN58-RDS-PDP-WG-Slides-FinalRev.pdf?version=1&modificationDate=1489227048000&api=v2" target="_blank"><span style="color:#3b73af">ICANN5<wbr>8-RDS-PDP-WG-Slides-Final.pdf</span></a><span style="color:#333333"> <wbr>and </span><a href="https://community.icann.org/download/attachments/64074265/ICANN58-RDS-PDP-WG-Slides-FinalRev.pptx?version=1&modificationDate=1489227119000&api=v2" target="_blank"><strong><span style="font-family:"Calibri","sans-serif";color:#3b73af;font-weight:normal;text-decoration:none">ppt</span></strong><span style="color:#3b73af"> </span></a><span style="color:#333333"><u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:#333333"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><a href="https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-7March2017.pdf?version=3&modificationDate=1489036968927&api=v2" target="_blank"><span style="color:#3b73af">KeyConceptsDeliberation-<wbr>WorkingDraft-7March2017.pdf</span></a><strong><span style="font-family:"Calibri","sans-serif";color:#333333;font-weight:normal"> </span></strong><span style="color:#333333">an<wbr>d </span><a href="https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-7March2017.docx?version=3&modificationDate=1489036982656&api=v2" target="_blank"><span style="color:#3b73af">doc</span></a><span style="color:#333333"><u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:#333333"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><strong><span style="font-family:"Calibri","sans-serif";color:#333333;font-weight:normal">7 March Call Poll on Purpose -</span></strong><span style="color:#333333"><u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:#333333"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:#333333">Link to participate:<em><span style="font-family:"Calibri","sans-serif""> </span></em></span><a href="https://www.surveymonkey.com/r/WLMXDJG" target="_blank"><i><span style="color:#3b73af">https://www.<wbr>surveymonkey.com/r/WLMXDJG</span></i></a><span style="color:#333333"><u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:#333333"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:#333333">PDF of Poll Questions: </span><a href="https://community.icann.org/download/attachments/64072843/Poll-on-Purpose-from-7MarchCall.pdf?version=1&modificationDate=1488938315379&api=v2" target="_blank"><span style="color:#3b73af">Poll-on-Purpose-<wbr>from-7MarchCall.pdf</span></a><span style="color:#333333"><u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:#333333"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:#333333">SurveyMonkey PDF Summary Poll Results: </span><a href="https://community.icann.org/download/attachments/64074265/SummaryResults-Poll-on-Purpose-from-7MarchCall.pdf?version=1&modificationDate=1489222898000&api=v2" target="_blank"><span style="color:#3b73af">SummaryResults-Poll-<wbr>on-Purpose-from-7MarchCall.pdf</span></a><span style="color:#333333"><u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:#333333"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:#333333">SurveyMonkey ZIP of Raw Poll Results: </span><a href="https://community.icann.org/download/attachments/64074265/RawResults-Poll-on-Purpose-from-7MarchCall.zip?version=1&modificationDate=1489222956000&api=v2" target="_blank"><span style="color:#3b73af">RawResults-Poll-on-<wbr>Purpose-from-7MarchCall.zip</span></a><span style="color:#333333"><u></u><u></u></span></p><p class="MsoNormal" style="margin-top:7.5pt;background:white"><b><span style="color:#333333"><u></u> <u></u></span></b></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:0in;background:white"><b><span style="color:#333333">Notes - RDS PDP WG Meeting – Wednesday 15 March, 2017<u></u><u></u></span></b></p><p class="MsoNormal">1. Introductions: Guest presenters were introduced to RDS PDP WG:<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Joe Cannataci, UN Special Rapporteur on the right to privacy<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-bottom:12.0pt"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Peter Kimpian, Data Protection Unit of the Council of Europe<u></u><u></u></p><p class="MsoNormal">2. Data Protection Expert – Q&A session<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>The WG chair briefly introduced our charter and current areas of deliberation<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Preface from Joe Cannataci: With regard to future interaction, we need to consider sustainability; may wish to set up a group to invite experts to join WG discussion formally<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Guest presenters discussed the WG’s list of questions:<br><a href="https://community.icann.org/download/attachments/64072843/RDSPDP-QuestionsForDataCommissioners-7March2017.pdf?version=1&modificationDate=1488916433480&api=v2" target="_blank"><b><span style="color:#3b73af">RDSPDP-<wbr>QuestionsForDataCommissioners-<wbr>7March2017.pdf</span></b></a><u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Discussion with Joe Cannataci on purpose of a next generation RDS, including:<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-left:.75in"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>What specifying purpose entails<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-left:.75in"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Where purpose of data will and will not apply in the RDS<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-left:.75in"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Criteria that apply to legitimate purposes<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-left:.75in"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Publication of data elements in the RDS<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-left:.75in"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Feedback on the WG’s specific purpose #1:<br>“A purpose of gTLD registration data is to provide information about the lifecycle of a domain name and its resolution on the Internet.”<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-left:.75in"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Applicability to “thin” versus “thick” data elements<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-left:.75in"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Differentiation between primary and secondary purposes<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.75in"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Notes below provide a brief overview of points raised during discussion; refer to the <a href="http://schd.ws/hosted_files/icann58copenhagen2017/d0/Transcript%20RDS%2015%20March%20Copenhagen.pdf" target="_blank"><b><span style="color:#3b73af;background:white">Transcript</span></b></a> for a complete recap of this Q&A session<u></u><u></u></p><p class="MsoNormal">Q1. What do you mean when you tell ICANN to specify the purpose of WHOIS?<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">Test for purpose should be based on use studies or case studies. <u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">Whenever you have someone stipulate they want to collect data, you must ask why. <u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">Example of applying for a bank loan or insurance policy to assess risk. <u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">Each bit of information must be in line with purpose. <u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">Purpose cannot be general or just in case.<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">Can only keep records for as long as needed for purpose.<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">Purpose questions (and answers) will change over time.<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">If you are a bank or telecom developing a new service you must define your primary purpose.<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">A secondary purpose might be a different service marketed to the same client later on.<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>It would be good to get definitions for “primary purpose” and “secondary purpose.”<span lang="EN-GB" style="color:black"><u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>From chat: Australian Privacy Act 1988: "Use or disclosure of personal information for a purpose other than the primary purpose of collection (being a 'secondary purpose') is permitted under specific exceptions where that secondary use or disclosure is ... in the conduct of surveillance activities, intelligence gathering activities or monitoring activities, by a law enforcement agency"<span lang="EN-GB" style="color:black"><u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">The purpose must be clear – for example “in order to enable enforcement of specific law”<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">If a purpose is provided for by law then a purpose is legitimate.<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">For example, the purpose of collection of registrant data might be to ensure that the DNS works. There is a belief by some that there should be access to that data by others (e.g., those investigating cybercrime). Are those secondary purposes? The WG must decide.<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span lang="EN-GB" style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="color:black">Do you need separate purposes for collection, access, and display? Absolutely yes.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="color:black"><u></u> <u></u></span></p><p class="MsoNormal">Q2. <span style="color:black">Under what circumstances might the publication of registration data elements that are personal data be allowable?<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Why do you want to publish information? What is the public interest in publishing that data?<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">For example, why is information about the lifecycle of domain in the public interest?<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">If data is easily linked to an individual, then it is personal data.<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Just because it is personal data doesn’t mean it cannot be in a WHOIS record<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">No data protection law prohibits publication of personal data for legitimate purposes<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:black">Q5. Do you believe that any of the following THIN data elements are considered personal information under the General Data Protection Directive, and why?<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">In this case (thin data example in #5) the data is not personal data, but in other cases it might be<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">If an individual registers their own name as a domain name, is the domain name personal data? WG view: In this case, the individual has chosen to publish their name in the DNS. A domain name is required for DNS resolution and as the key to the WHOIS record.<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Why is expiration date published in a directory service? Isn’t that just of interest to the subscriber? Why is it of legitimate interest to others?<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Analogy with telephone directory – in most countries, subscribers can opt out of being in the phone directory; why doesn’t that apply here?<u></u><u></u></span></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">There may be other analogies that are more appropriate than a telephone directory</span><u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">3. Deferred: <i>Continuation of Saturday F2F session deliberation, time permitting<u></u><u></u></i></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">4. Conclusions and Adjourn<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Plan is to collect answers to the WG’s questions (all 19) from the data protection experts who participated in the Monday cross-community session. <u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>In principle, there is broad agreement amongst panelists on the answers to the WG’s questions. Responses from data commissioners may be published on the WG’s wiki, if helpful.<u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u>Reminder for all WG members to participate in this week’s poll no later than COB 26 March.<u></u><u></u></p><p style="margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;background:white"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333">Action Item #5: </span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333">Peter Kimpian to gather answers to the 19 WG questions from the panelists and provide them (if possible) prior to the next WG call on 28 March 2017. <u></u><u></u></span></p><p style="margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;background:white"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333"><u></u> <u></u></span></p><p class="MsoNormal"><b>Meeting Materials:</b> <a href="https://community.icann.org/x/HbLRAw" target="_blank"><span style="color:#333333;text-decoration:none">https://community.icann.org/<wbr>x/HbLRAw</span></a><u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><a href="https://community.icann.org/download/attachments/64072843/RDSPDP-QuestionsForDataCommissioners-7March2017.pdf?version=1&modificationDate=1488916433480&api=v2" target="_blank"><span style="color:#3b73af">RDSPDP-<wbr>QuestionsForDataCommissioners-<wbr>7March2017.pdf</span></a> and <br><a href="https://community.icann.org/download/attachments/64072843/RDSPDP-QuestionsForDataCommissioners-7March2017.docx?version=1&modificationDate=1488916450802&api=v2" target="_blank"><span style="color:#3b73af">RDSPDP-<wbr>QuestionsForDataCommissioners-<wbr>7March2017.docx</span></a><u></u><u></u></p><p class="m_3827200018119411458MsoListParagraph"><u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><strong><span style="font-family:"Calibri","sans-serif";color:#333333;font-weight:normal">11MarchMeeting-Handout (primarily slides 28-37):</span></strong><strong><span style="font-family:"Calibri","sans-serif";color:#333333"> </span></strong><b><br></b><a href="https://community.icann.org/download/attachments/64074269/ICANN58-RDS-PDP-WG-Slides-FinalRev2.pdf?version=1&modificationDate=1489578526000&api=v2" target="_blank"></a></p></div></div><br>______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br>...</blockquote></div>