Thanks Maureen for forwarding this

 

Hadia

 

From: ALAC [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Maureen Hilyard
Sent: Tuesday, March 05, 2019 1:21 AM
To: ALAC
Subject: [ALAC] Fwd: FOLLOW UP (Re: ICANN64 Cross Community Session: Next Steps in ICANN's Response to the GDPR)

 

FYI

---------- Forwarded message ---------
From: Steve DelBianco <sdelbianco@netchoice.org>
Date: Tue, Mar 5, 2019 at 6:24 AM
Subject: Re: FOLLOW UP (Re: ICANN64 Cross Community Session: Next Steps in ICANN's Response to the GDPR)
To: Mary Wong <mary.wong@icann.org>
Cc: Chantelle Doerksen <chantelle.doerksen@icann.org>, Carlos Reyes <carlos.reyes@icann.org>, Cyrus Namazi <cyrus.namazi@icann.org>, Bruna Santos <bruna.mrtns@gmail.com>, Maureen Hilyard <maureen.hilyard@gmail.com>, Manal Ismail <manal@tra.gov.eg>, Rod Rasmussen <rod@rodrasmussen.com>, Maria Otanes <maria.otanes@icann.org>, Austin, Donna <Donna.Austin@team.neustar>

 

Mary – now that the Council vote is done, could you please update the Kobe session description as follows:

 

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 will be accepting public comments before it votes to approve the EPDP policy recommendation.

 

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.
  • The ICANN community must consider how to update existing policies and procedures to ensure consistency with the EPDP recommendations, including: Consistent Labeling and Display Policy; Thick WHOIS Transition Policy for .COM, .NET, .JOBS; UDRP and URS Rules; Transfer Policy and TDRP; and WHOIS Data Reminder Policy.
  • GNSO must decide whether and how to re-start work that may be dependent on the outcomes of the EPDP, including Privacy & Proxy Services accreditation issues and the procedure for handling Whois conflicts with Privacy Law. 

 

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.

--