ICANN 59 Report from the NCUC Rep to NCSG ExCom

[Zalnieriute, Monika]

Dear NCSG members,



I, Monika Zalnieriute, have attended ICANN 59, Policy Forum, 26 – 29th June in Johannesburg, as a NCUC Representative to the NCSG Executive Committee, and I am writing to inform You briefly of my activities during that meeting.


By the way of background, the NCSG Executive Committee is responsible for working with the NCSG Chair to make sure the NCSG functions according to its mission and principles. The NCSG-EC is responsible for supervising and monitoring the NCSG Chair’s performance of executive functions, and the NCSG-EC may call for a new chair election. The NCSG‑EC is also responsible for establishing and overseeing membership criteria, rules, as well as reviewing and approving applications to form new Constituencies in accordance with the Section 2.3 of the NCSG Charter and any applicable Constituency Recognition Process approved by the ICANN Board of Directors. The NCSG-EC’s formation, functions, composition and duties within the NCSG are set out in Section 2.4 of the NCSG Charter.



During the Policy Forum in Johannesburg, I have participated in the following meetings:

·      Outreach sessions and strategy sessions of the NCSG (26 June 08:00; and 27 June 08:00),

·      GNSO Council working session (26 June 09:00)

·      Cross – Community Discussion on Next-Generation gTLD RDS Policy Requirements (26 June, 15:15)

·      GNSO New gTLD Subsequent Procedures PDP Working Group Face-to-Face Meeting(27 June, 08:30)

·      GAC Human Rights and International Law Working Group Session<https://schedule.icann.org/event/B49B/gac-human-rights-and-international-law-working-group-session> (27, 11:15)

·      GDPR and its potential impact: looking for practical solutions<https://schedule.icann.org/event/B3ot/gdpr-and-its-potential-impact-looking-for-practical-solutions> (27, 15:15)

·      Cross Community Discussion – Geographic Names at the Top-Level Session (27 June, 17:00)

·   New gTLD Registration Directory Services (RDS) to replace WHOIS Policy Development Process Working Group(28 June, 08:30)

·      NCSG Executive Committee Meeting, (28 June, 09:00)

·      NPOC Constituency Day (28 June, 10:30)

·      GNSO Council Public Meeting (28 June, 13:00)

·      NCUC Policy Session (28 June 17:00)

·      RPMs in all gTLDS PDP Working Group Meeting (29 June, 09:00)

·      GNOS Wrap-Up Session (June 29; 13:30)

·      Cross Community Discussion – Geographic Names at the Top-Level Session II<https://schedule.icann.org/event/B3pD/cross-community-discussion-geographic-names-at-the-top-level-session-ii> (June 29; 15:15)



In addition to these formal meetings and my duties on the NCSG ExCom, during ICANN Policy Forum, I have strategized and planned future policy contributions in the following areas:



·      Rights Protection Mechanisms (RPMs)



In the area of Rights Protection Mechanisms (RPMs) I have discussed the future research strategies on trademarks and intellectual property policies of ICANN with Kathy Kleiman (who is a chair of the RPM working group), and discussed the potential uses of my legal research work on the Uniform Dispute Resolution Policy in particular, and how it could be used as a strategic input from NCUC/NCSG when the UDRP reform comes up in a Phase II of the RPMs Review. I have drafted a detailed report on the UDRP from the human rights perspective, which could provide a useful basis for discussions both within the RPMs PDP working group, and also be useful for the NCUC/NCSG. Some NCUC members, such as Robin Gross and Stephanie Perrin, has already commented on the drafts of this report, and revised version will be submitted for more general NCUC comments soon.



·      Data Protection, Privacy and GDPR



During the Policy Meeting in Johannesburg, as NCSG representative, together with Stephanie Perrin and Wendy Seltzer, I have been appointed to the special ICANN GDPR (General Data Protection Regulation) Compliance Consultation Group however, due to numerous other commitments, I could not accept this appointment and this position was transferred to Ayden Ferdeline, who is in a much better position to actively contribute to this very intensiv taskforce.  However, this does not mean, I will not be providing my data protection/privacy expertise, because I have extensively discussed the future strategy and potential contributions of the NCUC/NCSG to the data protection/privacy policies of ICANN with Council of Europe representative Peter Kimpian, with whom we agreed to explore the opportunities for a detailed report on ICANN & EU General Data Protection Regulation in the near future. This line of work has been proposed and debated/planned a year ago (and involves an official EU agency, in addition to the Council of Europe), and now the situation and circumstances within ICANN regards the increased attention to the General Data Protection Regulation seem to be suitable for such a report. I will update the NCUC regarding this work regularly.



If You have any questions or ideas regarding any of the above mentioned issues and potential contributions, please feel free to contact me



Best wishes,



Dr Monika Zalnieriute,

Your NCUC Rep to NCSG Executive Committee








Kind regards,



Dr. Monika Zalnieriute



Post-Doctoral Fellow @ Melbourne Law School |

The University of Melbourne I law.unimelb.edu.au I

185 Pelham St, Carlton VIC 3053, Australia I



Visiting Fellow @ Center for Media, Data and Society I

Central European University I cmds.ceu.edu I



Representative @ Executive Committee I

Non-Commercial Stakeholder Group I ICANN I icann.org I









The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination, distribution, forwarding, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited without the express permission of the sender. If you received this communication in error, please contact the sender and delete the material from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20170802/1f8b1722/attachment.htm>