.AZURE New gTLD Application

Click to view Chinese translation articles.

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

New gTLD Application Submitted to ICANN by: Microsoft Corporation

String: AZURE

Originally Posted: 13 June 2012

Application ID: 1-1129-27259

 

Applicant Information

 

  1. Full legal name

Microsoft Corporation

 

  1. Address of the principal place of business

One Microsoft Way

Redmond WA 98052-7329

US

 

  1. Phone number

+1 425 882 8080

 

  1. Fax number

+1 425 706 7329

 

  1. If applicable, website or URL

http:⁄⁄www.microsoft.com

 

Primary Contact

 

6(a). Name

Ms. Cynthia Ruth Kern

 

6(b). Title

Business Manager

 

6(c). Address

 

6(d). Phone Number

+1 425 703 7472

 

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

Ms. Lorna Jean Gradden

 

7(b). Title

Director

 

7(c). Address

 

7(d). Phone Number

+44 207 421 8263

 

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

Corporation

 

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

USA, State of Washington

 

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;MSFT

 

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

Microsoft Corporation, the applying entity, is the parent company and not a subsidiary

 

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

Microsoft Corporation, the applying entity, is not a joint venture

 

Applicant Background

 

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

Charles H. Noski Director

David F. Marquardt Director

Dina Dublon Director

Helmut G. W. Panke Director

John W. Thompson Director

Maria M. Klawe Director

Raymond V. Gilmartin Director

Steven A. Ballmer Chief Executive Officer

  1. Reed Hastings Director

William H. Gates III Chairman

 

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

  1. Kevin Turner Chief Operating Officer

Bradford L. Smith Senior Vice President, General Counsel and Secretary

Craig J. Mundie Chief Research and Strategy Officer

Kurt D. DelBene President, Microsoft Office Division

Lisa E. Brummel Senior Vice President, Human Resources

Peter S. Klein Chief Financial Officer

Satya Nadella President, Server & Tools

Steven A. Ballmer Chief Executive Officer

Steven J. Sinofsky President, Windows & Windows Live Division

 

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.

AZURE

 

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.

 

  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), Microsoft Corporation does not believe there are any known operational or rendering problems concerning the string.

 

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

The mission of Microsoft Corporation is to transform the way people work, play and communicate throughout the world through the provision of software, services and hardware.  Microsoft does business throughout the world,  offices in more than 100 countries and over 90,000 employees.  Every day, billions of consumers and businesses work, play, and communicate using Microsoft software, services, and hardware.

 

Windows Azure is the name given to Microsoftʹs family of cloud services, which includes a scalable operating system with compute, storage, hosting and management capabilities, a relational database, and a platform that helps developers quickly and easily create applications running in the cloud.  

 

Our family of Windows Azure cloud services offers customers in over 40 countries the opportunity to use Microsoft and Microsoft partner solutions in ways never before possible.  Resellers, such as HP, Dell, Fujitsu and eBay, offer cloud services based on our Windows Azure platform.

 

The missions of the .azure registry are to lay the groundwork for providing consumers and businesses who interact with Microsoft through the .azure registry with a more secure and authentic experience, to protect the Windows Azure brand, and to promote the family of Windows Azure cloud services.  

 

We are assessing the opportunities that a new gTLD has for the delivery of secure communications, products, and services.

 

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

We expect that customers and users of our Windows Azure family of cloud services will benefit if the .azure gTLD registry allows us to lay the groundwork for a more secure, globally recognized platform to complement our on-going efforts to enhance the security, stability, and reliability of our family of Windows Azure cloud services.  We believe that the opportunity to provide our customers and users with an increased sense of security and authenticity for their interactions with Windows Azure cloud services may increase their confidence in and use of these services.  We hope that an .azure gTLD will help us deliver a more secure, stable and reliable family of cloud services.

 

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

 

The goals of the proposed .azure gTLD are to lay the groundwork for providing customers and users who interact with Microsoft through the .azure gTLD with an increased sense of security and authenticity, to protect the Windows Azure brand and to promote the family of Windows Azure cloud services.  Because the .azure gTLD is the logical, short gTLD counterpart to our Windows Azure brand, the importance of maintaining and strengthening this brand dictates that we operate the .azure registry to the highest service levels.

 

We anticipate that operation of the .azure gTLD has the potential to provide us with the opportunity to use the gTLD as a globally recognized and more secure platform to give customers and users choice and flexibility and an easy-to-use interface through which we can continue to provide our innovative family of Windows Azure cloud services.  

 

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

 

Our proposed .azure gTLD will add differentiation to the current space because it will be the only gTLD that may provide customers who interact with Microsoft through the .azure gTLD with an increased sense of security and authenticity, to protect the well-known Windows Azure brand, and to promote the family of Windows Azure cloud services.  We anticipate that the opportunity to operate an .azure gTLD may provide an authentic and secure platform through which we can continue our commitment to innovation.

 

  1. What is the goal of your proposed gTLD in terms of user experience?

 

The goals of the .azure gTLD are to lay the groundwork for providing users who interact with Microsoft through the .azure gTLD with an increased sense of security and authenticity for using the family of Windows Azure cloud services, to protect the Windows Azure brand, and to promote the family of Windows Azure cloud services.  

 

  1. Provide a complete description of the applicants intended registration policies in support of the goals above.

 

The Microsoft Domain Name Management team is responsible for the development, maintenance and enforcement of the .azure Domain Management Policy (aDMP). The aDMP defines the rules for eligibility and domain name allocation, sets out the terms governing the use of an .azure domain name, and describes the dispute resolution policies for the .azure TLD.  We intend to update and revise the aDMP as appropriate to reflect Microsoft’s commercial and strategic interests as well as ICANN Consensus Policy and Temporary Policy developments.  We summarize below the aDMP.

 

Registration of an .azure domain name is a four-step process: Eligibility Confirmation, Naming Convention Check, Acceptable Use Review, and Registration.

 

Registration of an .azure domain name will be restricted to Microsoft Corporation and its wholly owned subsidiaries.  

 

All domains in the .azure registry will be registered to Microsoft Corporation or one of its wholly owned subsidiaries.

 

Checks will be performed to ensure that each applied-for domain name satisfies the .azure Naming Conventions. Each .azure domain name must:

  • not be a prohibited label such as “example”;
  • 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; and
  • not match any protected country or territory name identified in the internationally recognized lists set forth in Specification 5 to the New gTLD Agreement, unless Microsoft reaches agreement regarding release of such names with the applicable government or pursuant to a proposal reviewed by the ICANN Governmental Advisory Committee and approved by ICANN.

 

The .azure registry may support Internationalized domain names (IDN) at the second level.  

 

.azure domain names must be used solely for purposes that, in Microsoft’s sole discretion and judgment, enhance its strategic or commercial interests.  .azure domains shall not be used to knowingly infringe, violate, or misappropriate the intellectual property rights of any third party.

 

Registrants may not assign any rights in .azure domains to any third party.

 

Microsoft will require that the WHOIS data for all .azure domains is accurate and current.  

 

  1. Will your proposed gTLD impose any measures for protecting the privacy of confidential information of registrants or users?

 

Microsoft is committed to protecting the privacy of employee and customer data.

 

The .azure registry will be operated by the Microsoft Corporation, a corporation organized under the laws of the State of Washington; data will be processed in accordance with applicable data protection requirements.  We intend to comply with the Personal Data obligations set forth in Section 2.10 of the Registry Agreement.

 

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

 

We anticipate engaging in the types and scope of outreach and communications appropriate to the operation of a .brand registry in which the brand owner and its wholly owned subsidiaries are the registrants of all second-level domain names.

 

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

We believe that the operation of a gTLD registry that is the logical counterpart to one of our key brands, the registration of all .azure domain names in the name of Microsoft Corporation or its wholly owned subsidiaries, and the use of those domains in accordance with our requirements will serve to eliminate or minimize social costs and negative consequences⁄costs imposed on consumers.   

 

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

 

We anticipate that domains in the .azure registry will only be registered to Microsoft Corporation or its wholly owned subsidiaries.  We do not anticipate receiving multiple applications for a particular domain and, accordingly, believe that there will be no need for any resolution.

 

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

 

Because all .azure domain names will be registered to Microsoft Corporation or its wholly owned subsidiaries, there will be no cost benefits for registrants.  

 

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

 

We do not intend to make contractual commitments to registrants regarding the magnitude of price escalation because the universe of registrants will be limited to Microsoft Corporation and its wholly owned subsidiaries.  We intend to comply with the provisions of Section 2.10 of the Registry Agreement.