[council] FW: [Gnso-epdp-team] EPDP Phase 2A Chair Update to GNSO Council -- Initial Report

Wed Jun 9 15:12:46 UTC 2021

Dear Councillors,
Please see the EPDP P2A chair's update to Council regarding the Initial Report of the EPDP.
In particular, you will note Keith's characterisation of where the team is in terms of identifying new consensus policy elements, what is expected from the public comment in this regard along with the five areas where specific inputs are sought as they relate to their chartered goals. The WG remains on track for a Final Report end of August.
An update is scheduled for our call next week on this.
You will find the public comment page & initial report here https://www.icann.org/public-comments/epdp-phase-2a-initial-report-2021-06-03-en.
Regards,
Philippe

From: Gnso-epdp-team [mailto:gnso-epdp-team-bounces at icann.org] On Behalf Of Drazek, Keith via Gnso-epdp-team
Sent: Tuesday, June 8, 2021 12:35 AM
To: gnso-chairs at icann.org
Cc: gnso-secs at icann.org; gnso-epdp-team at icann.org
Subject: [Gnso-epdp-team] EPDP Phase 2A Chair Update to GNSO Council -- Initial Report

Dear GNSO Council Leadership Team,
In my capacity as Chair of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data (Phase 2A), I am pleased to report to the GNSO Council that the Phase 2A team has finalized its Initial Report for public comment. The Initial Report includes a status update on the deliberations of the EPDP 2A team and primarily poses questions around five key issues and possible recommendations for community feedback. The public comment period will run for 45 days from 03 June to 19 July 2021.
The EPDP 2A team has not yet reached consensus on whether there should be new consensus policy elements, amendments to the existing Phase 1 recommendations, or if the existing policies are sufficient at this time. This is a key area of focus for the community during the public comment period and the EPDP 2A team looks forward to considering all inputs, and especially new information, as we work to develop policy recommendations in a Final Report.
The five key areas where new community input is requested are:

  1.  As the report indicates, there are substantially different views on the question of whether changes are needed to the Phase 1 recommendation which allows for differentiation between legal and natural person data, but does not require it. Some are of the view that changes are warranted, while others believe that the Phase 1 recommendation does not require changes at this time.

  1.  The EPDP Team has noted there are a number of potential relevant developments such as NIS2, decisions by pertinent tribunals and data protection authorities, as well as the possible adoption of the Phase 2 recommendations on a Standardized System for Access and Disclosure (SSAD) that may require, or benefit from, a renewed consideration of the question of whether any further policy changes are necessary. The EPDP Phase 2A preliminary recommendation included in the Initial Report suggests that the Council should monitor these developments to decide if/when (re)consideration is warranted, while others have suggested that this is already the responsibility of the Council and as such, neither monitoring nor specific triggering points need to be specifically called out. Community input is sought on if/how this recommendation is necessary for future GNSO Council consideration of any new policy work. Further information from the Council on how this monitoring suggestion is helpful is also welcomed.

  1.  As a possible new requirement, the EPDP Team has discussed the introduction of a standardized data element to facilitate and harmonize practices for those Contracted Parties who do choose to differentiate between legal and natural person data, but some important questions remain and are called out in the Initial Report, as follows:

     *   Should a standardized data element be available for a Contracted Party to use? If yes, why? If no, why not? Why is harmonization of practices beneficial or problematic?
     *   If yes, what field or fields should be used and what possible values should be included, if different from the ones identified in the Initial Report (Registrant Legal Person - Yes/No/Unspecified)?
     *   If such a standardized data element is available, MUST a Contracted Party who decides to differentiate use this standardized data element or should supporting this standardized data element remain optional for a Contracted Party that implements this differentiation?

  1.  The EPDP Team has developed guidance for Contracted Parties who choose to differentiate but there are a number of questions that are put out for community input:

     *   Does this guidance as written provide sufficient information and resources to Registrars and Registry Operators who wish to differentiate? If not, what is missing and why?
     *   Are there additional elements that should be included?
     *   Are there legal and regulatory considerations not yet considered in this Initial Report, that may inform Registries and Registrars in deciding whether and how to differentiate, and if so, how?
     *   If a Registrar or Registry Operator decides to differentiate, should this guidance become a requirement that can be enforced if not followed ("MUST, if Contracted Party decides to differentiate")?

  1.  The EPDP Team has put forward a preliminary recommendation that Contracted Parties who choose to publish a registrant- or registration-based email address in the publicly accessible RDDS should ensure appropriate safeguards for the data subject in line with relevant guidance on anonymization techniques provided by their Data Protection Authority(ies) and the appended legal guidance in this recommendation. The EPDP Team asks:

     *   Does this guidance as written provide sufficient information and resources to Registrars and Registry Operators who wish to publish a registrant- or registration-based email address?
     *   If not, what is missing and why?
In summary, irrespective of whether consensus is ultimately reached on the above issues, the EPDP 2A Team will continue working during the public comment period to ensure we remain on track for publication of a Final Report by the end of August 2021. The EPDP 2A Team appreciates the ongoing support of the GNSO Council as we conduct this important policy work, and we very much look forward to receiving, reviewing, and incorporating the community's feedback.
Please advise if the GNSO Council has any follow-up questions for the EPDP Phase 2A team.
Sincerely,
Keith Drazek

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20210609/93feb32c/attachment-0001.html>