At-Large Workspace: ICANN Seeking Community Feedback on Proposed Unified Access Model
Public Comment Close | Statement | Status | Assignee(s) | Call for | Call for | Vote Open | Vote Close | Date of Submission | Staff Contact and Email | Statement Number |
|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
Hide the information below, please click here
FINAL VERSION SUBMITTED (IF RATIFIED)
The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote.
FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC
The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.
DRAFT SUBMITTED FOR DISCUSSION
The first draft submitted will be placed here before the call for comments begins. The Draft should be preceded by the name of the person submitting the draft and the date/time. If, during the discussion, the draft is revised, the older version(S) should be left in place and the new version along with a header line identifying the drafter and date/time should be placed above the older version(s), separated by a Horizontal Rule (available + Insert More Content control).
From:Tijani BEN JEMAA
Sent:Thu, 12 Jul 2018 18:34:43 +0100
Subject:Re: [ALAC] Draft Principles for GDPR
Alan,
I see that you exclude the registrants from the Users: Quit interesting….
Registrants are users and our duty is to defend the interest of both registrant and not registrant users.
For more clarity, I wouldn’t accept that criminals use domain names to harm users. This doesn’t mean that I accept to use the registrant data for other purpose than the one they were collected for.
In my opinion, if we are to fix principles to our representatives in the EPDP, it should be through a large consultation among the whole at-large community, means the ALSes, individual members, RALOs and ALAC, not only the 15 members of ALAC and the few people around them. An official call for comment in a well communicated wiki page should be sent to all the RALO lists and the ALAC one.