1. Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data
Name of Presenter
Event Name
DD Month 2018

2. Expedited Policy Development Process (EPDP) Overview

3. Generic Names Supporting Organization EPDP1
Can only be initiated in specific circumstances:
To address policy issue after policy recommendation has been adopted or implemented by ICANN Board
To provide new/additional recommendations 2
No Preliminary Issue Report or Final Issue Report required (no public comment period)
Talking points:
An EPDP may be initiated by the GNSO Council only in the following specific circumstances:
to address a narrowly defined policy issue that was identified and scoped after either the adoption of a GNSO policy recommendation by the ICANN Board or the implementation of such an adopted recommendation; or
to provide new or additional policy recommendations on a specific policy issue that had been substantially scoped previously
A GNSO EPDP is almost identical to a traditional GNSO PDP, but does not require a Preliminary Issue Report or Final Issue Report (and associated public comment periods).
Instead, the EPDP Drafting Team works together on an Initiation Request and the EPDP Team’s Charter.
The Initiation Request includes the scope of the effort, why it meets the criteria for an EPDP, proposed mechanism, method of operation (if different than GNSO WG guidelines), et. al.
The Charter looks similar to a PDP WG Charter and includes, amongst others, Team Composition, Team Leadership, Scope, Decision-making methodologies, Status reporting, Problem/Issue Escalation & Resolution Processes. 3
EPDP drafting team develops: 
Initiation request
EPDP team’s Charter

4. What is the mission and proposed scope?
To confirm, or not, the Temp Spec as Consensus Policy by
25 May 2019
Triggered by ICANN Board’s adoption of Temp Spec
Discuss a standardized access model to nonpublic registration data
Only after the “gating questions” specified in the EPDP Team’s Charter are addressed
Talking points:
The adoption of the Temporary Specification triggered an obligation on the GNSO Council to undertake a policy development process to confirm, or not, the Temporary Specification as Consensus Policy within 12 months of the Board’s adoption of the Temporary Specification.
Given the time constraints, the GNSO Council agreed that the Expedited Policy Development Process (EPDP) provides the best opportunity to meet this timeline.
The proposed scope of the EPDP Team’s efforts includes confirming, or not, the Temporary Specification as Consensus Policy by 25 May 2019 (the date the Temporary Specification will expire).
The proposed scope also 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 are specified in the EPDP Team’s Charter. 
Topics not included in the Temporary Specification are out of scope for this EPDP.
Only covers topics in the Temp Spec

5. EPDP Timeline
ICANN62
F2F-LA
ICANN63
ICANN64 1 2 3 4 5 6 7 8 9
May
2018
June
July
Aug
Sep
Oct
Nov
Dec
Jan
2019
Feb
Mar
Apr 1
Prep work, incl. EPDP Initiation Request & Charter adoption 2
Formation of EPDP Team 3
EPDP Team Deliberation & Publication of Initial Report(1) 4 5
Public Comment on Initial Report 6
Review of Public Comment & Submission of Final Report
Input from SO/ACs & SG/Cs 7
Council consideration of Final Report 8
Public Comment prior to Board consideration(2) 9
Board consideration
Access Model deliberations will begin after gating questions have been completed & will be added to the timeline then.
Exploring option for alternative method for community input while satisfying Bylaws requirement, await response.

6. Participation in EPDP

7. 2 members + 1 alternate per constituency
EPDP Team Composition
Chair
GNSO
RySG
RrSG
CSG
NCSG
3 Members
3 Members
6 Members
6 Members
1 Chair
3 Alternates
3 Alternates
3 Alternates
3 Alternates
2 members + 1 alternate per constituency
ALAC
SSAC
GAC
Liaisons
Talking points:
1 Independent Chair (neutral, not counted as part of EPDP Team membership/participants
GNSO Members are appointed by GNSO Stakeholder Groups (SG).
Each Contracted Party House Stakeholder Group (Registries SG and Registrars SG) was invited to appoint up to 3 Members + 3 Alternates,
Each Non-Contracted Party House SG, namely the Commercial Stakeholder Group and the Non-Commercial Stakeholder Group, was invited to appoint 6 Members + 3 Alternates (for the Commercial Stakeholder Group this is further broken down to 2 Members + 1 Alternate per Constituency).
The ALAC, SSAC, RSSAC and ccNSO were invited to appoint 2 members + 2 Alternates
Both the RSSAC and CCNSO chose not to provide members to the EPDP and will only provide input to the process as they see fit.
The GAC was invited to appoint 3 members + 3 Alternates
2 ICANN Staff Liaisons (one from Legal, one from GDD)
2 ICANN Board Liaisons
1 GNSO Council Liaison
2 Members
2 Members
2 Members
2 ICANN Staff Liaisons
(Legal & GDD)
1 GNSO
Council Liaison
2 Alternates
2 Alternates
2 Alternates
2 ICANN Board Liaisons

8. EPDP Members & Alternates
Can only represent the formal position of their SG/C or SO/AC
Alternates
Only participate if member is not available
Must keep up with all relevant EPDP WG deliberations
Talking points:
For the purpose of assessing level of consensus, Members are required to represent the formal position of their SG/C or SO/AC, not individual views or positions.
Alternates will only participate if a Member is not available. Alternates will be responsible for keeping up with all relevant EPDP WG deliberations to ensure they remain informed and can contribute when needed.
Unlike other GNSO PDP efforts, which are open for anyone to join, the GNSO Council has decided 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.
Membership limited due to tight timeframe

9. EPDP Observers Individuals can participate as observers Observers can:
Subscribe to the mailing list
listen to audio-cast of all meetings
be a public consultation respondent
Learn about the EPDP and its work:
Talking points:
Individuals may still participate as observers, even if they are not official members of the EPDP.
Observers may subscribe to the mailing list, and follow along on the audio-cast of all meetings (if so desired).
If you would like to observe the EPDP, you can do so as a mailing list observer, or a public consultation respondent.
Get involved: