[gnso-rds-pdp-wg] Now open: 18 January Poll on Purpose

Wed Jan 25 17:09:23 UTC 2017

Stephanie

Sorry, but policy + the technology go hand in hand. You cannot completely separate them and any policy that this (or any other) group produces needs to be technically possible to implement.

As to the specifics ..

I would argue that generated data is NOT collected, as it’s generated.

If you register stephanieperrin.com with us the only elements we are “collecting” that end up in in the “thin” data are:

the domain name string

the nameservers you’re using (and if you don’t specify any we’ll use our own)
All the other elements are NOT collected by the registrar or even the registry from the registrant, they are generated as part of the process of the domain being registered.

Regards

Michele

--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
https://www.blacknight.com/
http://blacknight.blog/
Intl. +353 (0) 59  9183072
Direct Dial: +353 (0)59 9183090
Social: http://mneylon.social
Some thoughts: http://ceo.hosting/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 370845

From: Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>
Date: Wednesday 25 January 2017 at 11:56
To: Sam Lanfranco <sam at lanfranco.net>, Michele Neylon <michele at blacknight.com>, David Cake <dave at davecake.net>
Cc: "gnso-rds-pdp-wg at icann.org" <gnso-rds-pdp-wg at icann.org>
Subject: Re: [gnso-rds-pdp-wg] Now open: 18 January Poll on Purpose

Sorry, this discussion is important.  Your example proves my point.  What you show below is a disclosure.  It is a disclosure of a limited set of data.  we are not supposed to be talking about disclosure at this point in our proceedings.  I leave it to the experts on whether this is "thin" in the sense of the thick transition discussion, I really don't know because we are focused on gTLD policy here.  My point is this is a disclosure.  We do not "collect" thin data per se, we collect a whole mess of mandatory data elements, as per the RAA.  Then we generate a whole mess as part of activating and making real the domain's existence.  Then we share (release) a small subset.

So talking about collecting thin data is misleading in my view.  Purpose of disclosing it is what we are in fact talking about. Calling it a purpose for collection opens the barn door.

Stephanie

On 2017-01-25 06:46, Sam Lanfranco wrote:
Thank you Michele, ( ignoring the spell check driven typo of "think" for "thick" (-: ). We should be able to put this "thin" discussion behind us.
The "thin" discussion should have taken about 2 email exchanges. Here is CIRA's (thin) search for .ca domain names [disclosure: it is my domain name]

Domain name: artisanalpot.ca
Domain status: registered
Creation date: 2016/12/14
Expiry date: 2017/12/14
Updated date: 2016/12/19
DNSSEC: Unsigned
Registrar:
Name: Web Hosting Canada (7081936 Canada Inc.)
Number: 5000080
Name servers:
ns1.whc.ca 173.209.49.178
ns2.whc.ca 198.245.53.176
ns3.whc.ca 198.245.61.86
% WHOIS look-up made at 2017-01-25 11:32:24 (GMT)
% Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal
% Notice, available at http://www.cira.ca/legal-notice/?lang=en
% (c) 2017 Canadian Internet Registration Authority, (http://www.cira.ca/)

Nothing private is disclosed and LEA would have to resort to legal means to get to what is in the "thick" data set.
There are no ICANN policy  issues here.

Sam L <artisanalpot.ca> (-:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20170125/823f2ce8/attachment.html>