April 2019 - Gnso-epdp-team

FW: Reminder - input on mind map and questions coming out of ICANN64 meeting
by Georgios.TSELENTIS＠ec.europa.eu April 8, 2019

April 8, 2019

Dear EPDP colleagues, Apologies for the lateness of our response. The GAC supports what Alex from the IPC articulated in his email from March 29. We would like to further propose that Work Stream 1 (Standardized Access) be given priority. Also, the GAC suggests that the EPDP immediately identify the scope of Work Stream 1 and develop a work plan for completing work no later than 12 months from the appointment of the new EPDP Chair. It should also be the expectation that considerable and demonstrable progress be made by ICANN 66 in Montreal. Such an approach and timeframe would meet the community feedback from Kobe asking for Phase 2 of the EPDP to move forward quickly given the importance of the issues involved. Further, we felt it worth noting GAC advice from Kobe specific to this effort: WHOIS and Data Protection Legislation a. The GAC advises the Board to: i. Take necessary steps to ensure that the GNSO EPDP on the Temporary Specification for gTLD Registration Data institutes concrete milestones, progress reports and an expeditious timeline, similar to Phase 1, for concluding Phase 2 activities; ii. Take necessary steps to ensure that the scope of phase 2 activities is clearly defined with a view to expeditious conclusion and implementation; iii. Make available the necessary resources for Phase 2 to expeditiously advance on the complex legal issues deferred from Phase 1; iv. Consider instituting additional parallel work efforts on technical implementations, such as that carried out by the Technical Study Group, for purposes of informing and complementing the EPDP’s Phase 2 activities; v. Facilitate swift implementation of the new Registration Directory Services policies as they are developed and agreed, including by sending distinct parts to implementation as and when they are agreed, such as the questions deferred from Phase 1; vi. Consider re-starting implementation processes for relevant existing policies, such as the Privacy Proxy Services Accreditation Issues Policy. RATIONALE The GAC has consistently advised on the necessity of finding a swift solution to ensuring timely access to non-public registration data for legitimate third party purposes that complies with the requirements of the GDPR and other data protection and privacy laws, in view of the significant negative impact of the changes in WHOIS accessibility on users with legitimate purposes. The GAC has previously noted that such legitimate purposes include civil, administrative and criminal law enforcement, cybersecurity, consumer protection and IP rights protection. The GAC also notes that the European Data Protection Board, in its guidance, has expressly encouraged ICANN and the community to develop a comprehensive model covering the entirety of the data processing cycle, from collection to access. As already highlighted in the GAC’s Puerto Rico Communiqué, the GDPR provides for mechanisms to balance the various legitimate public and private interests at stake, including privacy and accountability. We note that the legitimate interests reflected in ICANN’s Bylaws are consistent with the recitals to the GDPR, which provide examples such as “preventing fraud”; “ensuring network and information security,” including the ability to resist “unlawful or malicious actions” and reporting possible “criminal acts or threats to public security” to authorities (see GDPR Recitals 47, 49 and 50). The GAC will closely monitor and assess the progress reports prepared by the GNSO EPDP, and reserves the possibility of providing further guidance if the pace of progress so requires. The GAC notes that the time and resources necessary to complete Phase 2 are considerable and require focused scoping of the activity to ensure the expeditious conclusion of the activity. The GAC would therefore encourage a judicious definition of the scope of the Phase 2 efforts, giving consideration to elements that could be provided by Community efforts in parallel and may not need to be included in the scope, such as accreditation models. The GAC received a briefing on the work of the Technical Study Group. The GAC considers that the development of options for technical implementation demonstrates how a future system for RDS access could be implemented, also with a view to data security and privacy considerations. The Phase 2 considerations could benefit from further exploration of technical implementation options. In addition, engaging in such considerations in parallel can help ensure that policies - once agreed - are swiftly put into practice. Kind regards, Georgios Tselentis [cid:image001.gif@01D40705.22489500] European Commission Directorate-General for Communication Networks, Content and Technology E3: Next-Generation Internet BU31 05/70 B-1049 Brussels/Belgium Office: +32 229 99923 Mobile: +32 498 999923 https://ec.europa.eu/digital-single-market/en/policies/next-generation-inte… ________________________________ From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org<mailto:gnso-epdp-team-bounces@icann.org>> on behalf of Alex Deacon <alex(a)colevalleyconsulting.com<mailto:alex@colevalleyconsulting.com>> Sent: Friday, March 29, 2019 1:39 AM To: Marika Konings Cc: gnso-epdp-team(a)icann.org<mailto:gnso-epdp-team@icann.org> Subject: Re: [Gnso-epdp-team] Reminder - input on mind map and questions coming out of ICANN64 meeting Thanks Marika, Here are the IPCs thoughts on your questions and how to best proceed with the Phase 2 work. Method We believe the Phase 2 work should occur in two separate and concurrent work streams. · Work Stream 1 will focus on issues and questions related to the system for standardized access to non-public registration data, as defined in the EPDP charter and the overlapping EPDP Team Recommendation #3. · Work Stream 2 will focus on completing Phase 1 issues. We also believe that the "legal small team" should continue to meet concurrent with the two work streams described above, with the focus of drafting questions to our legal resource specific to our phase 2 work and analyzing responses received (both existing and TBD). Additional thoughts · Each work stream should set and work forward on its own schedule and work plan. In fact we suggest that a separate report should be generated for each work stream. · Each work stream should schedule its own separate weekly 90min meeting. Access to these meetings is open to all EPDP members (and alternates per the charter). · In a lesson learned from phase 1, consensus calls should happen early and often. Prioritization Legal Small Group Priorities · We suggest the first priority for this team is to answer the controllership and legal basis question for a system for Standardized for Standardized Access to Non-Public Registration Data, assuming a technical framework consistent with the TSG, and in a way that sufficiently addresses issues related to liability and risk mitigation with the goal of decreasing liability risks to Contracted Parties through the adoption of a system for Standardized Access. Work Stream One Priorities · Answer the gating question in Rec #3 - "Whether such a system should be adopted" · Identify the various legitimate purposes for third parties to access registration data · Move on to answering the charter questions on Access (a), (b) and (c) in the order listed. (We note that several of these questions have been answered in Phase 1 and also by the TSG work.) Work Stream Two Priorities · Issues related to Legal vs Natural distinction as identified in Rec #17 · Potential additional purposes to facilitate ICANN's Office of the Chief Technology Officer as identified in Rec #2 · Retention period issues and data collection as identified in Rec #15 · The rest. We note that several issues in this work stream are dependent on legal advice (see below). Dependencies Any large project with parallel work streams is subject to dependencies, however we believe it is important that the EPDP team avoid serializing its work and steer clear of (while still recognizing) potential deadlocks in the process. Specifically, we appreciate the important legal issues related to controllership, risk and liability and agree that these questions must be addressed in a way that results in a win-win situation whereby risks are diminished for contracted parties and authenticated/accredited users have reliable access to requests for non-public registration data. As above, we believe that this important discussion happen in parallel with the work outlined in the work streams. ___________ Alex Deacon Cole Valley Consulting alex(a)colevalleyconsulting.com<mailto:alex@colevalleyconsulting.com> +1.415.488.6009 On Tue, Mar 19, 2019 at 12:50 PM Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> wrote: Dear EPDP Team, As a reminder, please share any input you may have on the phase 2 mind map (see attached) by Thursday 28 March. In addition, your input is requested on the following questions: · How should the team prioritize going forward? · What next steps should be taken in relations to the dependencies identified? · What should be the next steps in relation to the legal guidance to date? · What is the target date for publication of the Initial Report that the EPDP Team is aiming to work toward? Please share any feedback you may have with the mailing list. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefens…> and visiting the GNSO Newcomer pages<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefens…>. _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.…> As of March 18, 2019, all NTIA email addresses will change to username(a)ntia.gov<mailto:username@ntia.gov>

1 0

Re: [Gnso-epdp-team] Reminder - input on mind map and questions coming out of ICANN64 meeting
by Alan Greenberg April 7, 2019

April 7, 2019

I support the path laid out by Alex. I once more register dissatisfaction that the Phase 2 roadmap does not include the issue of geographic differentiation. This was clearly deferred to Phase 2 in Toronto (see the discussion ending on page 34 of the Friday 3rd transcript) and at an extensive discussion on 19 Feb (ending on page 52 of the transcript) saying that there would be a study and further discussion in phase 2. Alan At 29/03/2019 01:39 AM, Alex Deacon wrote: Thanks Marika, Here are the IPCs thoughts on your questions and how to best proceed with the Phase 2 work. Method We believe the Phase 2 work should occur in two separate and concurrent work streams. * Work Stream 1 will focus on issues and questions related to the system for standardized access to non-public registration data, as defined in the EPDP charter and the overlapping EPDP Team Recommendation #3. * Work Stream 2 will focus on completing Phase 1 issues. We also believe that the "legal small team" should continue to meet concurrent with the two work streams described above, with the focus of drafting questions to our legal resource specific to our phase 2 work and analyzing responses received (both existing and TBD). Additional thoughts * Each work stream should set and work forward on its own schedule and work plan. In fact we suggest that a separate report should be generated for each work stream. * Each work stream should schedule its own separate weekly 90min meeting. Access to these meetings is open to all EPDP members (and alternates per the charter). * In a lesson learned from phase 1, consensus calls should happen early and often. Prioritization Legal Small Group Priorities * We suggest the first priority for this team is to answer the controllership and legal basis question for a system for Standardized for Standardized Access to Non-Public Registration Data, assuming a technical framework consistent with the TSG, and in a way that sufficiently addresses issues related to liability and risk mitigation with the goal of decreasing liability risks to Contracted Parties through the adoption of a system for Standardized Access. Work Stream One Priorities * Answer the gating question in Rec #3 - "Whether such a system should be adopted" * Identify the various legitimate purposes for third parties to access registration data * Move on to answering the charter questions on Access (a), (b) and (c) in the order listed. (We note that several of these questions have been answered in Phase 1 and also by the TSG work.) Work Stream Two Priorities * Issues related to Legal vs Natural distinction as identified in Rec #17 * Potential additional purposes to facilitate ICANN's Office of the Chief Technology Officer as identified in Rec #2 * Retention period issues and data collection as identified in Rec #15 * The rest. We note that several issues in this work stream are dependent on legal advice (see below). Dependencies Any large project with parallel work streams is subject to dependencies, however we believe it is important that the EPDP team avoid serializing its work and steer clear of (while still recognizing) potential deadlocks in the process. Specifically, we appreciate the important legal issues related to controllership, risk and liability and agree that these questions must be addressed in a way that results in a win-win situation whereby risks are diminished for contracted parties and authenticated/accredited users have reliable access to requests for non-public registration data. As above, we believe that this important discussion happen in parallel with the work outlined in the work streams. ___________ Alex Deacon Cole Valley Consulting alex(a)colevalleyconsulting.com<mailto:alex@colevalleyconsulting.com> +1.415.488.6009 On Tue, Mar 19, 2019 at 12:50 PM Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org> > wrote: Dear EPDP Team, As a reminder, please share any input you may have on the phase 2 mind map (see attached) by Thursday 28 March. In addition, your input is requested on the following questions: How should the team prioritize going forward? What next steps should be taken in relations to the dependencies identified? What should be the next steps in relation to the legal guidance to date? What is the target date for publication of the Initial Report that the EPDP Team is aiming to work toward? Please share any feedback you may have with the mailing list. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation ffor Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>. _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-team

3 2

Blog post: Next Steps for the Technical Study Group & EPDP
by Marika Konings April 6, 2019

April 6, 2019

For your information: https://www.icann.org/news/blog/next-steps-for-the-technical-study-group-ep…. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

NEW LINK--Update Observers--Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon April 5, 2019

April 5, 2019

My apologies, Please use this link for observers to join: https://docs.google.com/forms/d/e/1FAIpQLSdqyFFrSFXIpwwpUoYCTqfnekQf9-m9pAB… Thank you! Kind Regards, Andrea Glandon From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Friday, April 5, 2019 at 14:55 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Update Observers--Call for Volunteers: Registration Data Policy Implementation - pre-IRT Dear all, Observers will now be able to sign up in a read only status to the pre-IRT email list. Any community members who would like to join the email list as an observer, should complete this form: https://drive.google.com/open?id=1VBLejg2GvisYuqWjsa34_84nBYaenZMWG2TITxaxa… [drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-…> Please let me know if you have any questions. Thank you. Kind Regards, Andrea Glandon From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Friday, March 29, 2019 at 13:27 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Call for Volunteers: Registration Data Policy Implementation - pre-IRT Call for Volunteers: Registration Data Policy Implementation - Informal pre-IRT ICANN org is currently seeking volunteers to participate in an informal Pre-Implementation Review Team, or “pre-IRT.” The pre-IRT will assist the ICANN implementation project team in planning implementation work for the EPDP Team’s policy recommendations. As background, the GNSO Council approved and EPDP Team recommended that the GNSO Council and ICANN Org should informally convene the Implementation Review Team to allow for the necessary planning to take place before ICANN Board consideration of its Final Report, following which the IRT would be formally convened (See EPDP Team Recommendation 28). This pre-IRT will act as a temporary implementation review team, which will assist with the gTLD registration data policy implementation planning until the formal Implementation Review Team is officially convened. All members of the pre-IRT are expected to transition to the IRT. The work of the pre-IRT will consist of the following: * Review the proposed implementation plan as drafted by ICANN org * Assist where questions or clarifications from ICANN org arise * Advise on technical and operational details related to the implementation of EPDP recommendations For this pre-IRT, ICANN org is seeking volunteers who are current or former EPDP Team members and assisted in the Team’s Phase 1 work, and accordingly, possess a deep understanding of the EPDP Team’s policy recommendations and accompanying rationale. All volunteers responding to this call are expected to understand the role and remit of the IRT for the implementation project. The work of the pre-IRT is estimated to last until May 2019 when the IRT is expected to convene to take over the work. The pre-IRT is anticipated to have weekly teleconferences starting in early April 2019 for one hour each. Between the meetings, the pre-IRT will be working using collaborative tools. The expected time commitment for supporting the implementation is about three hours per week. How to apply To participate, please send an email to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. If you wish to join the IRT and not the Pre-IRT, please wait to respond to the Call for IRT, which will come later. Background On 17 May 2018, the ICANN Board of Directors (ICANN Board) adopted the Temporary Specification for generic top-level domain (gTLD) Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> ("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 in order to comply with the European Union's General Data Protection Regulation ("GDPR"). Following adoption of a temporary specification, the procedure for Temporary Policies as outlined in the Registrar Accreditation and Registry Agreements provides the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." Additionally, the procedure provides this Consensus Policy development process on the Temporary Specification must be carried out within a one-year period as the Temporary Specification can only remain in force for up to one year; from the effective date of 25 May 2018, i.e., the Temporary Specification will expire on 25 May 2019. On 19 July 2018, the GNSO Council initiated<https://community.icann.org/display/gnsocouncilmeetings/Motions+19+July+2018> an Expedited Policy Development Process (EPDP) and chartered [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> the EPDP on the Temporary Specification for gTLD Registration Data team. Unlike other GNSO PDP efforts, which are open for anyone to join, the GNSO Council chose to limit the membership composition of this EPDP, primarily in recognition of the need to complete the work in a relatively short timeframe and to resource the effort responsibly. GNSO Stakeholder Groups, the Governmental Advisory Committee (GAC), the Country Code Names Supporting Organization (ccNSO), the At-Large Advisory Committee (ALAC), the Root Server System Advisory Committee (RSSAC), and the Security and Stability Advisory Committee (SSAC) were each invited to appoint up to a set number of members and alternates, as outlined in the charter<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter?preview=/885…>. In addition, the ICANN Board and ICANN Org were invited to assign a limited number of liaisons to this effort. A call for volunteers to the aforementioned groups was issued in July and the EPDP Team held its first meeting on 1 August 2018<https://community.icann.org/display/EOTSFGRD/2018-08-01+EPDP+Team+call+%231>. On 4 March 2019, the GNSO Council adopted the EPDP Team’s Final Report and submitted it to the Board for their consideration. The Board is currently conducting a public comment that is scheduled to close on 17 April 2019.

1 0

Update Observers--Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon April 5, 2019

April 5, 2019

Dear all, Observers will now be able to sign up in a read only status to the pre-IRT email list. Any community members who would like to join the email list as an observer, should complete this form: https://drive.google.com/open?id=1VBLejg2GvisYuqWjsa34_84nBYaenZMWG2TITxaxa… Please let me know if you have any questions. Thank you. Kind Regards, Andrea Glandon From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Friday, March 29, 2019 at 13:27 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Call for Volunteers: Registration Data Policy Implementation - pre-IRT Call for Volunteers: Registration Data Policy Implementation - Informal pre-IRT ICANN org is currently seeking volunteers to participate in an informal Pre-Implementation Review Team, or “pre-IRT.” The pre-IRT will assist the ICANN implementation project team in planning implementation work for the EPDP Team’s policy recommendations. As background, the GNSO Council approved and EPDP Team recommended that the GNSO Council and ICANN Org should informally convene the Implementation Review Team to allow for the necessary planning to take place before ICANN Board consideration of its Final Report, following which the IRT would be formally convened (See EPDP Team Recommendation 28). This pre-IRT will act as a temporary implementation review team, which will assist with the gTLD registration data policy implementation planning until the formal Implementation Review Team is officially convened. All members of the pre-IRT are expected to transition to the IRT. The work of the pre-IRT will consist of the following: * Review the proposed implementation plan as drafted by ICANN org * Assist where questions or clarifications from ICANN org arise * Advise on technical and operational details related to the implementation of EPDP recommendations For this pre-IRT, ICANN org is seeking volunteers who are current or former EPDP Team members and assisted in the Team’s Phase 1 work, and accordingly, possess a deep understanding of the EPDP Team’s policy recommendations and accompanying rationale. All volunteers responding to this call are expected to understand the role and remit of the IRT for the implementation project. The work of the pre-IRT is estimated to last until May 2019 when the IRT is expected to convene to take over the work. The pre-IRT is anticipated to have weekly teleconferences starting in early April 2019 for one hour each. Between the meetings, the pre-IRT will be working using collaborative tools. The expected time commitment for supporting the implementation is about three hours per week. How to apply To participate, please send an email to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. If you wish to join the IRT and not the Pre-IRT, please wait to respond to the Call for IRT, which will come later. Background On 17 May 2018, the ICANN Board of Directors (ICANN Board) adopted the Temporary Specification for generic top-level domain (gTLD) Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> ("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 in order to comply with the European Union's General Data Protection Regulation ("GDPR"). Following adoption of a temporary specification, the procedure for Temporary Policies as outlined in the Registrar Accreditation and Registry Agreements provides the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." Additionally, the procedure provides this Consensus Policy development process on the Temporary Specification must be carried out within a one-year period as the Temporary Specification can only remain in force for up to one year; from the effective date of 25 May 2018, i.e., the Temporary Specification will expire on 25 May 2019. On 19 July 2018, the GNSO Council initiated<https://community.icann.org/display/gnsocouncilmeetings/Motions+19+July+2018> an Expedited Policy Development Process (EPDP) and chartered [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> the EPDP on the Temporary Specification for gTLD Registration Data team. Unlike other GNSO PDP efforts, which are open for anyone to join, the GNSO Council chose to limit the membership composition of this EPDP, primarily in recognition of the need to complete the work in a relatively short timeframe and to resource the effort responsibly. GNSO Stakeholder Groups, the Governmental Advisory Committee (GAC), the Country Code Names Supporting Organization (ccNSO), the At-Large Advisory Committee (ALAC), the Root Server System Advisory Committee (RSSAC), and the Security and Stability Advisory Committee (SSAC) were each invited to appoint up to a set number of members and alternates, as outlined in the charter<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter?preview=/885…>. In addition, the ICANN Board and ICANN Org were invited to assign a limited number of liaisons to this effort. A call for volunteers to the aforementioned groups was issued in July and the EPDP Team held its first meeting on 1 August 2018<https://community.icann.org/display/EOTSFGRD/2018-08-01+EPDP+Team+call+%231>. On 4 March 2019, the GNSO Council adopted the EPDP Team’s Final Report and submitted it to the Board for their consideration. The Board is currently conducting a public comment that is scheduled to close on 17 April 2019.

1 0

**REMINDER: UPDATED EOI DEADLINE 8 APRIL 2019** Expressions of Interest Sought for Chair of GNSO EPDP on the Temporary Specification for gTLD Registration Data – Phase 2
by Julie Bisland April 5, 2019

April 5, 2019

https://www.icann.org/news/announcement-2019-03-01-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> LOS ANGELES –1 March 2019 – The Generic Names Supporting Organization (GNSO) is looking for expressions of interest to chair Phase 2 of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. The EPDP Team recently completed its Phase 1 work and is expected to commence planning for Phase 2 at ICANN64 meeting in Kobe, Japan. During Phase 2, the EPDP Team will work on a system for standardized access to non-public registration data, topics identified in the annex to the Temporary Specification, as well as a number of carry over items from Phase 1. The GNSO Council is looking to appoint a neutral Chair to the EPDP Team. With such an important issue under consideration, significant responsibility comes with the role to ensure the success of deliberations. The EPDP Team is expected to have regular calls, although it may be necessary to hold calls more frequently if need arises. Additionally, the EPDP Team may have face-to-face meetings in order to meet the required milestones of the EPDP. The EPDP Team is expected to start developing the work plan for Phase 2 at ICANN64 in Kobe for which the GNSO Council may provide further guidance. There will be no compensation associated with the role of the EPDP Team Chair; however, travel associated with any face-to-face meetings may be supported by ICANN org. To express interest in this role, please submit an Expression of Interest to EOI-EPDPTeam-Chair(a)icann.org<mailto:EOI-EPDPTeam-Chair@icann.org> by 22 March 2019 at 14:00 UTC. Please answer the following questions: · What is your interest in this position? · What particular skills and attributes do you have that will assist you in chairing the EPDP? · What is your knowledge of the Temporary Specification for gTLD Registration Data, EPDP Team's Phase 1 work and associated challenges and requirements particularly as it relates to the EPDP? · What is your experience in and knowledge of the GNSO Policy Development Process, ICANN's consensus policies, ICANN's registry agreements and the Registrar Accreditation Agreement related to gTLD registration data? · Are you able to commit the time required and necessary work needed to chair the EPDP, noting that this to a certain extend will be dependent on the EPDP Team's work plan for phase 2 which is under development? · Conflict of Interest Statement – do you have any affiliation with or involvement in any organization or entity with any financial or non-financial interest in the subject matter of this EPDP? · Please also include: · A link to an up-to-date Statement of Interest (SOI) - https://community.icann.org/display/gnsosoi/New+SOIs · A statement confirming your commitment and ability to act neutrally. Application materials will be reviewed by the Council leadership and will not be shared publicly. Names of applicants, including the recommended candidate, will be shared with the GNSO Council for its consideration. The Council leadership is expected to provide its recommendation to the GNSO Council in time for the GNSO Council meeting on 18 April 2019. Additional questions and inquiries can be sent to EOI-EPDPTeam-Chair(a)icann.org<mailto:EOI-EPDPTeam-Chair@icann.org>. More Information · Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> · Additional information about the EPDP is located in Annex-A1 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> of the ICANN Bylaws and the EPDP Manual [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> [PDF, 345 KB]. · EPDP Charter<https://community.icann.org/x/0opHBQ> · EPDP wiki<https://community.icann.org/x/IYEpBQ> · EPDP Phase 1 Final Report [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> [PDF, 2.7 MB] About EPDP On 17 May 2018, the ICANN Board approved the Temporary Specification for gTLD Registration Data. The Board took this action to establish temporary requirements for how ICANN and its contracted parties would continue to comply with existing ICANN contractual requirements and community-developed policies related to WHOIS, while also complying with the European Union's General Data Protection Regulation (GDPR). The Temporary Specification has been adopted under the procedure for Temporary Policies outlined in the Registry Agreement (RA) and Registrar Accreditation Agreement (RAA). Following adoption of the Temporary Specification, the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." This Consensus Policy development process on the Temporary Specification would need to be carried out within a one-year period. Additionally, the scope includes discussion of a System for Standardized Access to Non-Public Registration Data. However, the discussion of a Standardized Access System will occur only after the EPDP Team has comprehensively answered a series of "gating questions" and non-objection by the GNSO Council. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. ANNEX A – CHAIR RESPONSIBILITIES AND EXPECTATIONS As outlined in the GNSO Working Group Guidelines, the purpose of a Chair is to call meetings, preside over working group (WG) deliberations, manage the process so that all participants have the opportunity to contribute, and report the results of the WG to the Chartering Organization. These tasks require a dedicated time commitment as each call has to be prepared, the agenda concretized, and relevant material has to be reviewed. The Chair shall be neutral. While the Chair may be a member of any group which also has representation on the EPDP Team, the Chair shall not act in a manner which favors such group. The Chair shall not be a member of the PDP Team for purposes of consensus calls. In addition, it is required – that interested candidates have considerable experience in Chairing working groups, and direct experience with at least one GNSO Policy Development Process throughout its lifecycle would be an advantage. Familiarity with the functioning of a Working Group is important to understand the various leadership skills that are necessary to employ during a WG's lifecycle. For example, a chair has to ensure that debates are conducted in an open and transparent matter and that all interests are equally represented within the WG's discussions. During the later stages of a WG when recommendations are drafted, a Chair will benefit from understanding the viewpoints of various members to ensure that an acceptable and effective outcome – ideally in form of consensus – can be achieved. In short, the EPDP Team Chair is expected to: 1. Attend all EPDP Team meetings to ensure continuity and familiarity with the subject matter and the on-going discussions; 2. Prepare meetings by reading all circulated materials; 3. Be familiar with the subject matter, including but not limited to GDPR and data protection laws, and actively encourage participation during the calls 4. Be active on the EPDP Team mailing list and invite EPDP Team participants to share their viewpoints; 5. Drive forward the EPDP Team and assure that discussions remain on point; 6. Work actively towards achieving policy recommendations that ideally receive full consensus; 7. Ensure that particular outreach efforts are made when community reviews are done of the EPDP Team's output; 8. Underscore the importance of achieving overall representational balance on any sub-teams that are formed; 9. Encourage and, where necessary, enforce the ICANN Standards of Behavior and resolve any conflicts in a timely manner. 10. Co-ordinate with ICANN staff and ensure that the EPDP Team is supported as effectively as possible 11. Conduct consistent timely reporting to the GNSO Council on the progress of the EPDP. Finally, as also pointed out the in GNSO Working Group Guidelines, 'appointing a co-chair(s) or vice-chair(s) may facilitate the work of the Chair by ensuring continuity in case of absence, sharing of workload, and allowing the Chair to become engaged in a particular debate.' As a result, similar tasks and skills are expected from vice chairs, although the overall workload may be reduced as a result of being able to share this with the Chair. Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

NTIA Letter re: EPDP Phase 2
by Chris Disspain April 4, 2019

April 4, 2019

FYI Cheers, CD Begin forwarded message: > > > _______________________________________________ > icann-board mailing list > icann-board(a)icann.org > https://mm.icann.org/mailman/listinfo/icann-board

1 0

EPDP Team mailing list page has incomplete list of subscribers
by Ayden Férdeline April 4, 2019

April 4, 2019

Hi all, I believe the [EPDP mailing list page](https://community.icann.org/pages/viewpage.action?pageId=88574688), which includes the names of observers, is incomplete. I note this because a recent email I sent to our list received a response directly from someone whose name is not listed on this webpage. I am unable to view the subscribers list, because unusually, [this functionality has been disabled](https://mm.icann.org/mailman/listinfo/gnso-epdp-team) in Mailman. We work in the open and our mailing list discussions should, of course, be accessible to everyone. But we should also be clear about whose inboxes are correspondence will be reaching. I'd like to request that we please update the EPDP mailing list page to include the names of all observers. Many thanks, Ayden Férdeline

5 10

Reminder: Re: Input requested on legal questions for phase 2
by Marika Konings April 2, 2019

April 2, 2019

Reminder! From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Thursday, March 21, 2019 at 11:50 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Input requested on legal questions for phase 2 Dear EPDP Team, In follow up to the action item coming out of the ICANN64 EPDP Team meetings, please find hereby the link to the google doc where you can start adding any legal questions you believe require a response in the context of the phase 2 identified topics: https://docs.google.com/document/d/11fCpx_FxuQSS89Z6H1pGsHy1qZJpSbUSiOzZeEe…. You are also encouraged to highlight any specific legal guidance that has already been provided (see https://community.icann.org/x/thFIBg) that may be of relevance to the upcoming deliberations. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 1

Re: [Gnso-epdp-team] Not doing Phase 2
by Stephanie Perrin April 2, 2019

April 2, 2019

I am sorry Kavouss, I am just tuning in after being completely absorbed with another project that was due March 31. I will dig back and respond to all the other earlier messages. kind regards, Stephanie On 2019-04-02 13:50, Kavouss Arasteh wrote: Dear All, There are till now 4 members of the team who stepped down Only one was considered as being missed Others were not taken taken being missed? It is strange '''' Kavouss On Tue, Apr 2, 2019 at 7:30 PM Stephanie Perrin <stephanie.perrin(a)mail.utoronto.ca<mailto:stephanie.perrin@mail.utoronto.ca>> wrote: We will really miss you Benedict!! are you sure you have to do this? Stephanie On 2019-04-02 13:06, Benedict Addis wrote: Dear all, after chatting with one of my directors last week, I’ve decided not to continue with Phase 2 of the ePDP. I need to focus on the Registrar of Last Resort this year, and that’s not compatible with the workload. Sorry I couldn’t see it through to the end. Thank you everyone for your hard work during this thorny process! Benedict. _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team

1 0