14,932
edits
Changes
no edit summary
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.
* Other characteristics
* Other characteristics
** Open-Source Intelligence (OSINT)
** Open-Source Intelligence (OSINT)
===Public Comments===
From late January to mid-March 2022, the NCAP Discussion Group sought [[Public Comment]]s on two draft work products related to NCAP Study 2 goals of understanding how measurements of DNS hierarchy layers can convey the impact of name collisions.<ref>[https://www.icann.org/en/public-comment/proceeding/name-collision-analysis-project-ncap-study-2-documents-27-01-2022 NCAP Study 2 Public Comment Proceedings, ICANN]</ref> The group received 3 comments on the topics of:
# A Prospective Study of DNS Queries for Non-Existent Top-Level Domains to understand the distribution of DNS name collision traffic throughout the DNS hierarchy and determine where and how to collect and assess DNS data.
# Case Studies of Collision Strings (.corp, .home, .mail, .internal, .lan, and .local) based on DNS query data from A and J root servers in light of DNS evolution.<br/>
[[OCTO]] suggested specific amendments to the documents whereas the [[ISPCP]] and [[RySG]] gave high-level statements about the group’s approach. OCTO noted that the study descriptions are not related to understanding the root cause of most name collisions, and this relationship should be spelled out. OCTO also advised the group that the documents should be revised to specify quantitatively which, if any, of their findings had a significant impact on the RSS, end users, or resolvers. OCTO encouraged the group to support all conclusions with data.<ref>[https://itp.cdn.icann.org/en/files/name-collision/nacp-study-2-documents-04-04-2022-en.pdf NCAP Study 2 Drafts, Public Comments, ICANN]</ref> The ISPCP suggested the discussion group should be expanded to include representatives from other parts of the [[ICANN Community]]. RySG supported the continued use of the hypothesis that "controlled interruption is effective" based on the data.<ref>[https://itp.cdn.icann.org/en/files/name-collision/nacp-study-2-documents-04-04-2022-en.pdf NCAP Study 2 Drafts, Public Comments, ICANN]</ref>
===Outputs===
NCAP resulted in a broader definition for a name collision: when a name that is defined and used in one namespace also appears in another. Partly in reference to [[AltRoot]]s, the NCAP team warned that the "indiscriminate and uncoordinated introduction of new namespaces without a careful review from the larger community may be a cause of ongoing and unavoidable name collisions, making the Internet less stable and less secure."<ref>[https://www.icann.org/en/system/files/files/octo-034-27apr22-en.pdf OCTO-034, ICANN Files]</ref>
==References==
==References==
{{reflist}}
{{reflist}}
[[Category:Glossary]]
[[Category:Glossary]]