ICANN New gTLD Application

New gTLD Application Submitted to ICANN by: MiTek USA, Inc.

String: CONNECTORS

Originally Posted: 13 June 2012

Application ID: 1-1085-40392


Applicant Information


1. Full legal name

MiTek USA, Inc.

2. Address of the principal place of business

14515 N Outer 40 Rd
Ste 300
Chesterfield MO 63017
US

3. Phone number

3144341200

4. Fax number

3148517965

5. If applicable, website or URL

http:⁄⁄www.mii.com

Primary Contact


6(a). Name

Mr. Michael Paul

6(b). Title

Vice President of Corporate Information Technology

6(c). Address


6(d). Phone Number

3148517469

6(e). Fax Number

3148517869

6(f). Email Address

mpaul@mii.com

Secondary Contact


7(a). Name

Mr. Stan Gaston

7(b). Title

Senior Network Administrator

7(c). Address


7(d). Phone Number

3148517382

7(e). Fax Number


7(f). Email Address

sgaston@mii.com

Proof of Legal Establishment


8(a). Legal form of the Applicant

Corporation

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

Please review the attached. I have additional documentation support the recent name change to MiTek USA, Inc., but I was unable to attach them all.

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


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

Richard MarriottPresident
Thomas ManentiCEO

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

MiTek HoldingsNot 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


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

CONNECTORS

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.


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

TLD will not be resold. Purchased for brand protection only.

17. (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.

TLD will not be resold. Purchased for brand protection only.

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

TLD will not be resold. Purchased for brand protection only.

18(c). What operating rules will you adopt to eliminate or minimize social costs?

TLD will not be resold. Purchased for brand protection only.

Community-based Designation


19. Is the application for a community-based TLD?

No

20(a). Provide the name and full description of the community that the applicant is committing to serve.


20(b). Explain the applicant's relationship to the community identified in 20(a).


20(c). Provide a description of the community-based purpose of the applied-for gTLD.


20(d). Explain the relationship between the applied-for gTLD string and the community identified in 20(a).


20(e). Provide a description of the applicant's intended registration policies in support of the community-based purpose of the applied-for gTLD.


20(f). Attach any written endorsements from institutions/groups representative of the community identified in 20(a).

Attachments are not displayed on this form.

Geographic Names


21(a). Is the application for a geographic name?

No

Protection of Geographic Names


22. Describe proposed measures for protection of geographic names at the second and other levels in the applied-for gTLD.

TLD will not be resold. Purchased for brand protection only.

Registry Services


23. Provide name and full description of all the Registry Services to be provided.

TLD will not be resold. Purchased for brand protection only.

Demonstration of Technical & Operational Capability


24. Shared Registration System (SRS) Performance

TLD will not be resold. Purchased for brand protection only.

25. Extensible Provisioning Protocol (EPP)

TLD will not be resold. Purchased for brand protection only.

26. Whois

TLD will not be resold. Purchased for brand protection only.

27. Registration Life Cycle

TLD will not be resold. Purchased for brand protection only.

28. Abuse Prevention and Mitigation

TLD will not be resold. Purchased for brand protection only.

29. Rights Protection Mechanisms

TLD will not be resold. Purchased for brand protection only.

30(a). Security Policy: Summary of the security policy for the proposed registry

TLD will not be resold. Purchased for brand protection only.



© Internet Corporation For Assigned Names and Numbers.