1	New TLD Strategy Implementation ICANN meeting Luxemburg July 2005
2	Background Adding new TLDs to the root system - part of the core mission of ICANN ICANN Board resolution in Tunis 2003 Strategy published in September 2004 Commitment to follow a predictable, transparent and objective method Reports received from OECD, WIPO Experience gathered from sTLD introductions
3	Implementation In line with adopted strategy, we need to: Identify the complete set of issues necessary to resolve for the practical implementation Plan and conduct consultations on the issues within the ICANN community and with external bodies Compile responses, existing and new
4	Current phase In order to identify issues and plan consultations a staff paper “New TLD Questions” was drafted. Sent to SOs and ACs and posted on the web for comments regarding: Completeness of the set of questions Views on the matrix for consultations It is a draft – NOT foreclosing anything! The questions do NOT imply any preferences! The matrix does NOT imply exclusivity! Comments are due by 1 August!
5	Structure Questions grouped in five issue areas Frequency and number of new TLDs to issue Naming conventions to follow Allocation methods to use Conditions to apply IDN aspects to observe Matrix mapping individual questions to ICANN bodies and other organisations Input welcome from all on any question Input from certain bodies identified as essential for each question
6	1. How many new TLDs should ICANN designate, and with what frequency? a. What are the benefits and costs associated with delegating and operating new TLDs? b. With what frequency should new TLDs be introduced? i. Should applications be accepted at any time and measured against published criteria? ii. Should strings to be allocated per round at either a fixed or indeterminate rate? iii. What feedback mechanisms and criteria should be used to adjust the frequencies? c. What are the technical limits on the number of TLD strings that can safely be included in the root zone file? d. What are the practical, logistical and resource limits to the frequency of adding new TLDs?
7	2. Which naming conventions should apply? Which strings should be reserved or not designated? What method and who should be employed to evaluate the appropriateness of particular strings that may be reserved? c. What level of protection should be given to trademarks and other asserted rights in strings ? d. What methods should be used to protect trademarks or other rights? How should conflicts between parties with competing legitimate rights in a name be resolved? e. Who and what form of organization should vet which strings to designate?
8	3. Which allocation method or methods should be used? a. In what manners do various allocation methods support the technical, market and geo-political issues described in the previous questions? b. Determine rules or restrictions that must be applied to any allocation model in order to support the technical, market and geo-political issues described in the questions above? c. Determine appropriate uses for one-time, positive revenue derived from allocation process?
9	4. What conditions should apply for new TLD operators? a. In what cases should market forces versus imposed conditions affect registry behaviour and actions (e.g., pricing, data escrow, bonding. reserved second level names)? b. To what extent should ICANN take steps to ensure the success or sustainability of registry operations? (Are minimum financial and technical eligibility requirements appropriate and effective tools for reducing the likelihood of registry failure?) c. Should ICANN implement a program to accredit registry operators (i.e., registry back-end service providers)? d. What differentiation or classes should be made (compare today’s unrestricted, restricted, and sponsored TLDs)? How should differentiations be enforced? Can TLDs or SLDs be sublicensed? Can and should STLD use be governed by agreement? e. To what extent should new TLDs be required take steps to ensure continuity of operations in the event of a business failure or disruption to the registry sponsor or operator? What failover mechanisms must be in place to protect registrants?
10	5. How will the deployment of Internationalized Domain Names (IDNs) at the top level impact discussion and findings on the previous questions? a. What are the benefits and costs associated with delegating IDN strings as TLDs? b. What are there technical issues preventing or limiting the use of IDN TLDs? c. What naming conventions should apply to the delegation of IDN TLDs (consider objectionable strings, trademarks, TLD spoofing)? When should proposed strings be referred for advice or vetting? d. What are the rights of existing TLDs regarding IDN analogues, homophones and other equivalents?
11	Proposed Procedure 1. When, in accordance with step 1 in the Global Policy Development Process of the ASO MoU (Attachment A, article 1), ICANN staff liaising with the addressing community becomes aware of a global policy development within the scope of the ASO MoU, ICANN staff informs the ICANN Board of this development. The Board decides, as and when appropriate, that this development should be followed by ICANN staff and instructs the ICANN CEO to assign staff for this purpose. ICANN staff so assigned shall inform all ICANN Supporting Organizations and Advisory Committees, shall establish an ICANN web page to be kept up to date and shall compile a background report to be kept up to date on this global policy development. This background report shall be provided to the Board as requested. 2. Within one business day from the receipt of a proposed global policy forwarded by the ASO Address Council to the ICANN Board, the ICANN Board Secretary shall acknowledge receipt of this to the ASO Address Council and submit the proposed global policy to the Board together with an updated background report. This is the start of the 60-days window for Board response to the ASO Address Council.
12	Proposed Procedure 1. When, in accordance with step 1 in the Global Policy Development Process of the ASO MoU (Attachment A, article 1), ICANN staff liaising with the addressing community becomes aware of a global policy development within the scope of the ASO MoU, ICANN staff informs the ICANN Board of this development. The Board decides, as and when appropriate, that this development should be followed by ICANN staff and instructs the ICANN CEO to assign staff for this purpose. ICANN staff so assigned shall inform all ICANN Supporting Organizations and Advisory Committees, shall establish an ICANN web page to be kept up to date and shall compile a background report to be kept up to date on this global policy development. This background report shall be provided to the Board as requested. 2. Within one business day from the receipt of a proposed global policy forwarded by the ASO Address Council to the ICANN Board, the ICANN Board Secretary shall acknowledge receipt of this to the ASO Address Council and submit the proposed global policy to the Board together with an updated background report. This is the start of the 60-days window for Board response to the ASO Address Council.
13	Proposed Procedure 1. When, in accordance with step 1 in the Global Policy Development Process of the ASO MoU (Attachment A, article 1), ICANN staff liaising with the addressing community becomes aware of a global policy development within the scope of the ASO MoU, ICANN staff informs the ICANN Board of this development. The Board decides, as and when appropriate, that this development should be followed by ICANN staff and instructs the ICANN CEO to assign staff for this purpose. ICANN staff so assigned shall inform all ICANN Supporting Organizations and Advisory Committees, shall establish an ICANN web page to be kept up to date and shall compile a background report to be kept up to date on this global policy development. This background report shall be provided to the Board as requested. 2. Within one business day from the receipt of a proposed global policy forwarded by the ASO Address Council to the ICANN Board, the ICANN Board Secretary shall acknowledge receipt of this to the ASO Address Council and submit the proposed global policy to the Board together with an updated background report. This is the start of the 60-days window for Board response to the ASO Address Council.
14	Finally.. Comments due by 1 August The results of this consultation will be presented to the Board at their 16 August meeting for confirmation of the process moving forward Thanks for your attention!