FINAL VERSION SUBMITTED (IF RATIFIED)
The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote.
FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC
The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.
DRAFT SUBMITTED FOR DISCUSSION
The first draft submitted will be placed here before the call for comments begins. The Draft should be preceded by the name of the person submitting the draft and the date/time. If, during the discussion, the draft is revised, the older version(S) should be left in place and the new version along with a header line identifying the drafter and date/time should be placed above the older version(s), separated by a Horizontal Rule (available + Insert More Content control).
Hadia Elminiawi
22 feb. 11:46
The ALAC appreciates the opportunity to comment on the proposed procedure for selecting a Top-level Domain string for Private Use.
The selection criteria provided in the SAC113 “SSAC Advisory on Private Use TLDs” to guide the decision on which string to choose and assist the ICANN Board in making its determination, includes four criteria
- It is a valid DNS label
- It is not already delegated in the root zone
- It is not confusingly similar to another TLD in existence
- It is relatively short, memorable, and meaningful.
However, other considerations could be considered such as internationalized versions of the string and strings that are already in use for this purpose. Also, considering that it is not possible to choose a string that will accommodate the preference of all DNS users, as well as criteria three and four are subjective and cannot be easily verified through factual tests. The ALAC does not agree that the public comment proceeding for the string only asks the community to verify that IANA followed the process given, without having the opportunity to comment on the string itself.
The ALAC is of the view that allowing the public to comment on the selected string and not only the followed procedure will enable useful input that could support selection criteria three and four and consider all pros and cons associated with the string selected for private use. Therefore, assisting in people actually using the string and not continuing to use other ad-hoc strings for private use.
