I have heard a rumour that the pre-IRT will not be open to Observers. Is there any truth to this? Thanks, Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, April 2, 2019 3:44 PM, Andrea Glandon <andrea.glandon@icann.org> wrote:
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@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_resources...) ("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_de...) 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=/8857...). 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.