22 Describe proposed measures for protection of geographic names at the second and other levels in the applied-for gTLD
|gTLD||Full Legal Name||E-mail suffix||Detail|
|.radio||European Broadcasting Union (EBU)||ebu.ch||View|
Q22- Protection of Geo names
1. Reserved List of Geographic Names
In accordance with Specification 5 of the proposed TLD Registry Agreement published as Attachment to Module 5 of the Applicant Guidebook by ICANN, and with Governmental Advisory Committee (GAC) advice on geographic names at the second level, the .radio Registry will put the following names on the reserved list, therefore making them unavailable for registration or any other use:
• the short form (in English) of all country and territory names contained on the ISO 3166-1 list, as updated from time to time, including the European Union, which is exceptionally reserved on the ISO 3166-1 list, and its scope extended in August 1999 to any application needing to represent the name European Union;
• the United Nations Group of Experts on Geographical Names, Technical Reference Manual for the Standardization of Geographical Names, Part III Names of Countries of the World; and
• the list of United Nations member states in 6 official United Nations languages prepared by the Working Group on Country Names of the United Nations Conference on the Standardization of Geographical Names.
Technically, this is achieved by utilising the advanced domain name rule engine that is part of the CORE Registration System and described in detail in the answer to Question 28. As laid out there, the underlying set of checks can be tuned to block registrations of .radio names based on various syntactic rules, multiple reserved names lists, and patterns. Prior to the launch of the .radio TLD, the rule engine will be configured in accordance with the reserved list mandated by Specification 5, which means that the listed names are not available for registration by registrars.
The .radio Registry intends to propose to ICANN’s Governmental Advisory Committee (GAC), and, if approved, submit to ICANN for final approval an exception to allow the .radio Registry to use some or all of those itself, in the following circumstances.
• As a conflict-resolution mechanism to accommodate multiple applications for the same string, from radios located in different countries. Example: radio-name.countryA.radio and radio-name.countryB.radio.
• Alternatively, for the Registry’s own use to provide directory-like services of radio stations and services for each individual country and territory.
Technically, this is implemented via use of the advanced domain name rule engine that is part of the CORE Registration System. As laid out in the answer to Question 28, the underlying set of validations can be adjusted to block or allow registrations of .radio names based on various syntactic rules, and patterns in particular. Once final approval has been received, the systemʹs rule engine will be configured to allow the registration of third level domains like 〈subdomain〉.〈countryA〉.radio, but prohibit the direct registration of 〈countryA〉.radio as a second level domain.
Where required for the individual release of names, the .radio Registry may also issue special authorisation codes for specific third level names to be registered by eligible registrants only. This authorisation code is then used as the domain authinfo in an EPP 〈domain:create〉 request to the .radio SRS, which will let the request bypass the rule engineʹs blocking mechanism and permit the registration.
3. Additional monitoring
The .radio Registry does not plan to monitor use of geographic names below the second level (i.e. subdomains used by a .radio domain name registrant), as those procedures are both difficult and ineffective. Available dispute resolution mechanisms are a more adequate resolution procedure in cases where third or higher level domains unduly use country or territory names.
Similar gTLD applications: (0)
|gTLD||Full Legal Name||E-mail suffix||z||Detail|