.ovh New gTLD Application
Click to view Chinese translation articles.
-----------------------------------
New gTLD Application Submitted to ICANN by: OVH SAS
String: ovh
Originally Posted: 13 June 2012
Application ID: 1-1074-68417
Applicant Information
- Full legal name
OVH SAS
- Address of the principal place of business
2, rue Kellermann
ROUBAIX Cedex 1 59100
FR
- Phone number
+33 3 20 82 73 32
- Fax number
+33 3 20 83 99 28
- If applicable, website or URL
http:⁄⁄www.ovh.com
Primary Contact
6(a). Name
Mr. Thibaud Saudrais
6(b). Title
Quality Manager
6(c). Address
6(d). Phone Number
+33 3 20 82 73 32
6(e). Fax Number
6(f). Email Address
Secondary Contact
7(a). Name
Mr. Stéphane Lesimple
7(b). Title
Domain Names Manager
7(c). Address
7(d). Phone Number
+33 3 20 82 73 32
7(e). Fax Number
7(f). Email Address
Proof of Legal Establishment
8(a). Legal form of the Applicant
Société par Actions Simplifiée
8(b). State the specific national or other jursidiction that defines the type of entity identified in 8(a).
French Law – Code de commerce français art. L227-1 à L227-20 et L244-1 à L244-4
8(c). Attach evidence of the applicant's establishment.
Attachments are not displayed on this form.
9(a). If applying company is publicly traded, provide the exchange and symbol.
9(b). If the applying entity is a subsidiary, provide the parent company.
9(c). If the applying entity is a joint venture, list all joint venture partners.
Applicant Background
11(a). Name(s) and position(s) of all directors
Halina Klaba Directeur général délégué
Henryk Klaba Président
Miroslaw Klaba Directeur général délégué
Octave Klaba Directeur général
11(b). Name(s) and position(s) of all officers and partners
Nicolas Boyer Chief Financial Officer
Stéphane Lesimple Domain Names Manager
Thibaud Saudrais Quality Manager
11(c). Name(s) and position(s) of all shareholders holding at least 15% of shares
OVH GROUPE SAS Not Applicable
11(d). For an applying entity that does not have directors, officers, partners, or shareholders: Name(s) and position(s) of all individuals having legal or executive responsibility
Applied-for gTLD string
- Provide the applied-for gTLD string. If an IDN, provide the U-label.
ovh
14(a). If an IDN, provide the A-label (beginning with "xn--").
14(b). If an IDN, provide the meaning or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applicant.
14(c). If an IDN, provide the language of the label (in English).
14(c). If an IDN, provide the language of the label (as referenced by ISO-639-1).
14(d). If an IDN, provide the script of the label (in English).
14(d). If an IDN, provide the script of the label (as referenced by ISO 15924).
14(e). If an IDN, list all code points contained in the U-label according to Unicode form.
15(a). If an IDN, Attach IDN Tables for the proposed registry.
Attachments are not displayed on this form.
15(b). Describe the process used for development of the IDN tables submitted, including consultations and sources used.
15(c). List any variant strings to the applied-for gTLD string according to the relevant IDN tables.
- Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string. If such issues are known, describe steps that will be taken to mitigate these issues in software and other applications.
The .OVH TLD (and its Registry Back-end Service Provider, AFNIC) ensured that there are no known operational or rendering problems concerning the applied-for gTLD string ʺ.ovhʺ.
Since the gTLD string ʺ.ovhʺ is an ASCII-only string, it is safe to assume that, just like with existing ASCII-only TLD strings like .com, .net or .de, no operational or rendering problems may be expected. In particular, the name consists only of ASCII characters that are already used for existing top level domains; all the characters in the name are even used in the leftmost position of existing TLD labels. In order to confirm this,OVHʹs Registry Back-end Service Provider has conducted a thorough research regarding whether operational or rendering issues occurred for any existing ASCII-only top level domain in the past. The results of this research confirmed the assumption.
This means that bi-directional issues (like the ones described at http:⁄⁄stupid.domain.name⁄node⁄683) will not occur, also since the TLD string does not contain digits (which behaviour in bi-directional contexts can lead to rendering issues).
As the registry supports right-to-left scripts on the second level, the respective IDN tables were carefully crafted according to IDNA2008 standards to ensure that no rendering issues occur left or right of the dot (ʺ.ʺ) character separating the top and second domain name labels (which are the only labels under the registryʹs control).
Moreover, the gTLD string exclusively uses characters from a single alphabet, does not contain digits or hyphens, and it contains characters that are not subject to homograph issues, which means there is no potential for confusion with regard to the rendering of other TLD strings.
Finally, Â OVHʹs Registry Back-end Service Provider set up a testing environment for the OVH TLD using the OVH TLD target Registration System, including an EPP SRS, Whois and DNS servers, in order to conduct a series of tests involving typical use cases (like web site operation and e-mail messaging) for a TLD. The tests revealed no operational or rendering issues with any popular software (web browsers, e-mail clients) or operating systems.
- (OPTIONAL) Provide a representation of the label according to the International Phonetic Alphabet (http://www.langsci.ucl.ac.uk/ipa/).
Mission/Purpose
18(a). Describe the mission/purpose of your proposed gTLD.
OVH was founded by Octave Klaba with the objective of bringing to as many people as possible a complete range of communication services and features, at the lowest possible price, to allow everyone to be a player of the internet sphere.
At OVH, we believe that companies and individuals alike have the right to exist on the Internet, as we strongly support the notion that the right to a digital identity is fundamental in this day and age.
The .ovh extension will be a new way for the company to take this vision even further.
18(b). How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?
One of the goals of the .ovh extension will be to identify OVH as an innovative entity close to its customers in the field of new technologies. Furthermore, it will allow the company to offer its customers new development opportunities, allowing for the registration of extensions already reserved on the more “general” TLDs.
Buying a .ovh extension will be an entry-level opportunity for an individual to secure a visible web identity at a lower cost than the current rates. It will represent the occasion for this person to easily take place on the webspace without any financial risk. Additionally, the .ovh extension will be a way for this person to assert his belonging to the OVH IT community and enjoy privileged access to OVH services and forums where a large group of customers already collaborate to provide for mutual assistance.
Access conditions to a .ovh domain are completely open, as any OVH customer can acquire one. Any company or individual can become an OVH customer, as long as they can provide contact information that will be verified by the company. Customers will have to comply with sunrise and landrush phases during the launch of the extension.
The sale of .ovh extensions by OVH will be done according to French laws and follow the recommendations of the CNIL authority and the French anti-Data Mining laws for the protection of user data. Additional Whois protection possibilities will also be available to the customer who wants to hide their contact information.
The plan to promote the .ovh extension will also answer to a communautary logic. 20 000 .ovh domain names have already been requested by those who represent the heart of our user community. It is for and with these people and through the communication tools that we provide to our customers that we want to turn the .ovh extension into the IT extension of choice on the Internet.
18(c). What operating rules will you adopt to eliminate or minimize social costs?
The basic rule for a .ovh domain registration will be: first come, first served. If a conflict should arise, priority will be given to the OVH Holding and the criterion that will establish ownership is NIC precedence: the customer with the greatest seniority will have priority. To this we will add additional measures for trademark protection.
OVH will implement the means to ensure that customers have easy access to the .ovh extension: low cost of the extension, special deals for the 100 000 first requests and free domains for customers who acquire other specific OVH services.
In order to ensure the sustainability of these conditions to its customers, OVH commits to report any price increase at least 30 days prior to actual change.