Common Principles of City TLDs

This page is designed to let people from all over the world develop a good practice for city TLDs.

Contents 1 Common Objectives 2 Defining city-TLD boundaries 3 Which parties should be able to register? 4 UDRP procedures 5 Reasonable pre-allocation of domain names 6 What Next?

[edit] Common Objectives

The following are some baseline objectives that cities should strive to achieve.

• Serve the city's Internet community in the administration of its city-TLD.

• Develop and establish a policy framework for the development and administration of Internet domain names under the city-TLD.

• Develop a structure for the administration of Internet domain name.

• Administer a registration system.

• Provide services for registration of all levels of Internet domain names under the city-TLD.

• Establish a regulatory framework in respect of such registration system.

• Encourage a better understanding and use of the Internet and related technology.

• Promote the city's e-commerce needs.

• Administer and manage the allocation and assignment of Internet Protocol addresses within the cityTLD.

• Liaise with local and international bodies on issues relating to the development and administration of domain name systems and Internet Protocol addresses.

• Establish complaint handling and dispute resolution processes to redress grievances for names registered under the city's TLD.

[edit] Defining city-TLD boundaries

The scope of registrants under each city-TLD will vary depending upon the city's history and goals for its TLD. The following presents options being considered.

.BERLIN - .berlin reflects a multifaceted community and is based on the community of Berliners and recognizes their interests worldwide. The basis of Berlin's community are people and other entities which identify themselves with the name Berlin. The complex structure of the Berlin community includes:

• inhabitants of locations with the name Berlin worldwide,
• people which are born in locations with the name Berlin,
• people which work, live nearby, or feel themselves associated to a locations with the name Berlin,
• people with private, social, cultural, or other relations to locations with the name Berlin, e.g. relatives,
• organisations with cultural, economic, or other relations to a locations with the name Berlin,
• people with the name or surname Berlin.

.NYC - When King Charles II selected the Hudson River as the boundary between his New York and New Jersey provinces, he did not foresee today’s port and market realities, or even yesterday's. For example, not agreeing on ways to share their valuable, shared harbor and waterways, New York and New Jersey waged many disputes, with one resulting in state police exchanging shots mid-river. The Treaty of 1834 stopped the shooting, but it took another 87 years to create the Port Authority of New York & New Jersey and begin addressing the regions squandered opportunities.

Today, the Port Authority administers many common harbor and development interests – bridges, tunnels, rail, water, air, and tele ports. But strategic planners declare that if the region is to grow and maintain its role in an increasingly globalized market, it must solve the remaining problems caused by King Charles' myopia.

Some suggest a second regional consolidation is required (the first, in 1900, combined 5 county governments into today's NYC). Minimally, transportation and land use needs must be addressed, with broader advantages arising through service delivery consolidation and regional economic planning and development.

The .nyc TLD might provide the linchpin for addressing these needs, with residents and businesses operating within the region eligible for .nyc TLDs only if their geographic entity (city, town, village, etc.) joins a consolidated .nyc regional governance entity.

[edit] Which parties should be able to register?

dotBERLIN - All people and entities defined as the Berlin community should given the possibility to register a .berlin domain.

.NYC - Residents and businesses operating within the region would be eligible for .nyc TLDs if their geographic entity (city, town, village, etc.) joins the consolidated .nyc regional governance entity.

[edit] UDRP procedures

[edit] Reasonable pre-allocation of domain names

An intelligent multi-phase pre-allocation procedure is essential for the fair and equitable distribution of TLDs. It will provide the basis for an intuitive internet that will assist residents, businesses, and visitors find needed resources. And it will help avoid cyber squatting and domain grabbing.

• Sovereign Interest Domains

1. local government (e.g. council.nyc, police.nyc, ...)
2. authorities/administration (e.g. mta.nyc, ...)
3. institutions (e.g. highcourt.nyc, ...)
4. others (e.g. schools.nyc, kindergarden.nyc, ...)

• Domains for general interests of the city

1. economic (e.g. hotel.nyc, tourism.nyc, ...)
2. cultural (e.g. events.nyc, culture.nyc, ...)
3. linguistic (e.g. culture.nyc, cultura.nyc, ...)
4. places (e.g. statueofliberty.nyc, ...)

• Domains in the interest of the city community

1. profession terms (e.g. lawyer.nyc, physicians.nyc, cab.nyc, ...)
2. general interest terms(e.g. weather.nyc, traffic.nyc, ...)
3. Yellow Page terms (e.g. restaurants.nyc, ...)

• Domains for owners of intellectual property (IP)

1. trade marks and service marks
2. company names and product names
3. surnames
4. other protected names

• Domains based on WIPO 2 recommendations

1. Pharmaceutical INNs
2. Names of IGOs
3. Personal names, e.g. julia-roberts
4. Indigenous peoples names, e.g. aborigines
5. Geographical names, e.g. countries, famous place names
6. Agricultural trade names, e.g. Champagne, Cognac, Jaffa

[edit] What Next?

Visit the City TLDs home page or learn some more interesting stuff about city-TLDs at Just the FAQs. Or for a giggle, see some Silly FAQs about city-TLDs.