Public Comment is a vital part of our multistakeholder model. It provides a mechanism for stakeholders to have their opinions and recommendations formally and publicly documented. It is an opportunity for the ICANN community to effect change and improve policies and operations.
Submissions for this Proceeding
Proposed Procedure for Selecting a Top-Level Domain String for Private Use
View this Proceeding
Search Public Comment Submissions For This Proceeding
To search for keywords within Public Comment submissions documents or pages, type in the keyword and press Enter after each selection.
The BC is supportive of this procedure for the selection of a Top-Level Domain String for private use, and agrees that this is an IANA operational responsibility.
However, some elements of the selection process are vague - “deliberation with an internal evaluation team”, and issues resolution through consultation with relevant experts . These ought to be clarified in the interests of transparency.
The Registries Stakeholder Group (RySG) agrees on the importance of determining a top-level domain string for private use and provides comments on the proposed selection procedure.
The SSAC considers that this proposed procedure needs to have more detail in it, especially about how it will assess Criteria 3 and 4, if there is to be no further opportunity to comment on the process. In particular, the proposed procedure should explain how candidate strings will be tested for confusing similarity, memorability, and meaningfulness, taking into account both native and non-native speakers of the language(s) in which the string...
The IPC has 3 major concerns with the proposed procedure. The first is that trademark considerations are not factored into the process. Second, there should be a meaningful, substantive public comment period after the string is selected, not just a comment on whether process was correctly followed. And, third, the necessity of the process at all. ICANN should explain why currently reserved strings cannot be used for the purposes set forth in ...
The Network Information Center .ukgbni.com ( NIC UKGBNI) of the United Kingdom of Great Britain and Northern Ireland (UKGBNI), hereby submits its opinion to the ICANN community:
On ICANN's Community Question:
We propose regarding the "Proposed Procedure for Selecting a Top-Level Domain String for Private Use"
in order to avoid possible collisions of top-level and second-level domain...
Criterion 3 & 4 will introduce a different complexity in the process as the interpretations may vary across. Unless the process is reviewed again at a later stage where the interpretations can be agreed upon and be finalized on.
My recommendation is the creation of *two* private root labels: "home" for personal use, and "corp" for corporate use.
Those using the "corp" zone should be encouraged not to use it directly, but to create one or more zones under this as needed by business units. This is to account for mergers, acquisitions, and internal spin-offs. For instance, Microsoft might have "msft.corp" and "xbox.corp" amongst others, ICANN could have "pti.corp" ...