EN
Down Arrow
User Icon
Hamburger Icon
SEARCH
X

RECHERCHER SUR LE SITE WEB DU GAC

Rechercher

Avis du GAC

Le GAC émet des avis adressés au Conseil d’administration de l’ICANN sur des dossiers de politiques susceptibles d’impliquer une interaction entre les politiques de l’ICANN et des lois, des accords internationaux ou des objectifs en matière de politiques publiques. L’avis du GAC est communiqué au Conseil d’administration de l’ICANN sous forme de Communiqué ou de correspondance officielle.

2010-03-10-IDN-1

Avis du GAC

Référence n° :

2010-03-10-IDN-1

First Delivered via :

N/A

Consensus :

Consensus atteint

2010-03-10-IDN-1

Communication

General Principles

  1. The main provisions of the GAC ccTLDs principles: 'Principles and Guidelines for the Delegation and Administration of Country Code Top Level Domains' apply also for IDN ccTLDs. The current principles are intended to supplement the aforementioned principles insofar as non-ASCII ccTLDs are concerned.
  2. The introduction and operation of IDN ccTLDs should not undermine the security and stability of the DNS. To this end, all actors, including TLD operators, ICANN and the relevant government should work together to ensure that the highest standards of TLD operation are achieved, taking account of best practices and internationally accepted technical standards where they exist.
  3. All countries and distinct economies, listed in the International Standard ISO 3166-1 have equal rights to creating IDN ccTLDs that reflect their languages and scripts.
  4. Ultimate public policy authority over the IDN ccTLD(s) of a country or distinct economy rests with the government or relevant public authority. How this authority is exercised, is determined by applicable law.
  5. On receipt of an IDN ccTLD application, ICANN should ensure that either the proposal has the support of the Government or relevant public authority or that the Government or relevant public authority raises no objections to the application. In the event that such confirmation is not obtainable, ICANN should desist from the introduction of the proposed IDN ccTLD until such confirmation is obtained.
  6. The number of IDN strings per territory should reflect the cultural and linguistic characteristics of the community concerned. A limit on the number of IDN strings per territory may only be considered if there are reasons to believe that some form of limitation on the overall size of the root zone file is necessary to preserve the stability of the DNS. If a limit is to be introduced, this should be done in agreement with the government or relevant public authority of the territory concerned, and adequate justification for such a limit should be made clear beforehand in order for territories to establish their priorities properly.
  7. It is anticipated in most cases that the Government or relevant public authority will decide that one IDN ccTLD per script will be sufficient, but it should also be borne in mind that within some countries and distinct economies different scripts are in use and, in some cases, the same script is used in a number of widely used languages. In these cases the Government or relevant public authority may determine that more than one IDN ccTLD is necessary.

Communication

General Principles

  1. The main provisions of the GAC ccTLDs principles: 'Principles and Guidelines for the Delegation and Administration of Country Code Top Level Domains' apply also for IDN ccTLDs. The current principles are intended to supplement the aforementioned principles insofar as non-ASCII ccTLDs are concerned.
  2. The introduction and operation of IDN ccTLDs should not undermine the security and stability of the DNS. To this end, all actors, including TLD operators, ICANN and the relevant government should work together to ensure that the highest standards of TLD operation are achieved, taking account of best practices and internationally accepted technical standards where they exist.
  3. All countries and distinct economies, listed in the International Standard ISO 3166-1 have equal rights to creating IDN ccTLDs that reflect their languages and scripts.
  4. Ultimate public policy authority over the IDN ccTLD(s) of a country or distinct economy rests with the government or relevant public authority. How this authority is exercised, is determined by applicable law.
  5. On receipt of an IDN ccTLD application, ICANN should ensure that either the proposal has the support of the Government or relevant public authority or that the Government or relevant public authority raises no objections to the application. In the event that such confirmation is not obtainable, ICANN should desist from the introduction of the proposed IDN ccTLD until such confirmation is obtained.
  6. The number of IDN strings per territory should reflect the cultural and linguistic characteristics of the community concerned. A limit on the number of IDN strings per territory may only be considered if there are reasons to believe that some form of limitation on the overall size of the root zone file is necessary to preserve the stability of the DNS. If a limit is to be introduced, this should be done in agreement with the government or relevant public authority of the territory concerned, and adequate justification for such a limit should be made clear beforehand in order for territories to establish their priorities properly.
  7. It is anticipated in most cases that the Government or relevant public authority will decide that one IDN ccTLD per script will be sufficient, but it should also be borne in mind that within some countries and distinct economies different scripts are in use and, in some cases, the same script is used in a number of widely used languages. In these cases the Government or relevant public authority may determine that more than one IDN ccTLD is necessary.