[IRT.RegDataPolicy] Accidentally resolving comments in the google doc

[Sarah Wyld]

Hello team,

I was also surprised to see ‘publication’ in the definition; I did not recall noticing that at our most recent meeting, but in looking at the document history and Zoom recording I see it was added as a suggestion by the ICANN staff team on November 18 before our meeting began. It looks like on Nov 20 there was a further change to the text by an IRT member which took those words from suggest-mode to final-mode, perhaps unintentionally. 

Regardless, I would still suggest that our definition should be broad (“related to Domain Name Registration Data”) without mentioning access, disclosure, or publication. Those functions fall under the applicable Registry Agreements, Registrar Accreditation Agreement, and ICANN Consensus Policies to which the definition refers, and so can happen whenever appropriate. The definition need neither require nor prohibit those processing activities.

Thank you,

-- 
Sarah Wyld, CIPP/E

Policy & Privacy Manager
Tucows
swyld at tucows.com 
+1.416 535 0123 Ext. 1392



From: Alex Deacon
Sent: November 25, 2020 5:01 PM
To: Sarah Wyld
Cc: irt.regdatapolicy at icann.org
Subject: Re: [IRT.RegDataPolicy] Accidentally resolving comments in the google doc

For the record I object to the new definition of RDDS which narrows it to only publication of public data.   We can't be making such a major change at this point in the game. 

As I mentioned on the last call, I took an action to sync with my team and propose something to the list.   I hope to do this asap - and by the end of the day on Monday at the latest (given the US thanksgiving holiday). 

Alex

___________
Alex Deacon
Cole Valley Consulting
alex at colevalleyconsulting.com
+1.415.488.6009



On Mon, Nov 23, 2020 at 8:09 AM Sarah Wyld <swyld at tucows.com> wrote:
Hi Team,
 
I noticed this morning that the comment on our shared OneDoc which provided the CPH-proposed definition for RDDS had been resolved. I know it’s unfortunately easy to click on the wrong thing and resolve a comment when perhaps one might have intended to click through to a different point on the page.
 
As I don’t think this issue has been fully determined, I have added a new comment with the same proposed definition, to ensure we don’t lose track of the suggestion.
 
Thank you,
 
-- 
Sarah Wyld, CIPP/E
 
Policy & Privacy Manager
Tucows
swyld at tucows.com 
+1.416 535 0123 Ext. 1392
 

 
_______________________________________________
IRT.RegDataPolicy mailing list
IRT.RegDataPolicy at icann.org
https://mm.icann.org/mailman/listinfo/irt.regdatapolicy

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20201127/dd9b6dd5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 8E0FDA9E817547538AFE55E560C2FAD1.png
Type: image/png
Size: 13868 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20201127/dd9b6dd5/8E0FDA9E817547538AFE55E560C2FAD1.png>