Generic Top-Level Domain (gTLD) Registry Agreements
Unsponsored TLD Agreement: Appendix K | Redline
 |
Unsponsored TLD Agreement: Appendix K (24 July 2003) |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The redlining below shows changes proposed to the 26 April 2001 version of Appendix K of the .name Registry Agreement to implement the proposal of SLD .name registrations. Added text is shown with underlining and in magenta; Schedule of Reserved Names Except to the extent that ICANN otherwise expressly authorizes in writing, the Registry Operator shall reserve names formed with the following labels from initial (i.e. other than renewal) registration within the TLD: A. Labels Reserved at All Levels. The following names shall be reserved at the second level and at all other levels within the TLD at which Registry Operator makes registrations:
B. Additional Second-Level Reservations. In addition, the following names shall be reserved at the second level:
C. Tagged Domain Names. All labels with hyphens in the third and fourth character positions (e.g., "bq--1k2n4h4b") D. Second-Level Reservations for Registry Operations. The following names are reserved for use in connection with the operation of the registry for the Registry TLD. They may be used by Registry Operator under Subsection 3.6.1, but upon conclusion of Registry Operator's designation as operator of the registry for the Registry TLD they shall be transferred as specified by ICANN:
In addition, the Registry will reserve a set of names (“Common Names”) that are shared by a very substantial number of people. For a number of reasons, it is difficult to identify a specific number of names that should be reserved, or a specific percentage of the populations with names that should be reserved in any particular region or country. In some countries (such as China) reserving a very small number of names would protect a very large percentage of the population. In countries that have an extensive immigrant population or history of immigration (such as the United States), a much larger number of names is needed to cover the same portion of the population. At the same time, surnames popular in countries with very high Internet penetration are more likely to be already protected by existing third level registrations. In most cases, it will be most important to reserve names popular in developing countries. On the other hand, this will not always be the case: a name that is very popular in a small developing country may also be registered, and thus protected, as a result of a history of emigration from that country to developing nations (e.g., Vietnamese names in the U.S.). For this reason, the GNR Registry will need to make judgments, based on research and input from the ICANN community and from appropriate national and regional governments, to identify appropriate names for reservation. There are many sources of information about popular surnames. In developed nations, census data is generally available for this purpose. In other countries, this information may be available only through universities or other institutions. There is also a wealth of information available on the Internet, of various degrees of credibility that the GNR Registry will consult as appropriate. The following approaches will be used in parallel to identify appropriate names to be reserved at the second level for the operation of the registry for registrations of third level domain names and SLD Email Forwarding. While there is no perfect methodology, these approaches should produce, overall, an appropriate level of protection of popular surnames.
The GNR Registry intends to get input from the ICANN community to learn which names may be important to reserve on the 2nd level. Governments may volunteer information on common names in their respective countries. This would be particularly useful for regions where extensive knowledge about Common Names is not currently readily available. The Registry will evaluate names gathered from the Internet community, especially from government representatives participating in the Government Advisory Committee, and, after validation, may reserve common names on the 2nd level to help ensure that 3rd level registrations are available for such names. The period for receiving input will be from August 18, 2003 to September 18, 2003, and during this period the Registry would collect submissions by email for review and reservation. Only strings that are names should be submitted, for the purpose of reserving them for registration on the third level at some time in the future. There will be an expiration date on this reservation, and if no third level is registered on a given 2nd level one year from the reservation date, the reservation will expire. The Registry will publish its solicitation for input on the Registry website (http://www.nic.name), as well as ask ICANN to publish a link to the solicitation during the same timeframe.
The Registry will use names gathered from name statistics in a series of countries around the world to reserve names on the 2nd level. Names from these lists will be reserved on the 2nd level and made available only for 3rd level registrations. The Registry will use statistics gathered for last names for the following countries/regions:
D.3 Post-fix Reservations
As an example, the reservation of these post-fix strings means that all second level names ending in e.g. “–parivaar”, for example “patel-parivaar” are reserved on the second level for third level registrations only. Earlier drafts: 26 April 2001 Comments concerning the layout, construction and functionality of this site should be sent to webmaster@icann.org. Page Updated 24-Jul-2003 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||