IDN Fast Track comments

[Andy Gardner <andy@xxxxxxxxxxxxxxx>]

>A. Script Selection:

>(i) Is it necessary to limit the number of scripts for which a  
territory can
>have an IDN ccTLD under the fast track? If so what is the limit?

One script for each non_English language designated as an official  
language of that country, by the Government of that country, prior to  
1 January 2008.
>(ii) Is it necessary for the language represented by the IDN script to
>have a particular status with the Territory? If so what is the status?

Yes. The language must be designated as an official language of that  
country, by the Government of that country.
>B. String Selection:

>(i) Apart from the overarching requirements to meet the IDNA
>protocols and any other IDN technical requirements, are there any
>criteria for a string to be acceptable under the fast track (for
>example that the string must be a meaningful representation of the
>name of the Territory or an abbreviation of the name of the Territory
>in the relevant script)?

Yes. String must be a meaningful representation of the name of the  
Territory or an abbreviation of the name of the Territory in the  
relevant script. Script muct not be confusingly similar to an existing  
TLD.
>(ii) Does a selected string need to be evaluated against the
>requirements and criteria and if so by whom?

Yes. Confirmed as such by an appropriate independent global standards  
authority.
>C. String Proposal:

>(i) Who are the actors from the Territory who need to be involved in
>making a proposal for a string under the fast track?

Sovereign government of that Territory

>(ii) How is the involvement of those actors demonstrated?

Official statement in the standard manner for that Government.

>D. Objection procedure:

>(i) Once a string has been selected in accordance with the  
requirements
>and any criteria, should objections be allowed?

No.

>(ii) If so, who can object and on what grounds?
>(iii) If an objection is lodged, what is the impact?

>4. Mechanism to designate an IDN ccTLD manager.

>The second task is to develop a mechanism for designating the  
manager for an
>IDN ccTLD, bearing in mind the limitations and guidelines canvassed  
in section 2
>above. The IDNC WG suggests the following elements are part of such a
>mechanism:

>A. Who can be the IDN ccTLD manager:

Any IDN ccTLD managerial appointment is the responsibility of the  
Government in question. Historically ICANN has stayed out of this area  
and should continue to do so.
(i) Apart from the overarching requirements to meet the IDNA protocols
and any other IDN technical requirements, are there other IDN specific
criteria that an IDN ccTLD manager needs to meet?

No.

(ii) Does the IDN ccTLD manager need to be evaluated against the
requirements and criteria and if so by whom?

No.

(iii) Does the IDN ccTLD manager need to demonstrate a track record of
managing a TLD?

No.

(iv) Does the IDN ccTLD manager need to demonstrate experience with
running IDNs in the particular script?

No.

>B. Operation of the IDN ccTLD:

>(i) Given the overarching requirement to adhere to the IDNA protocols
>and other technical requirements on an ongoing basis how can
>ongoing adherence be ensured?

Adherence to IDNA protocols by a TLD manager is no different to  
current adherence to current non-IDNA protocols by current TLD  
managers. There is nothing special here.
>(ii) Are elements of the registration policies of the IDN ccTLD  
manager
>relevant in relation to compliance with the overarching IDNA protocols
>and other technical requirements? If so how can ongoing adherence to
>the required policies be ensured?

No. The registration policies of the IDN ccTLD manager are a matter  
between the manager and the government who appointed them. If they  
want to run a completely different namespace within the IDN ccTLD  
compared to their current ASCII ccTLD, or mirror them together, is no  
business of ICANN's.