<html>
<body>
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:<br>
<blockquote type=cite class=cite cite="">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>
<ul>
<li>RDS PDP WG Call -- Tuesday 7 March 2017 at 17.00 UTC
<li>RDS PDP WG F2F -- Saturday 11 March 2017 1:45-4:45 pm - See
<a href="http://sched.co/9npN" eudora="autourl">http://sched.co/9npN</a>
for further details.
<li>RDS PDP WG Wrap-Up -- Wednesday 15 March 2017 1:45-3:00 pm. See
<a href="http://sched.co/9npc" eudora="autourl">http://sched.co/9npc</a>
for further details.
</ul> <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</a><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" eudora="autourl">
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" eudora="autourl">
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" eudora="autourl">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" eudora="autourl">http://sched.co/9npc</a>
for further details.<br>
<br>
<b><i>Marika Konings<br>
</b>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>
gnso-rds-pdp-wg@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" eudora="autourl">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote>
</body>
</html>