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.
Контент доступен только на следующих языках
If no, please explain
The Registries Stakeholder Groups (RySG) notes that the draft AGB language for the Subsequent Application Rounds section is not consistent with ALL of the relevant SubPro Final Report recommendations on this topic. Most notably, the proposed AGB text is missing any reference to Recommendation 3.5, which provides an opportunity for the GNSO Council to recommend pausing the New gTLD Program if needed. The Annex of “Relevant Outputs” for this draft section also includes implementation guidance around strings that are “still being processed” from a previous application round. The RySG recognizes that it may be more appropriate to incorporate this guidance into a different section of the AGB, but is noting it here for completeness.
If no, please explain
The draft of this section notes that publicly traded corporations may undergo more limited background screening in section 1.1.2, which is consistent with Recommendation 22.4. However, it does not provide any further detail about how the background screening for such a corporation would differ from the screening of all other applicants. The RySG suggests that this section of the AGB will be clearer for future applicants if that is clarified, to the extent feasible. Additionally, it is challenging to fully assess this draft section while section 1.2.4.1 “Addressing Issues Identified during Background Screening” is not yet finalized
If no, please explain
The RySG notes it is difficult to fully assess this draft section until the String Similarity Guidelines are published.
If no, please explain
While the RySG believes this draft section is consistent with the relevant SubPro Final Report recommendations, we note that it may need to be updated in light of recent guidance from the ICANN Board regarding the resolution of contention sets.