Temporary Specification for gTLD Registration Data
The Temporary Specification for gTLD Registration Data (adopted by the ICANN Board on 17 May 2018) established temporary requirements for gTLD registry operators and registrars to comply with the European Union's General Data Protection Regulation (GDPR) without breaking existing ICANN contractual requirements and community-developed policies. The Temporary Specification provides a single, unified interim model that ensures a common framework for handling registration data and maintaining the WHOIS system while the GNSO determines whether to adopt it as a consensus policy or develop an alternative policy. ICANN's stated objective of the Temporary Specification is to comply with the GDPR, while maintaining the WHOIS system to the greatest extent possible.
Requirements for the Temporary Policy[edit | edit source]
Consensus Policy Developed Within a Year[edit | edit source]
The Temporary Specification requires the Consensus Policy process, carried out through an Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data (EPDP) (EPDP-Temp Spec), to be completed within one year of the effective date of 25 May 2018.
Renewal by ICANN Board[edit | edit source]
The ICANN Board is required to reconfirm the Temporary Specification every 90 days from their adoption and enforcement of the Temporary Specification, for a period of no more than 12 months or upon its confirmation or rejection as consensus policy.
Interim Registration Data Policy for gTLDs[edit | edit source]
On May 15, 2019, the ICANN Board adopted this Interim Consensus Policy, which requires gTLD registry operators and ICANN-accredited registrars to continue implementing measures consistent with the Temporary Specification for gTLD Registration Data on an interim basis, which expired on May 20, 2019.[1]
This policy was the outcome of one of the 29 recommendations discussed in an EPDP Final Report addressing the purposes for processing data; the collection, transfer, display, and redaction of data elements; and an implementation bridge.[2]