[Gnso-epdp-team] Input requested on BC input in relation to recommendation 9
alan at donuts.email
Thu Feb 7 13:16:47 UTC 2019
Sorry to be the continuous wet blanket here, but again I need to call a
halt to overreach and assumptions.
The ORG process discussions regarding consent for that field, has always
been about consent obtained by the registrar for the registrar's processing
of the data. We have NOT discussed the transfer, or logging of this consent
by the registry, or how basic matters such as change of mind / article 17 /
subsequent opt-out of the registrant would be properly notified, achieved
or even legally arranged by the registry.
I therefore we do NOT support the additional line from the BC as written, a
as it completely circumvents the discussion necessary to achieve GDPR
The Registries therefore will only support, *at this time*, the
recommendation as was discussed, and that is one that concerns the direct
relationship and consent of a registrant with the registrar. We therefore
propose the following update as clarification.
*After the implementation phase-in period, the ORG FIELD will no longer be
REDACTED by the registrar. *
NOTE: I will defer to my Registrar colleagues as to the assumptions of the
remainder of the insertion.
[image: Donuts Inc.] <http://donuts.domains>
Senior Compliance & Policy Manager, Donuts Inc.
15-18 Earlsfort Terrace
Dublin 2, County Dublin
Please NOTE: This electronic message, including any attachments, may
include privileged, confidential and/or inside information owned by Donuts
Inc. . Any distribution or use of this communication by anyone other than
the intended recipient(s) is strictly prohibited and may be unlawful. If
you are not the intended recipient, please notify the sender by replying to
this message and then delete it from your system. Thank you.
On Wed, Feb 6, 2019 at 5:27 PM Marika Konings <marika.konings at icann.org>
> Dear Registrar Team, all,
> Per today’s action item, you are requested to provide your input on the BC
> suggestion that in relation to recommendation 9 – Organization field:
> *“**Instead of a “via a process that can be determined by each
> registrar” we should have concrete steps that can be enforced by ICANN.
> Could the registrars identify some reasonable steps for this process?*
> *ADD: After the implementation phase-in period, the ORG FIELD will no
> longer be REDACTED by either the registry or registrar. “*
> Your feedback on this input is appreciated.
> Caitlin, Berry and Marika
> *Marika Konings*
> *Vice President, Policy Development Support – GNSO, Internet Corporation
> for Assigned Names and Numbers (ICANN) *
> *Email: marika.konings at icann.org <marika.konings at icann.org> *
> *Follow the GNSO via Twitter @ICANN_GNSO*
> *Find out more about the GNSO by taking our interactive courses
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses_gnso&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=Cg5uQf0yAfw-qlFZ0WNBfsLmmtBNUiH0SuI6Vg-gXBQ&e=> and
> visiting the GNSO Newcomer pages
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=tT-E2RoAucUb3pfL9zmlbRdq1sytaEf765KOEkBVCjk&e=>. *
> Gnso-epdp-team mailing list
> Gnso-epdp-team at icann.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnso-epdp-team