<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font size="+1"><font face="Lucida Grande">Indeed, I agree whole
heartedly. Registrars may collect what they need to do
business, and are governed by relevant data protection law.
However, what they collect, use, disclose, escrow, and retain
as instructed by ICANN is clearly within our remit, and unless
I am mistaken there is a certain crossover in the matter of
data retention....if the registrars over collect metadata,
they are instructed to retain it in the RAA so this may be an
instance where we ought to be looking over their shoulders.
The key question, from a data protection perspective is do
they have a legitimate interest, as data controller, in
collecting, using and disclosing it. The same applies to
ICANN as data controller: do they have a legitimate interest
in demanding through contract, as the data controller for the
purposes of mandating data collection, use and disclosure as a
condition of accreditation, the data listed in the RAA? And
it is ICANN which concerns us.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2016-05-09 20:49, Carlton Samuels
wrote:<br>
</div>
<blockquote
cite="mid:CAOZQb9TNPYJ9LbzT8xrYBfjocSdDXmFv5kLmqdesfgss8YDVpw@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="ltr">
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small">Exactly! And we have a
listing of the elements right there in the RAA.</div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small">This distinction has been made
again and again in every fora I have attended on registration
data. And all arguments/traige/decisions pertaining
purposefulness, access and privacy pertain ONLY to those
elements. </div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small">-Carlton</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature"><br>
==============================<br>
Carlton A Samuels<br>
Mobile: 876-818-1799<br>
<i><font color="#33CC00">Strategy, Planning, Governance,
Assessment & Turnaround</font></i><br>
=============================</div>
</div>
<br>
<div class="gmail_quote">On Mon, May 9, 2016 at 12:41 AM, Alan
Greenberg <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">One small
(but I think important) issue that has been bothering me
since we started this WG.<br>
<br>
When we talk about what data is being collected by
registrars or registries, I think we need to be very careful
in our wording. What we are interested in is what data is
being collected (or should be collected in the future)
MANDATED by ICANN agreements. What they collect on their own
volition is not on our agenda (whether it is credit card
information, your birth date so they can send you a
gratuitous Happy Birthday wish, or your national identity
number).<span class="HOEnZb"><font color="#888888"><br>
<br>
Alan</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
At 09/05/2016 12:12 AM, Kathy Kleiman wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Chuck, Michele, Susan, David, and Lisa,<br>
I think Holly has hit the nail on the head. At the
outset, and before moving forward to any additional
questions, we should evaluate:<br>
1) what data is collected?<br>
2) why is this data collected?<br>
3) is this data the subject of data protection laws?<br>
<br>
This is exactly the foundation and background that the
subgroups have prepared for us - the Data Elements,
Privacy law and Purpose subgroups. We now have the
materials to enter into this analysis as a full WG in
a constructive, informed and systematic way.<br>
<br>
Marika recently shared these questions in the link she
sent around summarizing our previous comments/
suggestions. Members from a range of SOs and ACs
raised the need for the WG to reorder the questions to
allow consideration of data elements, privacy
frameworks and "purpose" upfront and early on. As you
may remember, Scott Hollenbeck kicked off the
discussion and many others joined in. <a
moz-do-not-send="true"
href="https://community.icann.org/download/attachments/58730879/RDS-PDP-Phase1-ProposedWorkPlanChanges-16March2016.pdf"
rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="https://community.icann.org/download/attachments/58730879/RDS-PDP-Phase1-ProposedWorkPlanChanges-16March2016.pdf">https://community.icann.org/download/attachments/58730879/RDS-PDP-Phase1-ProposedWorkPlanChanges-16March2016.pdf</a></a>.
When we checked with members of Charter Team in
Marrakech, they blessed the idea that we as a WG
should choose our own order for the questions - as
long as we cover them all, they would be happy.<br>
<br>
Accordingly, why would we launch into secondary
purposes first? Rephrased, why would we consider all
of the "possible requirements" of a directory service
when we as a WG have not yet undertaken the basic
analysis of what data is collected, for what primary
purpose, and under what privacy laws and frameworks we
should be analyzing the data? This seems totally like
putting the cart before the horse.<br>
<br>
Best,<br>
Kathy<br>
<br>
<br>
On 5/7/2016 4:22 PM, Holly Raiche wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Lisa<br>
<br>
What the data group has been exploring is just what
data is actually collected by registries/registrars.<br>
<br>
I realise that the original Charter questions were
framed around gTLD registration data - the 'Whois'
data that must be made public under the 2013 RAA.
But what the data group has identified is that there
is more data in question than just the 'Whois' data.
Yet these questions are framed around the gTLD data.<br>
<br>
Somewhere, there should be a question - or something
- that suggests that the Charter questions should go
further to at least consider what data is collected
and why, and whether it should be the subject of
data protections.<br>
<br>
Thanks<br>
<br>
Holly<br>
<br>
<br>
On 8 May 2016, at 2:57 am, Lisa Phifer <<a
moz-do-not-send="true"
href="mailto:lisa@corecom.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:lisa@corecom.com">lisa@corecom.com</a></a>>
wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear all,<br>
<br>
A reminder that PDP WG feedback if any on the
attached early outreach message is due no later
than tomorrow - Sunday 8 May 23.59 UTC.<br>
<br>
Best, Lisa<br>
<br>
At 12:07 PM 5/3/2016, Lisa Phifer wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Dear all,<br>
<br>
As agreed during today's WG call, attached
please find a slightly revised draft input
template to solicit early input from ICANN
SOs/ACs and GNSO SG/Cs. This is the template
discussed in today's WG call.<br>
<br>
Remember, there will be many opportunities for
community input throughout this PDP. The
attached input template is to be used to
initiate the early outreach required of every
PDP to inform the WG at the start of its work.
The template is a tool used successfully by
other PDP WG's to solicit structured input,
along with any additional input each group
wishes to provide.<br>
<br>
WG member feedback on this draft input template
is welcome: please send any feedback to the
entire WG list <<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a>>
no later than Sunday 8 May 23.59 UTC.<br>
<br>
Our goal is to send the final version of this
template to initiate early outreach next week.<br>
<br>
Best, Lisa<br>
<br>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
</blockquote>
<RDS PDP - SO AC SG C Input Template - 2 May
2016
rev.pdf>_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
</blockquote>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
</blockquote>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
</blockquote>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</body>
</html>