18(b) How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?

Prototypical answer:

i. What is the goal of your proposed gTLD in terms of areas of specialty, service levels, or reputation?

There are no new services being introduced with .cloud, hence no area of specialities for Registrars, registrants or Internet users.

The service level will be defined in the Registry Registrar Agreement in accordance with ICANN policy and business standards.

The .cloud TLD will not create any confusion for users. The word .cloud is not connected to any bad behaviour.

CloudNames will establish .cloud as a TLD with a good reputation as a well functioning Registry with a reliable and secure technical solution, knowledgeable and service-minded staff and a well functioning namespace. In addition, the long term reputation will be that the TLD fulfills the EU requirements regarding the various EU data directives.

ii. What do you anticipate your proposed gTLD will add to the current space, in terms of competition, differentiation, or innovation?

We anticipate that .cloud will increase in a positive way the competition between the present gTLDs and the country code top level domains (ccTLDs).

One of the conclusions in the OECD report: “Generic Top Level Domain Names: Market Development and Allocation Issues (DSTI⁄ICCP⁄TISP(2004)2⁄FINAL)” located at http:⁄⁄www.oecd.org⁄dataoecd⁄56⁄34⁄32996948.pdf is that there is competition between the registries, further that some registries are very dominant. Introducing .cloud will create more competition between the registries, and will enable existing registrants and new entities to acquire a more specific identifier for their activities.

The name of the string “.cloud” will be clearly differentiated in the existing top levels and make it possible for the market to have a new identifier for their activities in the name space of .cloud.

The business model for .cloud (reference #45-50) defines a price for second level registrations that will be competitive for companies and individuals seeking an identity on the Internet.

CloudNames believe that the name space under .cloud will create new services for Internet users that will differentiate this name space compared to others.

iii. What goals does your proposed gTLD have in terms of user experience?

The .cloud TLD will be available for registration through ICANN accredited registrars and their resellers. Combined with Afilias and their experienced provisioning system and CloudNames experience in the European and US market, the new TLD will benefit all users.

.cloud’s registration policy states that the name space is available on a first-come, first-served basis. Further than that no particular requirements are needed.

The word “cloud” is a general term that has become synonymous with the Internet or a piece of the Internet. The new TLD .cloud could apply and mean different things to different markets.

The objective for .cloud is to create an easy-to-register label for companies, organizations and individuals with a business model and vision to grow their presence and identity on the Internet.

iv. Provide a complete description of the applicant’s intended registration policies in support of the goals listed above.

RESERVED ON THE SECOND LEVEL:
* Reserved names as referred in New Registry Agreement Specification 5.

** Example. The label “EXAMPLE” shall be reserved at the second level and at all other levels within the TLD at which Registry Operator makes registrations.

** Two-character labels. All two-character labels shall be initially reserved. The reservation of a two-character label string may be released to the extent that Registry Operator reaches agreement with the government and country-code manager. The Registry Operator may also propose release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes.

** Tagged Domain Names. Labels may only include hyphens in the third and fourth position if they represent valid internationalized domain names in their ASCII encoding (for example ʺxn--ndk061nʺ).

** Second-Level Reservations for Registry Operations. The following names are reserved for use in connection with the operation of the registry for the TLD. Registry Operator may use them, but upon conclusion of Registry Operatorʹs designation as operator of the registry for the TLD they shall be transferred as specified by ICANN: NIC, WWW, IRIS and WHOIS.

** Country and Territory Names. The country and territory names contained in the following internationally recognized lists shall be initially reserved at the second level and at all other levels within the TLD at which the Registry Operator provides for registrations:

*** the short form (in English) of all country and territory names contained on the ISO 3166- 1 list, as updated from time to time, 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 Standardization of Geographical Names, Part III Names of Countries of the World; and

*** the list of United Nations member states in 6 official United Nations languages prepared by the Working Group on Country Names of the United Nations Conference on the Standardization of Geographical Names;
provided, that the reservation of specific country and territory names may be released to the extent that Registry Operator reaches agreement with the applicable government(s), provided, further, that Registry Operator may also propose release of these reservations, subject to review by ICANN’s Governmental Advisory Committee and approval by ICANN.

* Registry reserved names
** Upon launch of .cloud, the Registry Operator will inform the market in due manner a complete list of reserved names in addition to the above Second-Level Reservation for Registry Operation.
Labels eligible for registration on second level:
* All labels not referred to in “Reserved on second level”
* IDN registrations in the languages and script as referred to in #44 and in accordance with RFCs 5890, 5891, 5892, 5893 and their successors
* A domain name must consist of at least 3 and at most 63 characters.
* The first and the last character of the domain name must be a letter or a digit
* The domain name must not be identical to a registered domain name
* Labels in accordance with RFC1035, RFC1123, RFC3490, RFC3491 and RFC3492

ANTI-ABUSE POLICY:
The following policy (ʺ.cloud Domain Anti-Abuse Policyʺ) will be announced pursuant to the Registry-Registrar Agreement (ʺRRAʺ) in effect between CloudNames and each of its Registrars. Abusive use(s) of .cloud domain names will not be tolerated.
CloudNames defines abusive use as the wrong or excessive use of power, position or ability, and includes, without limitation, the following:
* Illegal or fraudulent actions;

* Spam: The use of electronic messaging systems to send unsolicited bulk messages. The term applies to e-mail spam and similar abuses such as instant messaging spam, mobile messaging spam, and the spamming of Web sites and Internet forums. An example, for purposes of illustration, would be the use of email in denial-of-service attacks;

* Phishing: The use of counterfeit Web pages that are designed to trick recipients into divulging sensitive data such as user names, passwords, or financial data;

* Pharming: The redirecting of unknowing users to fraudulent sites or services, typically through DNS hijacking or poisoning;

* Willful distribution of malware: The dissemination of software designed to infiltrate or damage a computer system without the ownerʹs informed consent.? Examples include, without limitation, computer viruses, worms, keyloggers, and trojan horses;

* Fast flux hosting: Use of fast-flux techniques to disguise the location of Web sites or other Internet services, or to avoid detection and mitigation efforts, or to host illegal activities. Fast-flux techniques use DNS to frequently change the location on the Internet to which the domain name of an Internet host or name server resolves. Fast flux hosting may be used only with prior permission of Afilias or CloudNames;

* Botnet command and control: Services run on a domain name that are used to control a collection of compromised computers or ʺzombies,ʺ or to direct denial-of-service attacks (DDoS attacks);

* Distribution of child pornography; and

* Illegal Access to Other Computers or Networks: Illegally accessing computers, accounts, or networks belonging to another party, or attempting to penetrate security measures of another individualʹs system (often known as ʺhackingʺ). Also, any activity that might be used as a precursor to an attempted system penetration (e.g., port scan, stealth scan, or other information gathering activity).
Pursuant the RRA, CloudNames reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion; (1) to protect the integrity and stability of the registry; (2) to comply with any applicable laws, government rules or requirements, requests of law enforcement, or any dispute resolution process; (3) to avoid any liability, civil or criminal, on the part of CloudNames, as well as its affiliates, subsidiaries, officers, directors, and employees; (4) per the terms of the registration agreement or (5) to correct mistakes made by CloudNames or any Registrar in connection with a domain name registration. CloudNames also reserves the right to place upon registry lock, hold or similar status a domain name during resolution of a dispute. Abusive uses, as defined above, undertaken with respect to .cloud domain names shall give rise to the right of CloudNames to take such actions as deemed possible in the RRA in its sole discretion.
The Registrars must impose this policy on the domain holders as a part of the agreement. Registrars will be expected to include language in their registrar-registrant contracts that indemnifies the registrar if it takes action, and allows the registrar to suspend or cancel a domain name; this will be in addition to the registry Anti-Abuse Policy. Generally, registrars can act if the registrant violates the registrar’s terms of service, or violates ICANN policy, or if illegal activity is involved, or if the use violates the registry’s Anti-Abuse Policy.
If a registrar does not take action within a time period indicated by the registry operator (usually 24 hours), the registry operator might then decide to take action itself. At all times, the registry operator reserves the right to act directly and immediately if the potential harm to Internet users seems significant or imminent, with or without notice to the sponsoring registrar.
The registry operator will be prepared to call upon relevant law enforcement bodies as needed.
When valid court orders or seizure warrants are received from courts or law enforcement agencies of relevant jurisdiction, the registry operator will order execution in an expedited fashion. Compliance with these will be a top priority and will be completed as soon as possible and within the defined timelines of the order.

V. Will your proposed gTLD impose any measures for protecting the privacy or confidential information of registrants or users? If so, please describe any such measures.

CloudNames will cooperate with ICANN with the objective to modify the “Specification for Registration Data Publication Service” as given in the NewTLD Registry Agreement Specification 4, to be tuned into European legislation reflecting privacy and consumer protection.

CloudNames is aware of a request from Fundacio´ puntCAT to alter the whois service for .CAT (Reference ICANN Registry Request Service, Ticked ID: L6T5V-0Z9D2). CloudNames will monitor this request carefully and cooperate with both ICANN and Fundacio´ puntCAT for a modification of the .cloud whois service.

Until this process is finalized, CloudNames will adopt the whois policy as described in NewTLD Registry Agreement Specification 4.

Describe whether and in what ways outreach and communications will help to achieve your projected benefits.

CloudNames plan to use a variety of communication tools such as online marketing and PR activities in order to communicate the mission and benefits of .cloud. Communication is necessary in order to for .cloud to be widely accepted.

Similar gTLD applications: (1)