14,932
edits
Changes
Jump to navigation
Jump to search
Line 597:
Line 597: + + + +
Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data (view source)
Revision as of 16:40, 25 January 2023
, 1 year ago→Registration Data Consensus Policy for gTLDs
#* updates to existing policies and procedures that touch on Registration Data
#* updates to existing policies and procedures that touch on Registration Data
#* ICANN Org determined that 18 of 24 existing policies and procedures would be impacted by the Registration Data Consensus Policy, including outdated provision language, high-level issues, such as the relevance or inconsistency of an existing policy or procedure with the new Registration Data Consensus Policy, and implications for existing contractual provisions.
#* ICANN Org determined that 18 of 24 existing policies and procedures would be impacted by the Registration Data Consensus Policy, including outdated provision language, high-level issues, such as the relevance or inconsistency of an existing policy or procedure with the new Registration Data Consensus Policy, and implications for existing contractual provisions.
===Public Comments Final Report===
On January 20, 2023, ICANN Org released its final report on the 14 submissions it received. The summary identified several key themes, including:
# the need for clarification in sections 2, 3, 5, 6, 7, 9, 10, 12, and addendum I.
# areas in the drafted policy language did not accurately reflect the policy recommendations, such as "processing" in sections 1, the "scope" in section 2, the entirety of section 2.2, section 3.8-3.10, and "consent" and "personal data" as they relate to the GDPR, the timeline in section 4, updates to section 5 to reflect events that have happened in the meanwhile, the use of "must" in sections 6, 7, 8, and 9, the use of "urgent" in section 10,
==References==
==References==
[[Category:EPDPs]]
[[Category:EPDPs]]