[gnso-idn-wg] GNSO new TLDs: information relating to IDNs
Colleagues I have following the discussion about IDNs closely. Yesterday Olof sent you the links to the new TLDs report but I thought it may be helpful for you to see where IDN's fit within the more general discussion about new top-level domains. I released the updated version of the Report last week and many of you may not have had the time to read it in full. Could I suggest that you print this mail out and read through the draft recommendations? You will see that some questions which are being posed on the list now may well have been answered. There are more consultations sessions taking place at the Lisbon meeting -- you can raise any issues you may have with the Recommendations at the Committee Working Sessions and at the new gTLDs Public Forum. Of course, I am more than happy to answer detailed questions about any or all aspects of these principles and recommendations which would apply to all new TLDs -- whether ASC-II or IDN. Kind regards. Liz ..... Principle 1 -- New generic top-level domains (gTLDs) must be introduced in an orderly, timely and predictable way. Principle 2 -- Some new generic top-level domains may be internationalised domain names (IDNs) subject to the approval of IDNs being available in the root. Principle 3 -- The reasons for introducing new top-level domains include that there is demand from potential applicants for new top- level domains in both ASCII and IDN formats and that the new TLD process promotes competition, consumer choice and geographical and service-provider diversity. Principle 4 -- A set of technical criteria must be used for assessing a new gTLD registry applicant to minimise the risk of harming the operational stability, security and global interoperability of the Internet. Principle 5 -- A set of capability criteria for a new gTLD registry applicant must be used to provide an assurance that an applicant has the capability to meets its obligations under the terms of ICANN’s registry agreement. Principle 6 A set of operational criteria must be set out in contractual conditions in the registry agreement to ensure compliance with ICANN policies. Recommendation 1 -- ICANN must implement a process that allows the introduction of new top-level domains. Recommendation 2 -- Strings must not be confusingly similar to an existing top-level domain. Recommendation 3 -- Strings must not infringe the existing legal rights of others that are recognized or enforceable under generally accepted and internationally recognized principles of law. Recommendation 4 -- Strings must not cause any technical instability. Recommendation 5 -- Strings must not be a Reserved Word. Recommendation 6 -- Strings must not be contrary to generally accepted legal norms relating to morality and public order. Recommendation 7 -- Applicants must be able to demonstrate their technical capability to run a registry operation. Recommendation 8 -- Applicants must be able to demonstrate their financial and organisational operational capability. Recommendation 9 -- There must be a clear and pre-published application process using objective and measurable criteria. Recommendation 10 -- There must be a base contract provided to applicants at the beginning of the application process. Recommendation 11 -- Staff Evaluators will be used to make preliminary determinations about applications as part of a process which includes the use of expert panels to make decisions. Recommendation 12 -- Dispute resolution and challenge processes must be established prior to the start of the process. Recommendation 13 -- Applications must initially be assessed in rounds until the scale of demand is clear and there is a reduction to zero of applications for the same string. Recommendation 14 A -- If there is contention for strings, applicants may: i) resolve contention between them within a pre-established timeframe ii) if there is no mutual agreement, a process will be put in place to enable efficient resolution of contention and; iii)the ICANN Board may be used to make a final decision, using advice from staff and expert panels. Recommendation 14B -- Where an applicant lays any claim that the TLD is intended to support a particular community such as a sponsored TLD, or any other TLD intended for a specified community, that claim will be taken on trust with the following exception: i) the claim relates to a string that is also subject to another application and the claim to support a community is being used to gain priority for the application Under this exception, Staff Evaluators will devise criteria and procedures to investigate the claim. Recommendation 14C -- An application will be rejected or otherwise deferred if it is determined, based on public comments or otherwise, that there is substantial opposition to it from among significant established institutions of the economic sector, or cultural or language community, to which it is targeted or which it is intended to support. Staff Evaluators will develop criteria and procedures for making this determination. Recommendation 15 -- The initial registry agreement term must be of a commercially reasonable length. Recommendation 16 --There must be renewal expectancy. Recommendation 17 -- Registries must apply existing Consensus Policies and adopt new Consensus Polices as they are approved. Recommendation 18 -- A clear compliance and sanctions process must be set out in the base contract which could lead to contract termination. Recommendation 19 -- If an applicant offers an IDN service, then ICANN’s IDN guidelines must be followed. Recommendation 20 -- Registries must use ICANN accredited registrars. ..................................................... Liz Williams Senior Policy Counselor ICANN - Brussels +32 2 234 7874 tel +32 2 234 7848 fax +32 497 07 4243 mob |