.city Pre-Register Domain - .city Domain Information

"The city as a center where, any day in any year, there may be a fresh encounter with a new talent, a keen mind or a gifted specialist -- this is essential to the life of a country. To play this role in our lives a city must have a soul -- a university, a great art or music school, a cathedral or a great mosque or temple, a great laboratory or scientific center, as well as the libraries and museums and galleries that bring past and present together. A city must be a place where groups of women and men are seeking and developing the highest things they know."
-Margaret Mead-

We expect great things from our great cities. Bustling metropolis with fabulous places to dine, museums to visit history, architectural wonders, places of commerce, musical venues, theater, gathering places and great parks, are just some of our expectations. Or equally important, small cities with an affinity of specialized purpose, like those known for their specialized goods or services, or quality of living, or artists and academics. Deeper and more meaningful though are the identities we attach to these cities and that extend onto ourselves and our endeavours. It is common for a person to express their city as an extension of expected behavior or characteristic. Just by saying one is from London, Moscow, Paris, Mumbai, New York, Tokyo, we begin to imagine those cities and for what they are known best.

Capturing this sense of place and associated identity allows us to associate many things with the city.. In the Internet, in particular, a Top Level Domain with a themed approach carries a sense of purpose even as a generic, open TLD through its semantic meaning. Providing a TLD for every single city is a technical possibility, but perhaps not economically viable or pragmatic. We seek to allow the bold and innovative to step forward and use city themed registrations in viable and creative ways.

The mission/purpose of .city is to facilitate web services creating a virtual world around a defined name space that represents a real world - your city. The .city extension is intended to provide the registrant an immediately recognized domain name that tells end-users that the registrant's products, services or information, can be found in or associated with a particular city. The .city extension is a generic, global top-level domain that will be offered without restrictions. It is a TLD string with empirical meaning that we believe potential registrants will understand and see the opportunities for geographic identification through their registrations. Each registrant will be responsible for developing their unique value proposition based upon their products, services or information in the market defined by their .city registration.

We chose 153 diverse cities from around the world and found that there exist as many as 2.5 million domain names, that carry one of these city names as an integral part of the domain name. This corresponds to a substantial 1.93% of all gtld domain names, and demonstrates the popularity and need for registrants to associate their web presence to a city name.

The demand largely comes from various small localized shops and service providers that specialize in serving a specific city. A .city domain name will better classify their scope as ʹwithin the boundires of a specific cityʹ. (eg: ʹQuick Cabsʹ in London could buy ʹquickcabslondon.cityʹ; ʹJB Mallʹ in Dubai could get jbmalldubai.city).

The mission/purpose for .city is as follows -

1.1 ENHANCE SEARCHABILITY AND RECOGNITION

To create a namespace that enables local business operators to easily distinguish themselves from countless others. It enables them to call out that they belong to a city, and are a part of its eco-system. This benefits the Registrants as well as the end users. When an end user is in the need of localized support; he will be able to quickly spot local operators from others.

1.2 CREATE A CLEANER INTERNET SPACE

To create a cleaner internet experience for end users by implementing pioneering registration policies, content and usage policies, and abuse mitigation processes.

1.3 CREATE A STABLE AND RESILIENT INTERNET SPACE

To deliver a stable and resilient internet experience to registrants and end-users by going above and beyond the ICANN mandated SLAs and delivering 100% resolution uptime

This completes our response to Q18(a).

1. GOAL OF .CITY

1.1 SPECIALTY

* Our goal for .city in terms of area of specialty is to provide registrants an immediate and direct linkage to the city of their choice. It enables business operators to call-out the city where they belong and know like no other.

1.2 SERVICE LEVELS

Our goal for .CITY in terms of service levels is to go above and beyond the ICANN SLAs. ICANN provides for its expected SLA in Specification 10 in the Registry Agreement in the Applicant guidebook.

We have engaged ARI Registry Services (ARI) to deliver services for this TLD. ARI provides registry services for a number of TLDs including the .au ccTLD

Our contract with ARI is attached to our response to Q46. This contract details the SLA we intend on achieving with this TLD. As can be seen in the contract we have exceeded the ICANN required SLA on every parameter.

Our response to Q34 and Q35 provides details on ARI's distributed anycast DNS network. ARI's DNS network provides for 16 geo distributed sites resulting in a very low resolution latency for end-users, amongst the lowest in the industry.

It is our objective to provide 100% uptime, a resilient global DNS infrastructure, and very low latency in terms of DNS resolution for this TLD

1.3 REPUTATION

Reputation of our TLD is of paramount importance to us. The reputation of our TLD directly relates to how end-users on the internet perceive our Registrants. We will ensure the highest reputation of .CITY by ensuring the following -
* Maintaining a high quality bar with respect to Registrants in the TLD
* Well defined Acceptable usage and content policies
* Well defined dispute resolution mechanisms
* Ensuring Whois accuracy to support abuse mitigation
* Well defined and implemented abuse mitigation processes
* Well defined and implemented rights protection mechanisms
* Exceptional service levels

To this effect we have created unprecedented Abuse mitigation policies and Rights protection mechanisms that go significantly above and beyond mandatory requirements and common practice described in considerable detail in our response to Q28 and Q29. We also commit to extremely high service levels that go beyond the stipulated service levels in the applicant guidebook.

2. CONTRIBUTION OF .CITY TO THE NAMESPACE

2.1 CONTRIBUTION IN TERMS OF COMPETITION, DIFFERENTIATION, OR INNOVATION

Per ICANN's Bylaws as amended June 24, 2011, ICANN's core value number six is "Introducing and promoting competition in the registration of domain names where practicable and beneficial in the public interest."

* The .city registry's differentiation will be the association with a strong existing identity and an inferred relationship to a particular locality. We will provide registrants a domain space that intrinsically implies the relationship to city of their choosing.

* .CITY will also allow Registrants worldwide to differentiate themselves from the 200+ million domain names out there. As of now a domain name built around a city appears identical to any other domain name in a .gTLD (com) or .ccTLD extension (eg .in). .CITY provides the ability for Registrants to create a differentiated identity wherein just by looking at the URL end-users will be able to recognize and identify the kind of entity associated with the domain name.

* The .city registry's innovation will focus on two areas, the themed meaning of our string, and our enhanced abuse management programs.

* Despite the prevalence of English as a language of commerce, past gTLD registries have largely focused on North America and European marketplaces. Directi will be offering the .city to international markets, with the goal of a truly global distribution of registrants.
Our intent is to operate .city with a focus on integrity and quality for the .city brand. This entails running a robust abuse program from initiation, which in our case not only meets ICANN's requirements, but extends beyond such as offering optional contact paths for agencies working to enforce laws. We will be bringing the Directi Group's mature established abuse team and disciplined management to .city AND we will have strong provisions to act where registrars are remiss in their responsibilities. We believe .city will have the potential to set new standards for the reduction and control of domain abuse.

Lastly .City will provide registrants the option to register more desirable and shorter names as opposed to names they would have otherwise registered in existing gTLDs due to the high saturation of the existing namespaces.

Our intent is to operate .City with a focus on integrity and quality for the .City brand. This entails running robust abuse mitigation programs and pioneering Rights Protection Mechanisms from initiation, which in our case not only meets ICANN's requirements, but extends significantly beyond it as described in our response to Q28 and Q29.

3. USER EXPERIENCE GOALS

.CITY considers both its Registrants and the end-users that access .CITY websites as its users. Our goal is to create a highly reliable namespace and provide an outstanding user experience to both Registrants and end-users of .CITY.

Registrants of .CITY have an assurance of a scalable, resilient registry with 100% uptime, low latency, and exemplary security standards. Registrants will have the option to register the domain name of their choice, without much saturation of the namespace. Our registration policies and abuse mitigation policies ensure that Registrants will get advantages like higher recognition, better branding and more desirable, shorter names.

Our content and acceptable use policies and abuse mitigation processes ensure that end-users are benefited from a clean namespace. These are described in further detail in our response to Q28 and Q29.

4. REGISTRATION POLICIES IN SUPPORT OF GOALS

4.1 GENERAL NAMES

The goals of .CITY are outlined in the sections above. These goals are supported by the following artifacts -

* Registration policies and processes
* Acceptable usage policies and content guidelines
* Abuse mitigation processes
* Rights protection mechanisms
* Dispute resolution polices

To this effect we have created unprecedented Abuse mitigation policies and Rights protection mechanisms that go significantly above and beyond mandatory requirements and common practice. The salient aspects of all of the above are described below -

* DotCity Inc. is a wholly owned subsidiary within the Directi Group. The Directi Group runs various businesses including several ICANN Accredited Domain Registrars (ResellerClub.com and BigRock.com) and Web Hosting companies. With over four million active domain names registered through its registrars, Directi has significant experience (over 10 years) of managing domain name abuse mitigation and rights protection. Directi has been heralded as a white hat registrar and the undisputed leader with respect to abuse mitigation.
* Our Abuse and compliance processes will be run by the Directi Group
* We have an elaborate and detailed Accepted usage and content policy that covers over 11 macro forms of violations
* .CITY will create a zero-tolerance reputation when it comes to abuse
* We have a defined SLA for responding to abuse complaints ensuring guaranteed turn-around time on any abuse complaint depending on its severity
* We will work closely with LEA and other security groups to mitigate abuse within TLD by providing them with special interfaces (eg searcheable whois) and interacting with them regularly in terms of knowledge sharing.
* Other abuse mitigation steps we undertake include profiling, blacklisting, proactive quality reviews, industry collaboration and information sharing, regular sampling, contractual enforcements and sanctions
* The protection of trademark rights is a core goal of .CITY. .CITY will have a professional plan for rights protection. It will incorporate best practices of existing TLDs, going above and beyond the ICANN mandated RPMs to prevent abusive registrations and rapidly take-down abuse when it does occur.
* Standard RPMs such as Sunrise, Trademarks claims service, URS, UDRP, SDRP, PDDRP, SPOC etc are all provided for. Additional RPMs such as Optional Trademark declaration, profiling and blacklisting, proactive quality reviews, APWG Review and others will also be provided.

The above salient points barely scratch the surface in detailing the steps that .CITY will take in order to build a reputation of operating a clean, secure and trusted namespace. Significant details of all of the above and more are provided in our responses to Q26, Q27, Q28 and Q29

4.2. RESERVED NAMES

* We will reserve the following classes of domain names, which will not be available to registrants via the Sunrise or subsequent periods:
** The reserved names required in Specification 5 of the new gTLD Registry Agreement.
** The geographic names required in Specification 5 of the new gTLD Registry Agreement. See our response to Question 22 ("Protection of Geographic Names") for details.
** The registry operator will reserve its own name and variations thereof, and registry operations names (such as nic.CITY, registry.CITY, and www.CITY), so that we can point them to our Web site. Reservation of the registry operator's names was standard in ICANN's past gTLD contracts.
** We will also reserve names related to ICANN and Internet standards bodies (iana.CITY, ietf.CITY, w3c.CITY, etc.), for delegation of those names to the relevant organizations upon their request. Reservation of this type of names was standard in ICANN's past gTLD contracts. The list of reserved names will be published publicly before the Sunrise period begins, so that registrars and potential registrants will know which names have been set aside.
* We will reserve generic names which will be set aside for distribution via special mechanisms.

5. PROTECTING PRIVACY OF REGISTRANTS' OR USERS' INFORMATION

.CITY is committed to providing a secure and trusted namespace to its Registrants and end-users. To that extent we will have several measures for protecting the privacy or confidential information of registrants or users -

* Our Whois service (web-based whois, port 43 whois and searchable whois) all have built in abuse prevention mechanisms to prevent unauthorized access, data mining, data scraping and any other abusive behavior. Details of this are provided in our response to Q26
* .CITY will allow Registrants to use privacy protection services provided by their Registrars in the form of a Proxy whois service as long as they follow the guidelines stipulated within our response to Q28 to prevent any abuse of the same
* As per the requirements of the new gTLD Registry Agreement (Article 2.17), we shall notify each of our registrars regarding the purposes for which data about any identified or identifiable natural person ("Personal Data") submitted to the Registry Operator by such registrar is collected and used, and the intended recipients (or categories of recipients) of such Personal Data. (This data is basically the registrant and contact data required to be published in the WHOIS.)
* We will also require each registrar to obtain the consent of each registrant in the TLD for such collection and use of Personal Data. As the registry operator, we shall not use or authorize the use of Personal Data in a way that is incompatible with the notice provided to registrars.
* As the registry operator we shall take significant steps to protect Personal Data collected from registrars from loss, misuse, unauthorized disclosure, alteration, or destruction. In our responses to Q24, Q30 and Q38 we detail the security policies and procedures we will use to protect the registry system and the data contained there from unauthorized access and loss.
* As registry operator we impose certain operational standards for our registrars. In order gain and maintain accreditation for our TLD, we require them to adhere to certain information technology policies designed to help protect registrant data. These include standards for access to the registry system. Please see our response to Q24, Q25 and Q30 for details.
* We offer a "registry lock" service, designed to help protect participating registrants' contact data from unauthorized modification, and against unauthorized domain transfers and deletions. Please see our response to Q27 for details.
* .CITY implements DNSSEC at the zone which guarantees origin authentication of DNS data, authenticated denial of existence, and data integrity. This protects end-users from a man-in-the-middle attack protecting the privacy of data of end-users.

6. OUTREACH AND COMMUNICATIONS

* We will engage in relevant PR and outreach programs as well as ensure appropriate publication of information on our website.
* Our outreach efforts will thus be directed towards our target market in coordination with Registrar partners, to ensure greater adoption of the .CITY TLD. One important method of outreach will involve co-marketing programs with registrars. We will also leverage Directi's existing channel of 65,000 Resellers, and its strategic relationships with other ICANN Accredited Registrars.

The communication and outreach will focus on -

* Education amongst the Registrants and Internet Users about the new .city namespace, and the immense possibilities and internet innovations that it could result in.
* Generating awareness of our Registration policies, Acceptable usage and content policies, Abuse mitigation processes and Rights protection mechanisms

This completes our response to Q18(b).

.City considers both its Registrants and the end-users that access .City websites as its users. Our goal is to create a highly reliable namespace and provide an outstanding user experience to both Registrants and end-users of .City. To that extent it is our goal to -

* Reduce / minimize any incremental costs / negative consequences imposed upon our users

* Increase / maximize the value added to our Registrants and end-users

* Ensure that the net effect of .City on its users is that of positive value creation

In this response we explore how .City achieves a net benefit for Registrants and End-users.

1. MINIMIZING COSTS

1.1 REGISTRANTS

It is our goal to provide Registrants of .City incremental value and minimize any negative consequences and costs associated with .City. We address this in the following manner

1.1.1 SUNRISE, TMCH, RPMs

Rights protection is a core goal of .City. Our Right Protection mechanisms go significantly above and beyond the mandatory RPMs ensuring protection of trademark and IP rights of domain registrants and reducing the costs associated with rights protection for Registrants. Our elaborate RPMs are described in significant detail in our response to Q29. Some salient aspects of these are as follows -

* We offer a sunrise period to provide an opportunity for legitimate Registrants to block domain names in .City before general availability begins, preventing unnecessary post-facto litigation

* We will integrate with the Trademark Clearing House in the manner prescribed to provide the Trademarks claims service, so as to alert potential Registrants of any trademark violations prior to registration, as well as notify mark holders of potential mark violations

* We will provide SDRP, URS, UDRP and PDDRP reducing litigation costs by providing legitimate Registrants the opportunity to resolve disputes through standardized arbitration proceedings.

* Additionally we have pioneering RPMs like Optional Trademark Declaration, Profiling and Blacklisting, Proactive Quality assurance, APWG review etc - all intended to reduce rights violations and hence reduce costs for Registrants

The above salient points barely scratch the surface in detailing the steps that .City will take in order to reduce costs of Registrants with respect to rights violations. Significant details of all of the above and more are provided in our responses to Q26, Q27, Q28 and Q29.

1.1.2 MULTIPLE APPLICATIONS FOR A DOMAIN

All of the RPMs described in section 1.1.1 above ensure that applicants for domain names in .City are legitimate right holders for the applied string. During general availability domain names will be allocated on a first come first serve basis amongst applicants. During the initial registry launch periods of Sunrise and Landrush if multiple applications for the same domain name are received from applicants then the same will be distributed in the following manner -

* Incase of multiple sunrise applications for the same domain name, all applications will be validated against the TMCH for a valid trademark. Applications that do not qualify will be dropped.

* All remaining applications will be distributed through a fair auction.

1.1.3 COST BENEFITS FOR REGISTRANTS

The ICANN new gTLD program marks a historical event in the timeline of the Internet. It is an unprecedented event and one that will yield tremendous benefits for consumers. At this preliminary stage it is impossible to determine the true value consumers will derive from increase in competition and choice. However there is historical data to go by. Upon the launch of Domain Registrars and creation of competition amongst registrars, the Registrants benefited from reduced pricing.

With .City our goal is to provide fair pricing for domains within .City that reflect the value proposition derived by the Registrants of .City. While we do not have any committed pricing plans as yet and the same will be determined during the launch process, we do anticipate providing promotional offers through the life of .City for the purpose of customer acquisition. This is not too dissimilar from other gTLD registries currently in existence who offer ongoing promotional offers to their customer base.

1.1.4 PRICE ESCALATIONS

The ICANN new gTLD program is an unprecedented event and the actual nature of pricing pressures will only be determinable once several TLDs have successfully launched. At this preliminary stage it is impossible to commit to any pricing strategy on our part. We strongly believe that ultimately, the open market will determine the viability of pricing models and dictate pricing strategy for everyone. We intend to maintain the freedom to set pricing to accommodate for the existence of 100s of TLDs and business models and create a sustainable long term business model. Our goal is to provide fair pricing for domains within .City that reflect the value proposition derived by the Registrants of .City.

1.2 END USERS

It is our goal to provide end users of .City incremental value and minimize any negative consequences and costs associated with .City. We address this in the following manner

End-users bear a considerable amount of cost as a result of various forms of Internet abuse such as spam, malware, phishing, pharming, hacking, identity theft etc. Any TLD that implements policies and processes to create a clean namespace will result in a considerable reduction of these forms of abuse and hence a significant saving in terms of cost to consumers

.City intends to set an example when it comes to abuse mitigation and preventing abuse within .City. To this effect we have created unprecedented Abuse mitigation policies and Rights protection mechanisms that go significantly above and beyond mandatory requirements and common practice. These are detailed in our response to Q28. We strongly believe these practices will result in a significant reduction in online abuse and considerable savings for end users of .City. We similarly hope to set an example for other TLDs and cooperate with the industry in creating a clean internet experience for internet users.

2. COST BENEFIT ANALYSIS

There has been considerable debate within the community concerning the cost benefit analysis of launching new gTLDs. We strongly believe that the launch of new gTLDs and our implementation of .City will and add considerable value and result in a net positive effect on Registrants and end-users worldwide.

We recognize that there will be a post launch review of the New gTLD Program, from the perspective of assessing therelative costs and benefits achieved in the expanded gTLD space.

To this extent we would like to offer the following pointers concerning .City as well as the general expansion of the new gTLD space in determining the net positive value generated for Registrants and end users -

* .City will reduce overall cost for end-users in combating fraud and other forms of online abuse by implementing pioneering processes and anti-abuse policies as described in our response to Q28. Billions of dollars are spent worldwide combating various forms of fraud such as malware, phishing, spamming etc. Our abuse policies will result in overall reduction of these forms of abuses within .City resulting in a considerable reduction in global costs spent towards combating these abuses. We also strongly believe that introduction of new gTLDs will result in increased competition which will drive significant innovation as well as competitive pressures for everyone in the industry to improve their abuse mitigation processes resulting in overall cost reduction for end-users

* The value of a Registrant getting the name they want is immeasurably larger than any costs resulting from expansion of the namespace. DotCity Inc. is a subsidiary within the Directi Group which owns and operates several ICANN Accredited Registrars. Our stats show that 70% of the users who check for a .com domain name do not get their desired name. Until this launch of the new gTLD program there were very limited alternatives and none very viable/desirable for Registrants to choose from. .City will expand the namespace thus providing a higher probability for new Registrants to obtain names they desire

* In general increased competition always results in pricing benefits for Registrants. .City will provide additional options to new Registrants resulting in overall benefits to Registrants

* By virtue of registering a domain name within .City a Registrant declares themselves to be deeply related to a particular city. This adds considerable value in terms of searchability, SEO, creating trust, branding and a sense of belonging. As of now the only mechanism that exists for users to find a specific website are search engines. Search engines however do not classify the results in any manner to make it easier for users to determine which links are relevant to them with respect to their current search. .City enables Registrants to standout amongst search results and allows end users to directly co-relate as to whether a search result will likely be what they are looking for. This adds considerable value to Registrants who can be easily found now, and to end-users who will take lesser time to find sites that are built to serve their city.

This completes our response to Q18(c).

We have engaged ARI Registry Services (ARI) to deliver services for this TLD. This response describes protection of geographic names as implemented by ARI.

1. PROTECTION OF GEOGRAPHIC NAMES

In accordance with Specification 5 of the New gTLD Registry Agreement, we will initially reserve all geographic names at the second level, and at all other levels within the TLD at which the registry operator provides for registrations.

ARI supports this requirement by using the following internationally recognised lists to develop a comprehensive master list of all geographic names that are initially reserved:

- The 2-letter alpha-2 code of all country and territory names contained on the ISO 3166-1 list, including all reserved and unassigned codes [http://www.iso.org/iso/support/country_codes/iso_3166_code_lists/iso-3166-1_decoding_table.htm].
- The short form (in English) of all country and territory names contained on the ISO 3166-1 list, including the European Union, which is exceptionally reserved on the ISO 3166-1 List, and its scope extended in August 1999 to any application needing to represent the name European Union [http://www.iso.org/iso/support/country_codes/iso_3166_code_lists/iso-3166-1_decoding_table.htm#EU].

- The United Nations Group of Experts on Geographical Names, Technical Reference Manual for the Standardisation of Geographical Names, Part III Names of Countries of the World. This lists the names of 193 independent States generally recognised by the international community in the language or languages used in an official capacity within each country and is current as of August 2006[http://unstats.un.org/unsd/geoinfo/ungegn/docs/pubs/UNGEGN%20tech%20ref%20manual_m87_combined.pdf].

- The list of UN member states in six official UN languages prepared by the Working Group on Country Names of the United Nations Conference on the standardisation of Geographical Names [http://unstats.un.org/unsd/geoinfo/UNGEGN/docs/9th-uncsgn-docs/econf/9th_UNCSGN_e-conf-98-89-add1.pdf].

Names on this reserved list in ARI's registry system are prevented from registration.

A corresponding list of geographic names will also be available to the public via our website, to inform Registrars and potential registrants of reserved names. The lists noted above, are regularly monitored for revisions, therefore the reserved list (both within the registry and publicly facing) will be continually updated to reflect any changes.

In addition to these requirements, ARI are able to support the wishes of the Governmental Advisory Council (GAC) or any individual Government in regard to the blocking of individual terms on a case by case basis. ARI's registry system allows such additions to be made by appropriately authorised staff, with no further system development changes required.

The following applies to all Domain Names contained within the registry's reserved list:
- Attempts to register listed Domain Names will be rejected.
- WhoIs queries for listed Domain Names will receive responses indicating their reserved status.
- Reserved geographic names will not appear in the TLD zone file.
- DNS queries for reserved domain names will result in an NXDOMAIN response.

2. PROCEDURES FOR RELEASE

We understand that if we wish to release the reserved names at a later date, this will require agreement from the relevant government(s) or review by the GAC, and subsequent approval from ICANN.

This completes our answer to Q22.