<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:274947510;
mso-list-template-ids:-1093376698;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:545066667;
mso-list-template-ids:-1242006632;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
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">Thank you very much Greg for your detailed review of the questions and constructive suggestions. I added some of my personal observations and questions below including some
comments on questions that Greg did not comment on.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I encourage others to insert their comments in this thread. If it is easier to send input separately that is okay. But remember to do it by Friday.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<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"> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Greg Aaron<br>
<b>Sent:</b> Tuesday, February 28, 2017 3:44 PM<br>
<b>To:</b> Lisa Phifer <lisa@corecom.com>; gnso-rds-pdp-wg@icann.org<br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Notes, action items and WG agreements from today's meeting<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">My comments regarding the draft questions are as follows. There are good questions, but need some work to crystallize what they are asking about.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">[Gomes, Chuck] I wonder if TB-1 & SP-1 are essentially the same and could be combined. Also, to me TB-3 seems overly broad and hard to answer.<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">TG-4 is recursive. The regulations state that data may be collected for specified, explicit and legitimate purposes. If the purposes are specified, explicit and legitimate,
then there is no violation of Article 6(1)(b). I think what Theo is trying to ask is: under what circumstances may the publication of personal registration data be allowable?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">TB-4 , TG-4 , and TG-2 all seem to be asking the same underlying thing and could be consolidated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">VS-1: the question is obscured – can it be clarified? Here’s what I think is being asked: An EU directive requires service providers such as registrars to post contact
data for their businesses. If registrars have to do that, does that mean that businesses in the EU could be required to have their contact data displayed in a registration data service?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">NC-3: Needs to be re-written, because private cybersecurity firms do not have the ability to obtain court orders in order to obtain evidence. Only law enforcement bodies and
prosecutors can obtain court orders in criminal cases. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Also, what about civil cases? They require information as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Please note that court orders and subpoenas generally come after a court case is underway. They are not options beforehand, which is when much investigation takes place.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">SP-4: This question seems irrelevant or tangential. The 2014 issue was about registrars retaining data for two years after a domain was deleted. In contrast, our WG is talking
about displaying data about currently registered domain names. And as far as the 2014 letter to ICANN, its reasoning speaks for itself and I don't see why we would ask them to explain what it says.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">[Gomes, Chuck] I believe that SP-6 has already been answered via another PDP so I don’t think we should revisit it. Are the DCs capable of answering the questions in
NC-6, i.e., are they the right ones to whom the questions should be directed?<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">NC-8: I can't follow this one; seems down in the weeds.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">TG-5: this one also seems recursive. If the contractual provisions are in keeping with the allowed cases, then there is no problem. What is this question really seeking?<o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">[Gomes, Chuck] I also think that this question is hard to answer without describing what the legitimate grounds are.</span></i></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">[Gomes, Chuck] Without minimizing the value of many of the other questions, I think that the questions in SP-3 & SP-2 are very useful.<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></i></b></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">[Gomes, Chuck] It seems to me that the question in TB-2 may be very hard for the DCs to answer. I think that they are questions the WG needs to answer once we have a
good understanding of the issues.</span></i></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The parked questions are very hard to understand.<o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">[Gomes, Chuck] Which may be a good reason to not use them unless we can make them clear and useful.</span></i></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">All best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">--Greg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">**********************************<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Greg Aaron<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Vice-President, Product Management<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">iThreat Cyber Group / Cybertoolbelt.com<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">mobile: +1.215.858.2257<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">**********************************<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">The information contained in this message is privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify
us immediately by replying to the message and deleting it from your computer.<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<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">
<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a> [<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Lisa Phifer<br>
<b>Sent:</b> Tuesday, February 28, 2017 1:46 PM<br>
<b>To:</b> <a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] Notes, action items and WG agreements from today's meeting<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Dear all,<br>
<br>
Calling your attention to <b>Action item #1</b>: <br>
<br>
<b>WG members requested to provide input on proposed questions to this mailing list by
<u>Friday 3 March at the latest</u>.<br>
<br>
</b>Attached please find the set of proposed questions introduced during today's WG call. This draft was developed by a small group of WG volunteers as explained in the document itself, in preparation for both the RDS PDP WG's Wednesday F2F session at ICANN58
and the Monday cross-community session with data protection experts.<br>
<br>
To make the best use of limited session time, we need to further narrow this draft list down. Feedback on prioritization is especially welcome to help the WG focus on those questions most likely to yield answers that will aid the WG in moving forward.<br>
<br>
Best, Lisa<br>
<br>
<br>
At 11:20 AM 2/28/2017, Marika Konings wrote:<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Dear All,<br>
<br>
Please find below the notes, action items and WG agreements from today’s meeting. Note that the upcoming WG meetings are scheduled as follows:<br>
<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
RDS PDP WG Call -- Tuesday 7 March 2017 at 17.00 UTC <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
RDS PDP WG F2F -- Saturday 11 March 2017 1:45-4:45 pm - See <a href="http://sched.co/9npN">
http://sched.co/9npN</a> for further details. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
RDS PDP WG Wrap-Up -- Wednesday 15 March 2017 1:45-3:00 pm. See <a href="http://sched.co/9npc">
http://sched.co/9npc</a> for further details. <o:p></o:p></li></ul>
<p class="MsoNormal"> <br>
Best regards,<br>
<br>
Marika<br>
<b> <br>
Notes RDS PDP WG meeting 28 February 2017 <br>
<br>
</b><i>These high-level notes are designed to help PDP WG members navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki
at</i> <a href="https://community.icann.org/x/HIzRAw"><i>https://community.icann.org/x/HIzRAw</i></a><i><br>
</i> <br>
<i>1. Roll call / SOI<br>
</i>· Roll call will be taken from Adobe Connect<br>
· Please state name for transcription purposes and remember to mute your microphone when not speaking<br>
· Call will be chaired by Michele Neylon today<br>
<br>
<i>2. Review draft questions to discuss with Data Commissioners in Copenhagen<br>
</i>a. Note WG plans to meet with DCs and Interpol's Caroline Goemans on Wednesday in Copenhagen<br>
· To take advantage of their presence in Copenhagen as well as the relevance to the current WG discussion<br>
<br>
b. Susan to introduce draft list developed by small group: Questions for Data Commissioners v5.pdf<br>
· See draft questions shared - more questions suggested than can possibly be asked. Leadership team went through the proposed questions and has re-organised / categorized the questions. A number of questions have been parked for now as may not be a
priority or not directly relevant to WG deliberations. <br>
· Need to further narrow list down. Priority should be given to those questions that will aid the WG in moving forward.<br>
· Need to make sure that the questions are laid out in clear simple terms as not all may be familiar with WHOIS or some of the technical terms.<br>
· Some of these questions may be addressed in cross-community sessions, but as it is an open session, there may be many others asking questions. Make sure that in the Wednesday session any questions are covered that are of particular importance to
WG's work. <br>
· Wednesday RDS PDP WG session will include guests to help answer these questions: - Joe Cannataci, UN Special Rapporteur on the right to privacy- Caroline Goemans, Interpol Data Protection Officer- TBD, from the European Data Protection Supervisor-
Peter Kimpian, Data Protection Unit of the Council of Europe.<br>
<br>
<b>Action item #1</b>: WG members requested to provide input on proposed questions by Friday 3 March at the latest. Leadership team to review input and finalise questions for submission to data protection commissioners in advance of Wednesday's WG meeting.
<br>
<br>
c. Action for WG members to provide feedback on-list by end of the week<br>
<br>
<i>3. Continue deliberation on the Purpose charter question:<br>
</i>Question 2.3: What should the over-arching purpose be of collecting, maintaining, and providing access to gTLD registration (thin) data?<br>
a. Review & discuss 22 February poll results: SummaryResults-Poll-on-Purpose-from-22FebCall.pdf<br>
<br>
Q2 - should consistency with ICANN's mission be a goal for each RDS Purpose<br>
· In relation to question on not being able to find mission, please see briefing materials from previous session (<a href="https://community.icann.org/download/attachments/64071050/28FebMeeting-Handout.pdf?version=1&modificationDate=1488216756000">
https://community.icann.org/download/attachments/64071050/28FebMeeting-Handout.pdf?version=1&modificationDate=1488216756000</a> )<br>
· Nearly 85% agreed that "Consistency with ICANN's mission" should be a goal for each RDS purpose<br>
· Is it within domain to decide for which secondary purposes data is used? First need to decide what is going to be within RDS. Whether law enforcement is a purpose for collection or access is within the scope of this WG to recommend. Nothing is being
foreclosed for now but will need to be further discussed. <br>
<br>
Q3 - should consistency with other consensus policies that pertain to gTLDs be a goal for each RDS purpose?<br>
· Just over 70% agreed that "Consistency with other consensus policies that pertain to gTLDs" should be a goal for each RDS purpose.<br>
· End result should definitely be consistency, but this shouldn't unnecessarily constrain the WG.
<br>
· Leadership team observations: This WG's policy recommendations may require updates to aspects of other policies that relate directly to WHOIS/RDDS. If this WG's recommendations introduce inconsistencies with other policies, the IRT would be given
direction to identify any updates that need to be made to other policies for consistency (e.g., new terminology), superseding other requirements that relate directly to RDDS. Consider possible goal rephrasing to acknowledge this?<br>
<br>
Q4 - Should "to provide a framework that enables compliance with applicable laws" be a goal for each RDS purpose?<br>
· Over 85% agreed that "Providing a framework that enables compliance with applicable laws" should be a goal for each RDS purpose.<br>
· Those who disagreed noted that: Not all purposes are related to applicable laws and General laws applicable to a subject matter might not apply in certain cases.<br>
· May wish to suggest adding this as a footnote to the statement of purpose?<br>
<br>
b. Action item to capture confirmed agreements in Section 2.3.2 of working draft<br>
· All rough agreements are being added to our working document to help us track points that have been covered. See
<a href="https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-22February2017.pdf">
https://community.icann.org/download/attachments/56986791/KeyConceptsDeliberation-WorkingDraft-22February2017.pdf</a>
<br>
<br>
c. Resume deliberation on this WG's draft statement of purpose -- see 28FebMeeting-Handout.pdf<br>
· Review draft in light of discussions to date, in particular in relation to the data protection concepts / requirements discussed. Does the draft statement align with those concepts / requirements or should updates be considered?<br>
· #3 - "facilitate" does not necessarily equate to open access<br>
· Concept of accurate data is not a problem from the perspective of data protection legislation. Actually a high level requirement.
<br>
· If there is a poll on this statement of purpose, would you be in support or if not, what objections would you be raising?<br>
· Nothing necessarily causing concern but there may be elements missing? WG may need a little bit more time to review.
<br>
· Might be issues with how specific these purposes are from a EU data protection perspective? Combination of purposes for RDS and the collection of data may have complicated matters? May need a closer review from a data protection perspective. Possibly
ask data protection commissioner's for guidance on how specific purposes must be? Unlikely that they will give specific input on the statement, but more likely to describe purpose in a more general way.
<br>
<br>
<b>Action item #2</b>: Staff to develop and circulate poll on statement of purpose<br>
<br>
<i>4. Confirm action items and proposed decision points<br>
</i> <br>
<b>Action item #1</b>: WG members requested to provide input on proposed questions by Friday 3 March at the latest. Leadership team to review input and finalise questions for submission to data protection commissioners in advance of Wednesday's WG meeting.<br>
<br>
<b>Action item #2</b>: Staff to develop and circulate poll on statement of purpose<br>
<br>
<b>WG Agreement #1</b>: "Consistency with ICANN's mission" should be a goal for each RDS purpose<br>
<b>WG Agreement #2</b>: "Consistency with other consensus policies that pertain to gTLDs" should be a goal for each RDS purpose.<br>
<b>WG Agreement #3</b>: "Providing a framework that enables compliance with applicable laws" should be a goal for each RDS purpose.<br>
<br>
<i>5. Confirm next meeting dates</i>:<br>
<br>
· RDS PDP WG Call -- Tuesday 7 March 2017 at 17.00 UTC<br>
· Saturday session will be continuation of deliberation, Wednesday session will be devoted to data protection Q&A<br>
· RDS PDP WG F2F -- Saturday 11 March 2017 1:45-4:45 pm - aim to detail agenda with timings so that those that are in other sessions are able to join for the items of main importance. See
<a href="http://sched.co/9npN">http://sched.co/9npN</a> for further details. <br>
· RDS PDP WG Wrap-Up -- Wednesday 15 March 2017 1:45-3:00 pm. See <a href="http://sched.co/9npc">
http://sched.co/9npc</a> for further details.<br>
<br>
<b><i>Marika Konings<br>
</i></b><i>Vice President, Policy Development Support – GNSO,, Internet Corporation for Assigned Names and Numbers (ICANN)
<br>
Email: <a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a> <br>
<br>
Follow the GNSO via Twitter @ICANN_GNSO<br>
Find out more about the GNSO by taking our <a href="http://learn.icann.org/courses/gnso">
interactive courses</a> and visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers">
GNSO Newcomer pages</a>. <br>
</i> <br>
_______________________________________________<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">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</blockquote>
</div>
</body>
</html>