14,952
edits
Changes
Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data (view source)
Revision as of 20:42, 21 January 2021
, 3 years agono edit summary
The Expedited Policy Development Process on the [[Temporary Specification for gTLD Registration Data]] (EPDP) was initiated by the [[GNSO]] Council on 19 July 2018 to determine if the Temporary Specification for gTLD Registration Data should become ICANN consensus policy, with or without modifications, while ensuring compliance with the [[European Union]]'s [[General Data Protection Regulation]] (GDPR) and other relevant privacy and data protection laws.
The Expedited Policy Development Process on the [[Temporary Specification for gTLD Registration Data]] (EPDP) was initiated by the [[GNSO]] Council on 19 July 2018 to determine if the Temporary Specification for gTLD Registration Data should become ICANN consensus policy, with or without modifications, while ensuring compliance with the [[European Union]]'s [[General Data Protection Regulation]] (GDPR) and other relevant privacy and data protection laws.
==Context==
==Background on the EPDP==
===History===
On January 8, 2012, GNSO Policy staffers released a discussion paper<ref>[https://gnso.icann.org/sites/default/files/filefield_36239/policy-implementation-framework-08jan13-en.pdf Policy vs. Implementation Framework]</ref> about the many questions that had arisen from the implementation of the [[New gTLD Program]], especially concerning when policy vs. implementation work was needed. The GNSO Policy & Implementation [[Working Group]] was formed in July 2013.<ref>[https://gnso.icann.org/sites/default/files/filefield_47703/policy-implementation-recommendations-01jun15-en.pdf PI WG Recommendations]</ref> On June 24, 2015, the GNSO Council unanimously adopted the WG's recommendations, which included three new GNSO processes. The GNSO Guidance Process (GGP) and the GNSO Expedited Policy Development Process required changes to the [[ICANN Bylaws]]. The EPDP procedures, outlined in Annex A-1 of the ICANN Bylaws, went into effect on September 28, 2015.
===Criteria===
The GNSO Council may invoke the EPDP (1) to address a narrowly defined policy issue that has already been identified and scoped, following the adoption and/or implementation of a GNSO policy recommendation by the Board; or (2) to create new or additional recommendations for an issue on which extensive, pertinent background information already exists; for instance, the issue may have been discussed in an Issue Report for a PDP that was not initiated or completed or was part of a GGP.<ref>[https://www.icann.org/resources/pages/governance/bylaws-en/#annexA1 ICANN Bylaws Annex A1]</ref>
==Temporary Specificiation Context==
On 17 May 2018, the [[ICANN Board]] adopted the Temporary Specification as an interim model for [[WHOIS]] compliance. This temporary specification was designed to allow [[registries]] and [[registrars]] to be compliant with the GDPR without being in breach of their contract with ICANN.
On 17 May 2018, the [[ICANN Board]] adopted the Temporary Specification as an interim model for [[WHOIS]] compliance. This temporary specification was designed to allow [[registries]] and [[registrars]] to be compliant with the GDPR without being in breach of their contract with ICANN.
The procedure for Temporary Policies, requires the consensus policy development process (in this case the EPDP) to be completed within a year of the Temporary Specification effective date of 25 May 2018.
The procedure for Temporary Policies requires the consensus policy development process (in this case the EPDP) to be completed within a year of the Temporary Specification effective date of 25 May 2018.
==Mission and Scope==
==Mission and Scope==
=== EPDP Phase 1 Final Report ===
=== EPDP Phase 1 Final Report ===
The [https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld-registration-data-specs-final-20feb19-en.pdf Final Report] of the [[Temporary Specification for gTLD Registration Data]] (EPDP) was published on 20 February 2019. The representatives from the Intellectual Property Constituency ([[IPC]]) and Business Constituency ([[BC]]) voted against the Final Report, but since all other [[GNSO]] Councillors were in favour the Final Report was approved.<ref>https://www.comlaude.com/epdp-update/</ref> The report was then passed to the ICANN Board for adoption.
The [https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld-registration-data-specs-final-20feb19-en.pdf Final Report] of the [[Temporary Specification for gTLD Registration Data]] (EPDP) was published on 20 February 2019. The representatives from the Intellectual Property Constituency ([[IPC]]) and Business Constituency ([[BC]]) voted against the Final Report, but since all other [[GNSO]] Councillors were in favour, the Final Report was approved.<ref>https://www.comlaude.com/epdp-update/</ref> The report was then passed to the ICANN Board for adoption.
The report contains an analysis of affected parties, anticipated time to implement recommendations, and other pertinent information that will assist the Board's deliberations on the EPDP Phase 1 policy recommendations<ref>https://gnso.icann.org/en/announcements/announcement-2-22apr19-en.htm</ref>. The recommendations from this report must be adopted by concerned parties on or before 29 February 2020.
The report contains an analysis of affected parties, anticipated time to implement recommendations, and other pertinent information that will assist the Board's deliberations on the EPDP Phase 1 policy recommendations<ref>https://gnso.icann.org/en/announcements/announcement-2-22apr19-en.htm</ref>. The recommendations from this report must be adopted by concerned parties on or before, 29 February 2020.
=== EPDP Phase 2 Final Report ===
In Phase 2, the EPDP team discussed a standardized access model to nonpublic registration data and submitted the Phase 2 Final Report to the GNSO Council on July 31, 2020, which the GNSO council approved on September 24, 2020. The Final Report primarily sets out recommendations for a [[System for
Standardized Access/Disclosure]] (SSAD) to nonpublic gTLD registration data. The 18 SSAD-related policy recommendations address the following areas:
* Accreditation of SSAD requestors, including governmental entities
* Required criteria and content of SSAD requests
* Response requirements
* Required Service Level Agreements (SLAs)
* Automation of SSAD processing
* Terms and conditions of SSAD
* Logging, auditing, and reporting requirements
* GNSO Standing Committee to evaluate SSAD operational issues and propose improvements to the GNSO Council
The EPDP Team advised the GNSO council to treat these recommendations as one package and pass them on as such to the ICANN Board.<ref>[https://gnso.icann.org/sites/default/files/file/field-file-attach/policy-briefing-epdp-temp-spec-gtld-registration-data-phase-2-06oct20-en.pdf GNSO ICANN69 Policy Briefing]</ref>
==References==