.TEVA New gTLD Application

Click to view Chinese translation articles.

-----------------------------------

New gTLD Application Submitted to ICANN by: Teva Pharmaceutical Industries Limited

 

Application Downloaded On: 28 May 2015

 

String: TEVA

 

Application ID: 1-1081-27807

 

Applicant Information

 

  1. Full legal name

Teva Pharmaceutical Industries Limited

 

  1. Address of the principal place of business

5 Basel Street Petach Tikva - 49131 IL

 

  1. Phone number

+972 392 67267

 

  1. Fax number

+972 392 67429

 

  1. If applicable, website or URL

 

Primary Contact

 

6(a). Name

Yehudah Livneh

 

6(b). Title

VP Corporate IP and Legislative Affairs

 

6(c). Address

 

6(d). Phone Number

+972 392 67489

 

6(e). Fax Number

 

6(f). Email Address

This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Secondary Contact

 

7(a). Name

Paul McGrady (in cooperation with Ellen Shankman)

 

7(b). Title

Partner

 

7(c). Address

 

7(d). Phone Number

+1 312 558 5963

 

7(e). Fax Number

 

7(f). Email Address

This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Proof of Legal Establishment

 

8(a). Legal form of the Applicant

Public Limited Liability Company

 

8(b). State the specific national or other jurisdiction that defines the type of entity identified in 8(a).

Israeli

 

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.

NASDAQ / TEVA

 

9(b). If the applying entity is a subsidiary, provide the parent company.

Not Applicable -Teva Pharmaceuticals Industries Limited is the parent company

 

9(c). If the applying entity is a joint venture, list all joint venture partners.

Not a joint venture

 

Applicant Background

 

11(a). Name(s) and position(s) of all directors

Name

Position

Amir Elstein Director

Barry Cohen Director

Chaim Hurvitz Director

Dan Suesskind Director

Erez Vigodman Director

Ory Slonim Director

Phillip Frost Director

Prof. Dafna Schwartz Director

Prof. Elon Kohlberg Director

Prof. Moshe Many Director

Prof. Roger Kornberg Director

Prof. Yitzhak Peterburg Director

Roger Abravanel Director

Yossi Nitzani Director

 

11(b). Name(s) and position(s) of all officers and partners

Name

Position

Aharon Yaari Group Vice President – Teva Generics System

Dr. Gerard Van Odijk President and Chief Executive Officer – Teva Europe

Dr. Jeremy Levin President and Chief Executive Officer Designate

Dr. Robert Koremans President and Chief Executive Officer – Teva Europe Designate

Eyal Desheh Chief Financial Officer

Guy Hadari Corporate VP, Global CIO, IT Management

Iris Beck Codner Senior VP, Chief Communication Officer

Isaac Abravanel Corporate Vice President, Human Resources & Chief Integration Officer

  1. Kevin Buchi Corporate Vice President, Global Branded Products

Moshe Manor President Teva Asia & Pacific

Prof. Itzhak Krinsky Corporate Vice President – Business Development

Richard S. Egosi Corporate Vice President and Chief Legal Officer

Ron Grupel Chief Internal Auditor

Shlomo Yanai President and Chief Executive Officer

William S. Marth President and Chief Executive Officer – Americas

 

11(c). Name(s) and position(s) of all shareholders holding at least 15% of shares

 

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

 

  1. Provide the applied-for gTLD string. If an IDN, provide the U-label.

TEVA

 

14A. If applying for an IDN, provide the A-label (beginning with "xn--").

 

 

14B. 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.

 

 

14C1. If an IDN, provide the language of the label (in English).

 

 

14C2. If an IDN, provide the language of the label (as referenced by ISO-639-1).

 

 

14D1. If an IDN, provide the script of the label (in English).

 

 

14D2. If an IDN, provide the script of the label (as referenced by ISO 15924).

 

 

14E. If an IDN, list all code points contained in the U-label according to Unicode form.

 

 

15A. If an IDN, upload IDN tables for the proposed registry.  An IDN table must include:

the applied-for gTLD string relevant to the tables,

the script or language designator (as defined in BCP 47),

table version number,

effective date (DD Month YYYY), and

contact name, email address, and phone number.

Submission of IDN tables in a standards-based format is encouraged.

 

 

15B. Describe the process used for development of the IDN tables submitted, including consultations and sources used.

 

 

15C. List any variants to the applied-for gTLD string according to the relevant IDN tables.

 

 

  1. 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.

 

As the applied-for gTLD string is not an IDN and is consistent with the requirements of the Applicant Guidebook Section 2.2.1.3.2 (String Requirements), Teva does not believe there are any known operational or rendering problems concerning the string. This answer is based upon consultation with Teva’s selected back-end provider, Neustar, which has successfully launched a number of new gTLDs over the last decade. In reaching this determination, Neustar analyzed the following data:

 -ICANN’s Security Stability Advisory Committee (SSAC) entitled Alternative TLD Name Systems and Roots: Conflict, Control and Consequences (SAC009);

-IAB - RFC3696 “Application Techniques for Checking and Transformation of Names”

-Known software issues which Neustar has encountered during the last decade launching new gTLDs;

-Character type and length;

-ICANN supplemental notes to Question 16; and

-ICANN’s presentation during its Costa Rica regional meeting on TLD Universal Acceptance.

 

  1. OPTIONAL.

Provide a representation of the label according to the International Phonetic Alphabet (http://www.langsci.ucl.ac.uk/ipa/).

 

 

18A. Describe the mission/purpose of your proposed gTLD.

 

The content of this Answer to Question 18 set forth below which describes the plans for Teva’s registry constitutes the “purpose” of the registry as that term is used in paragraph 1.b. of Specification 9 of the Draft New gTLD Registry Agreement found in Module 5 of the Teva Guidebook dated January 11, 2012 (“the Purpose”).  Teva will publish its Charter and its policies, guidelines, and other supporting documentation related to the implementation of the registry consistent with the Purpose, all prior to launch.  All second level domain names registered by Teva on behalf of itself or an affiliate will be registered through an ICANN-accredited registrar and will be consistent with the Purpose.

 

Teva Pharmaceutical Industries Limited (“Teva”) is among the top 15 pharmaceutical companies in the world and is the number one global generic pharmaceuticals leader.  Headquartered in Israel, we operate in 60 countries, distribute products to over 120 markets and have 47,000 employees worldwide, of whom 4,000 are Quality Assurance accredited.  

Teva was established in 1901 and our mission is to make quality healthcare accessible to more people around the world.  We take great pride in our long tradition of leadership and dedication to excellence and to the well-being of our employees, customers, community and environment.  Quality and safety are our number one priority and we act with integrity, ethical conduct and the highest standards of service.

We have the broadest product portfolio in the industry with over 1,300 molecules and specialize in the development, production and marketing of a wide range of generic and branded products, as well as active pharmaceutical ingredients (API).  

 

We are a member of the NASDAQ 100 and the TA-25 Index.  In 2010, our sales were $16billion, $4 billion in non-GAAP net income and we manufactured 63 billion tablets.   

 

We have employed a successful acquisitions and collaborations strategy which is guided by commercial, operational and structural considerations. Since 2008, we have successfully acquired and integrated eleven companies achieved through a unique set of guidelines and pre-defined milestones .  

 

Teva is the owner of the TEVA mark around the world.  By way of example, Teva is the owner of the mark TEVA, U.S. Reg. No. 1567918 having a registration date of November 28, 1989.  

The .Teva registry will be a standard, not a community-based, registry.  The .Teva registry will be a standard registry open only to Teva and our affiliates or in controlled circumstances to our business partners . For the avoidance of a doubt, the registry will be closed to registrants who do not have a formal, written trademark license agreement from Teva specifically allowing the registration of a second level domain name in the .Teva registry (the “Required License”).  The .Teva registry will not be a community-based registry and there will be no market for second level registrations outside of registrants which are affiliated with Teva and⁄or which have the Required License.  

Its Purpose will include:

  • To protect Teva’s intellectual property and ensure that the integrity of our brand is enhanced at the highest possible level in the domain name system.  We have a portfolio of registered intellectual property rights around the world and securing the term, .Teva, will enable us to harmonise our current brand protection policies

 

  • To provide a platform for the delivery of secure, consolidated digital material for pharma industry professionals and consumers alike

 

  • To ensure Teva remains at the forefront of innovation by keeping pace with internet technology developments

 

The success of the .Teva registry will be determined by the enhancement in the equity of the TEVA brand and in terms of the security and stability it brings to our communications.

 

18B. How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?

 

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.

 

18C. What operating rules will you adopt to eliminate or minimize social costs (e.g., time or financial resource costs, as well as various types of consumer vulnerabilities)? What other steps will you take to minimize negative consequences/costs imposed upon consumers?

 

 

As previously stated, the .Teva registry will be a standard registry closed to third parties for use only by pre-validated representatives of Teva or affiliates who have the Required License.  Social costs and negative consequences on customers are therefore likely to be minimised and possibly even eliminated because .Teva domains will not be made available to anyone outside Teva or to anyone not operating under a Required License.   In the unlikely event of an abuse of a .Teva domain name, the domain name will be revoked or reassigned in line with Teva’s corporate and strategic interests.

 

How will multiple applications for a particular domain be resolved, for example, by auction or on a first come first served basis?

 

There will be no market in .Teva domains. We are applying to protect and enhance Teva’s position as a leading pharma brand of the highest quality.  We will not receive multiple applications for a particular domain and therefore  there will be no need for any resolution.  We will control eligibility, which is limted to Teva, its affiliates, and those with the Required License, very strictly.

 

Explain any cost benefits for registrants you intend to implement (e.g. advantageous pricing, introductory discounts, bulk registration discounts).

 

Because all .Teva domain names will be registered to Teva Pharmaceutical Industries Limited, its wholly owned affiilates, or those operating under a Required License, there will be no market for .Teva domain names.  There will be no need to devise cost benefits for registrants because we will be the registrant.

 

The Registry Agreement requires that registrars be offered the option to obtain initial domain name registrations for periods of one to ten years at the discretion of the registrar, but no greater than 10 years. Additionally the Registry Agreement requires advance written notice of price increases. Do you intend to make contractual commitments to registrants regarding the magnitude of price escalation?

 

The Teva Domain Name Management Team will set the period of registration for .Teva domains. We are applying for .Teva to support our strategic goals and to protect our IP not to generate revenues from selling domains. Therefore it will not be necessary to make contractual commitments nor to consider issues around pricing including price escalation  though we will comply with the provisions of Section 2.10 of the Registry Agreement.

 

Before launching this TLD, Teva will develop and publish its policies and guidelines, setting out full details of how the registry will implement its vision and purpose as set out in this answer. Teva may adapt its policies and proposed use of the gTLD, in a manner consistent with the Purpose, to reflect changes in its business and the adoption of new gTLDs by the community.