Dear All, The Expedited Policy Development Process Team of the GNSO is considering the Temporary Specification for gTLD Registration Data and is seeking the written opinion on the topic from each Supporting Organization, Advisory Committee and GNSO Stakeholder Group / Constituency (see below). I am sure that individual ccTLDs have a lot of experience with registration data and GDPR compliance they would like to share with the team. Although the ccNSO did not appoint official members to the EPDP team, ccTLDs are welcome to provide advice and support to the team. Any such feedback from ccTLDs will not be viewed as the official position of the ccNSO. However, the EPDP team would appreciate if all feedback from ccTLDs would be consolidated and sent in one package. Therefore, if you have any comments or suggestions, please send them to ccnsosecretariat@icann.org or to me. Thank you! Kind regards, ]{atrina ----- To: ICANN Supporting Organizations / Advisory Committees / GNSO Stakeholder Groups / GNSO Constituencies From: EPDP Team on the Temporary Specification for gTLD Registration Data Subject: EPDP Team Request for Early Input 1 August 2018 Dear Community Leader: I am writing you on behalf of the Expedited Policy Development Process Team that is considering the Temporary Specification for gTLD Registration Data. In accordance with the GNSO Policy Development Process, we are seeking the written opinion on the topic from each Supporting Organization, Advisory Committee and GNSO Stakeholder Group / Constituency. While every Supporting Organisation and Stakeholder Group has been invited to participate in the discussion, we still wish to comply of this Policy Develop Process requirement and afford you the opportunity to make a written submission. As this is an expedited policy development, we are going to take advantage of the tighter timeframe afforded to us and require the input in 21 days from today, i.e., on 22 August. We do so because: the working group will start substantive discussions immediately, so timely input is required if it is to be considered, every ICANN stakeholder group has been afforded the opportunity to participate in the working group so the opportunity for this early input is somewhat redundant, and we will provide an additional opportunity with a lengthier timeframe for written input on more complex issues such as the provision of access to full non-public registration data. There are three deliverables set out in the GNSO Charter, that we will work on and deliver in order: a triage document of the Temporary Specification, which includes items that have the Full Consensus support of the EPDP Team that these should be adopted as is. an Initial Report which will include the items that received full consensus support per the triage document as well as all other items of the Temporary Specification (not including the Annex) that were considered and deliberated upon an Initial Report outlining a proposed model of a system for providing accredited access to non-public registration data Given the tight timeframe, it is recommended that you focus your early input focus on the first two deliverables only. (As stated above, we will provide an opportunity for input on the more complex issue of “access” in the near future.) To make the most effective comment and have it folded cleanly and clearly into the team’s documentation library, your written response should: Clearly identify the section of the Temporary Specification on which you are commenting, either by line numbers or paragraph. Then clearly state whether your respective group: Supports that section as is (where clearly labelled rationale is optional), Supports that section with modification with substitute language provided and clearly labeled rationale, or Supports the elimination of the section with clearly labeled rationale Comments without clearly labelled rationale will probably not add much to the discussion as we are attempted to develop consensus through collaboration and not voting. If you do not comment on a specific section of the document, that absence will not be taken as assent or any other opinion. Of course, you are welcome to provide any other input that you deem helpful in facilitating the EPDP Team’s deliberations, but as to the immediate deliverables of the working group, your input on the questions outlined above will be most valuable. Please submit your response to gnso-secs@icann.org. Timely input will be summarized in a document and provided to the team. Input received after the due date may be introduced into the discussion by you stakeholder group representative, ICANN staff support or me as the pertinent topic arises. Thank you very much and I look forward to receiving your input. You can contact me anytime via email (kurt@kjpritz.com). On behalf of the EPDP Team, Kurt Pritz EPDP Team Chair Background On 17 May 2018, the ICANN Board of Directors (ICANN Board) adopted the Temporary Specification for generic top-level domain (gTLD) Registration Data (“Temporary Specification”) pursuant to the procedures for the establishment of temporary policies in ICANN’s agreements with Registry Operators and Registrars (“Contracts”). The Temporary Specification provides modifications to existing requirements in the Registrar Accreditation and Registry Agreements to help bring them into compliance with the European Union’s General Data Protection Regulation (“GDPR”). Per the procedure for Temporary Policies as outlined in the Contracts, following adoption of the temporary specification, the Board “shall immediately implement the Consensus Policy development process set forth in ICANN’s Bylaws”. Per the requirements of the procedure for Temporary Policies, this Consensus Policy development process on the temporary specification would need to be carried out within a one-year period as the Temporary Specification can only remain in force for up to 1 year, from the effective date of 25 May 2018. At its meeting on 19 July 2018, the GNSO Council initiated an Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data and adopted the EPDP Team Charter. The charter outlines a number of questions that the EPDP Team is expected to answer. The scope of the EPDP Team’s efforts includes confirming, or not, the Temporary Specification by 25 May 2019 (the date the Temporary Specification will expire). Additionally, the proposed scope includes discussion of a standardized access model to nonpublic registration data; however, the discussion of a standardized access model will occur only after the EPDP Team has comprehensively answered a series of “gating questions”, which have been specified in the EPDP Team’s Charter.