Hello again Steve and everyone,

FYI that the session description is now up on the ICANN64 public meeting schedule: https://64.schedule.icann.org/meetings/961913. I hope it is all right that staff took the liberty of not including a mention of the GNSO Council vote, as that will take place only on 4 March and the schedule is viewable as of today. We will be sure to update the description accordingly following the Council’s vote.

Once again, we remain available to assist you with planning and managing the session. Please feel free to use this thread to continue any discussions you may wish to have as regards organizing the session. Thank you!

Cheers

Mary

Thank you, Steve! All, unless anyone has concerns about the proposed session description, we will proceed to post it for now to the public schedule (understanding, of course, that it can be updated following additional discussions among this group)

Thanks and cheers

Mary

Here’s a proposed Session Description for “Next Steps in ICANN’s Response to the GDPR”

The EU’s General Data Protection Regulation (GDPR) took effect May-2018, prompting ICANN Org to change how it enforces Whois policies. The GNSO launched an expedited policy development process (EPDP) to replace a Temporary Specification that expires May-2019.  Last month, the EPDP produced policy recommendations to replace the Temporary Specification, as approved by the GNSO Council on 4-Mar. The ICANN Board is now accepting public comments before it votes to approve the EPDP policy.

That’s what happened so far with GDPR and Whois.  This session will focus on What Happens Next:  

ICANN Org will work with a GNSO Implementation Review Team on details for the new policy. 

The EPDP will resume its work to resolve open questions from and to develop policy for a system for standardized access to non-public registration data (also known as a Unified Access Model)

ICANN Org and its Technical Study Group will continue work on technical means to support a Unified Access Model.

ICANN Org will continue exploring legal framework to support a Unified Access Model.

GNSO must decide whether and how to re-start policy development work that had been set aside during the EPDP, including Privacy & proxy services and the procedure for Whois conflicts with Privacy Law. 

GNSO might even resume work on a new policy framework for registration directory services (RDS).

Attend this session to understand and comment on policy work to reconcile ICANN’s Whois policies with privacy laws and legitimate needs for registrant data.

Dear all,

This note is just a follow up to the initial message from last week (below). As mentioned, we need to upload ASAP at least a tentative placeholder Session Description to the public meeting schedule (https://64.schedule.icann.org/meetings/961913 [64.schedule.icann.org]) to inform community members as they begin to plan their ICANN64 meeting schedules.

We also hope that, by putting together via this email thread all the community leaders who have expressed interest in either planning or having their community groups participate in that session, we can help facilitate a discussion as to the objectives, desired outcomes, preferred format and speaker line-up. In that regard, I’ve been reminded that I should have included Donna Austin (RySG) in the original email, so I have taken the liberty of adding her name to this follow up note.

As always, please let Cyrus and me know how Org can assist with the planning, management and logistics of this important session. Thank you!

Cheers

Mary

Dear Steve (and cc’ing Manal, Maureen, Bruna and Rod),

I am writing to you as the chairs of the SO/AC/SG/C groups that had expressed interest in planning the ICANN64 Cross Community session on “Next Steps in ICANN’s Response to the GDPR”, scheduled for Monday 11 March at 15.15. I believe that this was a session that had first been proposed by the BC and that, after the last planning call, there is general agreement amongst the community leaders that the session ought to combine a number of other proposals and suggestions (e.g. a unified access model and other specific topics that may be of interest based on the work of the Expedited PDP Team).

As we approach the final run-up to ICANN64, I hope that this email will serve to kick off further discussions as to the scope and format of the session. In this regard, please note the following points:

• In accordance with what has become the regular practice, Cyrus (cc’d) will be ICANN org’s designated senior executive for the session.
• Members of the Policy Team (including me and Carlos Reyes) will be available to assist you with coordination, logistics, programming and overall management of the session. As such, we will need the following information at your earliest convenience:
  • A session description (for posting on the public schedule and meeting website) – this is the most urgently needed item at this point so even a placeholder description that can provide basic information to attendees looking at the meeting schedule will be fine; and
  • Your preferred format and room setup (e.g. will it be run as a panel with a moderator; how many speakers/panelists and who they are; how you wish to handle audience interaction and Q&A etc.).

Steve, as the BC initially proposed the session, perhaps you have some ideas that you can share with Cyrus and the group. Thank you all!

Best regards,

Mary