| gTLD | Full Legal Name | E-mail suffix | Detail | | .IWC | Richemont DNS Inc. | valideus.com | View |
How do you expect that your proposed gTLD will benefit registrants, internet users and others?
The registry will be stringently controlled by authorised Richemont DNS personnel on behalf of the Richemont company, IWC, but it is predicted that it will also benefit the following stakeholders, all in the global public interest:
• Our customers: whether they are industry professionals or consumers, a new .IWC registry will benefit them by becoming a location for authentic, accessible information about the company and its collections.
• Our employees: a new gTLD will reinforce our brand worldwide and provide a more secure communication channel.
• Our authorized dealers: a new gTLD will provide our authorized dealer network with a space that sets them apart from counterfeiters and provides them with the direct relation to IWC in the minds of the public.
• Our investors seeking accurate information regarding IWC’s goods and services.
• Law enforcement seeking information about genuine products.
What is the goal of your proposed gTLD in terms of areas of speciality, service levels
reputation?
At Richemont, we pride ourselves on the integrity of our group brands and the high quality of our luxury goods. This will be reflected in the treatment of the new gTLD on IWC’s behalf. The goal is to position Richemont DNS, on behalf of IWC, to exploit this latest internet advance in order to further enhance the IWC brand and reputation. We hope that this registry will be regarded by IWC customers, as well as by the investors who follow our companies, as the authentic location for accurate information on IWC’s collections and products.
What do you anticipate your proposed gTLD will add to the current space in terms of competition, differentiation or innovation?
Richemont DNS is eager to operate a registry with shorter domain names that are universally applicable across the globe. We feel it offers clarity, simplicity and will enable our customers to place their trust in our registry while also providing potential for enhanced communication with them and with staff.
Richemont DNS looks forward to utilising the new registry in conjunction with IWC’s current domains and are particularly keen to market under the term .IWC in the future if the new gTLD process is a success. This new gTLD also enables brands to potentially leave behind complex naming hierarchies inherent in country code extensions.
What goals does your proposed gTLD have in terms of user experience?
IWC hopes that its customers and others who visit to communicate with IWC know they are in a trusted and authentic destination once they arrive at the new gTLD. We want them to be confident that they will receive accurate information and that their sensitive personal details will be protected in accordance with applicable laws as interpreted and applied.
Provide a complete description of the Richemont DNS’s intended registration policies in support of the goals above
Richemont DNS will be the operator of the .IWC registry and is the Richemont DNS entity in the ICANN process. The Richemont DNS Domain Name Management team will be responsible for the development, maintenance and enforcement of the Richemont DNS Domain Management Policy. This policy will define the rules associated with eligibility and domain name allocation, will set out the license terms governing the use of a .IWC domain name and will describe the dispute resolution policies for the IWC gTLD. This policy is intended to be updated and revised regularly to reflect IWC’s commercial and strategic interests and, where appropriate, ICANN consensus policies as they develop.
Registration of a .IWC domain name will be undertaken in four steps: Eligibility Confirmation, Naming Convention Check, Acceptable Use Review, and finally Registration. All domains in the .IWC registry will remain the property of Richemont.
Each applied for A-label character string must conform to the .IWC rules of eligibility. Each .IWC name must:
• Be at least 3 characters and no more than 63 characters long
• Not contain a hyphen on the 3rd and 4th position (except IDNs)
• Contain only letters (a-z), numbers (0-9) and hyphens or a combination of these
• Start and end with an alphanumeric character, not a hyphen
• Not match any character strings reserved by ICANN
• Not match any protected country names or geographical terms
Internationalized domain names (IDN) may be supported in the .IWC registry at the second level.
Users of .IWC names must utilise their domains solely for purposes that enhance IWC’s strategic or commercial interests. .IWC domains may not be used in a way which knowingly infringes any third party intellectual property rights or gives rise to moral or public order questions.
Users of .IWC names may not delegate or assign any rights in .IWC domains to external organizations, institutions, or individuals.
All .IWC domains will carry accurate and up to date registration records.
The Richemont DNS Domain Name Management Team may revoke a .IWC domain name at any time in line with Richemont’s corporate and strategic interests. Cancellation of any Required License will result in revocation of any second level domain name that was registered under any such Required License.
The .IWC registry will be ICANN compliant: the registry will interface with the Trademark Clearinghouse, operate a Sunrise and IP Claims and all registrants must comply with the UDRP and the URS and other relevant consensus policies.
Will your proposed gTLD impose any measures for protecting the privacy of confidential information of registrants or users?
As a global luxury goods brand with a high profile, we take our responsibility to protect the confidential information of customers and staff very seriously.
The .IWC registry will continue our policy of protecting confidential information. Richemont DNS will comply with the Personal Data obligations of the ICANN Registry Agreement and all applicable data protection laws as interpreted and applied. As required, approved representatives will be registered as data handlers and trained to ensure compliance with ICANN’s requirements.
We will:
• Document policies and procedures including an escalation process
• Use appropriate levels of encryption and physical security
• Train key staff and ensure responsibilities are understood and documented in rules of conduct
• Limit access to records only to those employees or service providers who need access for the performance of their job duties
• Test procedures
• Monitor best practice and ICANN’s mandated and recommended policies
• Audit the work of providers including the Escrow provider and checking data.
Describe whether and in what ways outreach and communications will help to achieve your projected benefits?
We will produce and publish guidelines for internal use. These are intended to provide clarity on who can apply for a .IWC second level domain and how any such second level domain name is to be used. This is a standard registry closed to third parties so these guidelines should ensure that .IWC domains are used in accordance with IWC’s objectives by authorised Richemont DNS representatives. For example, it will be necessary to create a home page for the registry using straightforward messaging for the benefit of internal users so that our policies and the rules of eligibility are clearly understood.
| gTLD | Full Legal Name | E-mail suffix | Detail | | .TEVA | Teva Pharmaceutical Industries Limited | valideus.com | View |
The registry will be stringently controlled by authorised Teva personnel and all registrants must have the Required License but it is predicted that it will also benefit the following stakeholders:
• Our customers: whether they are industry professionals or consumers, a new .Teva registry will benefit them by becoming a location for authentic, accessible information about the company and our products.
• Our employees: a new gTLD will reinforce our brand worldwide and provide a more secure communication channel.
• The free press and relevant governments. Since the .Teva registry will be a single entity registry, the free press and relevant governments will be able to take advantage of a single location for accurate information regarding the Teva.
What is the goal of your proposed gTLD in terms of areas of speciality, service levels reputation?
At Teva, we pride ourselves on the integrity of our brand and the high quality of our products. This will be reflected in the treatment of the new gTLD. Our goal is to position ourselves to exploit this latest internet advances in order to enhance our brand and reputation. We hope that our registry will be regarded by our customers as well as the investors who follow us and our peers in the pharma world, as the authentic location for accurate information on us and our work.
What do you anticipate your proposed gTLD will add to the current space in terms of competition, differentiation or innovation?
We are eager to operate a registry with shorter domain names that are universally applicable across the globe. We feel it offers clarity, simplicity and will enable our customers to place their trust in our registry while also providing potential for enhanced communication.
We look forward to utilising our new registry in conjunction with our current domains and are particularly keen to market under the term .Teva in future if the new gTLD process is a success. In enabling brands to leave behind complex naming hierarchies inherent in country code extensions, it accords with our culture of getting results by simplicity.
What goals does your proposed gTLD have in terms of user experience?
Regardless of their geographic location, we hope that our customers and others who visit to communicate with us, including investors, government, regulatory representatives and pharma experts, know they are in a trusted and authentic destination once they arrive at the new gTLD. We want them to be confident that they will receive accurate information and that their sensitive personal details will be protected.
Provide a complete description of the applicant’s intended registration policies in support of the goals above.
Teva is the operator of the .Teva registry. The Teva Domain Name Management team is responsible for the development, maintenance and enforcement of the Teva Domain Management Policy. This policy, which will be developed prior to launch, will define the rules associated with eligibility and domain name allocation, sets out the license terms governing the use of a .Teva domain name and describes the dispute resolution policies for the Teva gTLD. This policy will be updated and revised regularly to reflect Teva’s commercial and strategic interests and, where appropriate, ICANN consensus policies. The policy will restrict registration to only Teva and those who have the Required License.
Registration of a .Teva domain name will be undertaken in four steps: Eligibility Confirmation, Naming Convention Check, Acceptable Use Review, and finally Registration. All domains in the .Teva registry will remain the property of Teva. There will be no license right to use a domain name which is independent of the Required License.
Each applied for character string must conform to the .Teva rules of eligibility. Each .Teva name must:
• Be at least 3 characters and no more than 63 characters long
• Not contain a hyphen on the 3rd and 4th position (tagged domains)
• Contain only letters (a-z), numbers (0-9) and hyphens or a combination of these
• Start and end with an alphanumeric character, not a hyphen
• Not match any character strings reserved by ICANN
• Not match any protected country names or geographical terms
Internationalized domain names (IDN) will be supported in the .Teva registry at the second level.
All .Teva names must be utilised solely for purposes that enhance Teva’s strategic or commercial interests. .Teva domains may not be used in a way which knowingly infringes any third party intellectual property rights or gives rise to moral or public order questions.
.Teva domain names may not be delegated or assigned to external organizations, institutions, or individuals.
All .Teva domains will carry accurate and up to date registration records.
The Teva Domain Name Management Team may revoke a .Teva domain name at any time in line with Teva’s corporate and strategic interests.
The Teva registry will be ICANN compliant: the registry will interface with the Trademark Clearinghouse, operate a Sunrise and IP Claims and all registrants must comply with the UDRP and the URS,among other consensus policies.
Will your proposed gTLD impose any measures for protecting the privacy of confidential information of registrants or users?
As a global generic pharmaceuticals company, we take our responsibility to protect the confidential information of customers and staff very seriously.
The .Teva registry will continue our policy of protecting confidential information. Teva will comply with the Personal Data obligations of the ICANN Registry Agreement and it will meet standards such as those laid down in the European Union Data Protection Directive. As required, approved representatives will be registered as data handlers and trained to ensure compliance with ICANN’s requirements.
We will:
• Document policies and procedures including an escalation process
• Use appropriate levels of encryption and physical security
• Train key staff and ensuring responsibilities are understood and documented in rules of conduct
• Limit access to records only to those employees or service providers who need access for the performance of their job duties
• Test procedures
• Monitor best practice and ICANN’s mandated and recommended policies
• Audit the work of providers including the Escrow provider and checking data.
Describe whether and in what ways outreach and communications will help to achieve your projected benefits?
We will produce and publish guidelines for internal use. These are intended to provide clarity on who can qualify to register a .Teva domain and how it is to be used. As mentioned above, this is a standard registry closed to third parties that do not have the Required License so these guidelines should ensure that .Teva domains are used in accordance with Teva’s objectives by authorised Teva representatives. For example, it will be necessary to create a home page for the registry using straightforward messaging for the benefit of internal users so that our policies and the rules of eligibility are clearly understood.