Changes

For additional details, refer to the ICANN website, Name Collision Resources & Information at [http://icann.org/namecollision icann.org/namecollision].

For additional details, refer to the ICANN website, Name Collision Resources & Information at [http://icann.org/namecollision icann.org/namecollision].

==NCAP==

==NCAP==

The ICANN Board asked the ICANN Security and Stability Advisory Committee (SSAC) to study the impact of name collisions and advise the Board on their effects and possible mitigation. In response, SSAC started the Name Collision Analysis Project with three name collision studies to address the Board's request.<ref>[https://www.icann.org/en/public-comment/proceeding/name-collision-analysis-project-ncap-study-1-13-02-2020 NCAP Study 1 Public Comment]</ref>

The ICANN Board asked the ICANN Security and Stability Advisory Committee (SSAC) to study the impact of name collisions and advise the Board on their effects and possible mitigation.<ref>[https://community.icann.org/display/NCAP/History+of+the+Name++Collision+Analysis+Project NCAP Workspace - History of the Name Collision Analysis Project], last updated March 30, 2021</ref> In response, SSAC started the Name Collision Analysis Project with three name collision studies to address the Board's request.<ref>[https://www.icann.org/en/public-comment/proceeding/name-collision-analysis-project-ncap-study-1-13-02-2020 NCAP Study 1 Public Comment]</ref>

===Study 1===

===Study 1===

Study 1 concerns name collisions in the context of TLDs in the DNS (reflected in the root zone overseen by the IANA Function) and any other namespace, whether or not it is intended for use with the DNS or any other protocol.

Study 1 concerns name collisions in the context of TLDs in the DNS (reflected in the root zone overseen by the IANA Function) and any other namespace, whether or not it is intended for use with the DNS or any other protocol.