SAC130 - SSAC Comments on Name Collision Guidelines in the Proposed Language for the Draft Next Round Applicant Guidebook
Abstract
In this document, the SSAC focuses on a specific name collision scenario: when a new gTLD
applicant applies for a string already in use in an alternative, non-DNS naming system (e.g.,
blockchain-based naming systems). Several alternative naming systems increasingly utilize the
syntax of DNS names.Without explicit guidelines and proactive management, these alternative
naming systems may create collisions with new gTLDs delegated through the New gTLD
Program: Next Round.
The SSAC believes these collisions could cause the following problems:
● Security vulnerabilities stemming from misdirected traffic or unexpected system
interactions.
● Operational instability for network operators and end-users.
● User confusion due to unpredictable resolution behavior.
The SSAC submits this comment to amplify and clarify key principles from NCAP2 that address
these (previously identified) risks, so that the final AGB fully reflects this guidance.
applicant applies for a string already in use in an alternative, non-DNS naming system (e.g.,
blockchain-based naming systems). Several alternative naming systems increasingly utilize the
syntax of DNS names.Without explicit guidelines and proactive management, these alternative
naming systems may create collisions with new gTLDs delegated through the New gTLD
Program: Next Round.
The SSAC believes these collisions could cause the following problems:
● Security vulnerabilities stemming from misdirected traffic or unexpected system
interactions.
● Operational instability for network operators and end-users.
● User confusion due to unpredictable resolution behavior.
The SSAC submits this comment to amplify and clarify key principles from NCAP2 that address
these (previously identified) risks, so that the final AGB fully reflects this guidance.
