- Gnso-epdp-team - lists.icann.org

**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

Not doing Phase 2
by Benedict Addis April 2, 2019

April 2, 2019

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.

2 1

REMINDER-Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon April 2, 2019

April 2, 2019

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

Re: [Gnso-epdp-team] [Ext] Re: Bridging Mechanism Proposal
by Trang Nguyen March 30, 2019

March 30, 2019

Hi James, Thank you for your response. Typically, advisories explain ICANN org’s interpretation of obligations under ICANN Consensus Policies and/or contracts rather than create new obligations. Therefore, ICANN org believes that we must create a new Policy document to implement the EPDP Team’s recommendation 28 regarding the transition period. Regards, Dan and Trang ICANN Org Liaisons From: "James M. Bladel" <jbladel(a)godaddy.com> Date: Thursday, March 28, 2019 at 4:54 PM To: Trang Nguyen <trang.nguyen(a)icann.org>, Rafik Dammak <rafik.dammak(a)gmail.com>, Alan Woods <alan(a)donuts.email> Cc: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Ext] Re: [Gnso-epdp-team] Bridging Mechanism Proposal Thank you, Trang. With regard to your last paragraph, what other documents would ICANN consider ‘enforceable’? Could it issue an Advisory in conjunction with the new Consensus Policy? Just trying to keep things lightweight here. Thanks- J. ------------- James Bladel GoDaddy ________________________________ From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Trang Nguyen <trang.nguyen(a)icann.org> Sent: Thursday, March 28, 2019 18:11 To: Rafik Dammak; Alan Woods Cc: gnso-epdp-team(a)icann.org Subject: Re: [Gnso-epdp-team] Bridging Mechanism Proposal Dear Colleagues, Thanks for the clarification. Based on the clarification, ICANN org understands that the EPDP Team’s Recommendation 28 has three stages: Stage 1: As of 20 May 2019, contracted parties must continue to implement measures consistent with the Temp Spec until the development of the Consensus Policy based on recommendations by the EPDP Team is completed. Stage 2: Once the Consensus Policy document is completed, contracted parties must either continue to implement the Temp Spec or the new Consensus Policy. Stage 3: As of the Consensus Policy’s effective date (which the EPDP Team recommended to be 29 February 2020), contracted parties must comply with the new Consensus Policy. Based on this understanding, ICANN org foresees the implementation of Recommendation 28 taking the form of a Policy document that would reflect the above requirements. This form of implementation would allow for an enforceable mechanism to be in place until the new Consensus Policy goes into effect. Regards, Dan and Trang ICANN Org Liaisons From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Rafik Dammak <rafik.dammak(a)gmail.com> Date: Monday, March 18, 2019 at 5:51 PM To: Alan Woods <alan(a)donuts.email> Cc: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: Re: [Gnso-epdp-team] Bridging Mechanism Proposal Hi, The deadline we agreed on during our meeting (end of the week) already passed and there was no objection. Best, Rafik Le mer. 13 mars 2019 à 11:46, Alan Woods <alan(a)donuts.email> a écrit : Thanks Alan, taking into account your note, here is another suggested update.... maybe we can get this sorted by day's end (hope springs eternal). [Note: the removal of "Compliance" is to allow ICANN to figure out from whom they would like such an advisory to emanate from.] Suggested update: The effective date of the gTLD Registration Data Policy shall be [February 29, 2020]. All gTLD Registry Operators and ICANN-accredited registrars will be required to comply with the gTLD Registration Data Policy as of that date. Until such date [February 29, 2020], ICANN [Compliance] directs Contracted Parties that registries and registrars are required EITHER to comply with the[policy resulting from] the recommendations contained in the Final Report OR continue to implement measures consistent with the Temporary Specification (as adopted by the ICANN Board on 17 May 2018, and expired on 25 May 2019). Registries and registrars who continue to implement measures compliant with the expired Temporary Specification will not be subject to Compliance penalty specifically related to those measures until February 29, 2020. Failure to respond within 30 days of this notice shall be considered acceptance of the terms herein will be considered acceptance. Kind regards, Alan Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Donuts Inc. . Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. Thank you. On Wed, Mar 13, 2019 at 11:21 AM Alan Greenberg <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>> wrote: I think that the intent of this is exactly right, and keeping it lightweight is important. The problematic part of the wording is that it implies that contracted parties can interpret the Recs on their own prior to ICANN publishing the new Consensus Policy (CP) (presumably 6 months prior to 29 Feb 2020). For the period from xx May 2019 until the CP is published, the Temp Spec is the rule (properly phrased). After the CP is published, the new CP may apply and must apply no later than 29 Feb. Alan At 12/03/2019 12:42 AM, Elizabeth Bacon wrote: Hello Team, In Sunday?s session, ICANN noted that they feel they need a temporary policy to bridge between the expiration of the Temporary Specification and the completion of the EPDP Consensus Policy. There was some consensus in the room that the Team had anticipated this and provided that mechanism via Recommendation 28. In addition, the idea of what a ?temporary policy? might be raised several questions and concerns. In an effort to not recreate the wheel or implement an overly heavy solution, we proposed to Dennis that a formal notice/advisory from ICANN Compliance to Contracted Parties to operationalize the language we previously agreed for Recommendation 28 would be sufficient and appropriate. The language is below for your review. I look forward to your thoughts before I share with Dennis. Thanks, Beth The effective date of the gTLD Registration Data Policy shall be [February 29, 2020]. All gTLD Registry Operators and ICANN-accredited registrars will be required to comply with the gTLD Registration Data Policy as of that date. Until such date [February 29, 2020], ICANN Compliance directs Contracted Parties that registries and registrars are required EITHER to comply with the recommendations contained in the Final Report OR continue to implement measures consistent with the Temporary Specification (as adopted by the ICANN Board on 17 May 2018, and expired on 25 May 2019). Registries and registrars who continue to implement measures compliant with the expired Temporary Specification will not be subject to Compliance penalty specifically related to those measures until February 29, 2020. Failure to respond within 30 days of this notice shall be considered acceptance of the terms herein will be considered acceptance. Elizabeth Bacon Senior Director, Policy and Privacy Public Interest Registry Direct: +1 703-956-3962 | Mobile: +1 571-352-5029| Find us on www.pir.org [pir.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.pir.org_&d=DwMFaQ&c…> | Facebook [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_pir.or…> | Twitter [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_PIRegistry&…> | Instagram [instagram.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__instagram.com_piregistr…> | Celebrating 15 years of operating the .org domain _______________________________________________ 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 _______________________________________________ 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

Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon March 29, 2019

March 29, 2019

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<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#temp…> ("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<https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…> 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 - input on mind map and questions coming out of ICANN64 meeting
by Marika Konings March 29, 2019

March 29, 2019

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://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…>.

6 5