<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I don't know if I am the voice of caution here, or simply off the
playing field. <i>(That is what the Delete button is for.)</i>
But, I want to caution against something here. We can go two
directions in matching a data element to a purpose. We have been
using one approach and saying that a data element should only be
captured if there is an acceptable purpose. <br>
</p>
<p>In the proposed inclusion of the history of domains (how rich
(which data) and how far back?) we are slipping toward another
approach, starting with a purpose and proposing a (growing) set of
data elements that should be captured. I am not sure it is
practical, doable, or wise to start with purposes and cast a wide
data net. <br>
</p>
<p>We at least need to consider the merits of a purpose driven data
capture approach before getting into its details. Doing this is
not a forgone conclusion. <br>
</p>
<p>Sam L. <br>
</p>
<br>
<div class="moz-cite-prefix">On 9/21/2017 10:18 AM, Paul Keating
wrote:<br>
</div>
<blockquote type="cite" cite="mid:D5E99151.B257C%25Paul@law.es">
<pre wrap="">Hi Andrew,
Thanks for the response.
Are you advocating that this WG needs to expand the meaning of RDS to
include
the history of domains?
I do not see the difference. I want to make sure that the ³purposes² are
applicable to both current RDS data elements and those already captured.
It is unrealistic to presume that only current data will be retained.
And, historical data is consistent with purpose. For example, if ³a²
purpose is for security it would seem that this purpose applies not only
to current data elements but also to historical ones.
And, in any event, consideration must be given to the real application at
the collection level. I think it would be rather foolhardy to narrow our
focus on immediate collection and not also consider impact on data
retention. Otherwise we are handing the collectors a problem to deal with
in terms of monitoring their database 24/7.
Paul
On 9/21/17, 3:06 PM, "Andrew Sullivan" <a class="moz-txt-link-rfc2396E" href="mailto:gnso-rds-pdp-wg-bounces@icann.orgonbehalfofajs@anvilwalrusden.com"><gnso-rds-pdp-wg-bounces@icann.org
on behalf of ajs@anvilwalrusden.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
On Thu, Sep 21, 2017 at 02:54:40PM +0200, Paul Keating wrote:
</pre>
<blockquote type="cite">
<pre wrap="">It is also important to include purposes that would reach historical
data
that has already been collected.
</pre>
</blockquote>
<pre wrap="">
That would be an entirely new service from the existing RDDS. Are you
advocating that this WG needs to expand the meaning of RDS to include
the history of domains? Because as far as I know such a service is
not contractually required of registries or registrars today.
</pre>
<blockquote type="cite">
<pre wrap="">We also need to allow for the adoption of additional purposes in the
future.
As an example, 4 years ago WHOIS was not commonly used in cyber security
research. Today it is one of the more important tools used by all
investigators.
</pre>
</blockquote>
<pre wrap="">
I do not believe that it was not commonly used that way 4 years ago.
Indeed, when we stood up .info in 2001, I recall some of the feature
decisions we made were there for security-research reasons. Moreover,
you are suggesting that the list of reasons for collection needs to be
open ended, but my impression from the privacy commissioner input
we've had so far is that such an open-ended list is not allowed: if
you have a new purpose, you need to introduce that to the parties
whose data you are collecting and get explicit consent. So I think we
cannot do what you're envisioning here.
Best regards,
A
--
Andrew Sullivan
<a class="moz-txt-link-abbreviated" href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>
_______________________________________________
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>
<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>
<pre class="moz-signature" cols="72">--
------------------------------------------------
"It is a disgrace to be rich and honoured
in an unjust state" -Confucius
邦有道，贫且贱焉，耻也。邦无道，富且贵焉，耻也
------------------------------------------------
Dr Sam Lanfranco (Prof Emeritus & Senior Scholar)
Econ, York U., Toronto, Ontario, CANADA - M3J 1P3
email: <a class="moz-txt-link-abbreviated" href="mailto:Lanfran@Yorku.ca">Lanfran@Yorku.ca</a> Skype: slanfranco
blog: <a class="moz-txt-link-freetext" href="https://samlanfranco.blogspot.com">https://samlanfranco.blogspot.com</a>
Phone: +1 613-476-0429 cell: +1 416-816-2852</pre>
</body>
</html>