Changes

#* 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===

===Public Comments Summary Report===

On January 20, 2023, ICANN Org released its final report on the 14 submissions it received. The summary identified several key themes, including:  

On January 20, 2023, ICANN Org released its summary 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 addendums I and II.  

# the need for clarification in sections 2, 3, 5, 6, 7, 9, 10, 12, and addendums I and II.  

# 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, sections 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," the proposed deadlines, and the lack of explanation for circumstances under which a request must be considered in section 10, issues with the specifics of logging in section 11, and the "minimum retention period" in section 12.

# 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, sections 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," the proposed deadlines, and the lack of explanation for circumstances under which a request must be considered in section 10, issues with the specifics of logging in section 11, and the "minimum retention period" in section 12.

# the need to correct some of the redlines in the Additional Whois information Policy, the ERRP, the Protection of IGO and INGO Identifiers, the CL&D Policy, the Thick Whois Transition Policy, the Transfer FOA and initial authorization, the TDRP, the Transfer Policy, UDRP-related documents, the WDRP Rules, and RDAP-related documents

# the need to correct some of the redlines in the Additional Whois information Policy, the ERRP, the Protection of IGO and INGO Identifiers, the CL&D Policy, the Thick Whois Transition Policy, the Transfer FOA and initial authorization, the TDRP, the Transfer Policy, UDRP-related documents, the WDRP Rules, and RDAP-related documents.

==References==

==References==

[[Category:EPDPs]]

[[Category:EPDPs]]