Jump to content

.protection: Difference between revisions

From ICANNWiki
Vivian (talk | contribs)
No edit summary
No edit summary
Line 6: Line 6:
|language =
|language =
|translation =
|translation =
|registryprovider  =
|registryprovider  =[[Verisign]]
|registrations  =
|registrations  =
|date  =
|date  =
Line 17: Line 17:


'''.protection''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[Symantec Corporation]].<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref>
'''.protection''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[Symantec Corporation]].<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref>
==Application Details==
The following is excerpted from the applicant's response to question #18:


"18.1 Mission and Purpose of .PROTECTION
Symantec Corporation (“Symantec”) is a leading global provider of information security and protection, serving the needs of consumers around the world, with more than 18,500 employees and operations in numerous countries. Symantec’s products are available for purchase online to consumers and Symantec’s online content is accessible in the .COM gTLD and in multiple ccTLDs, including .CA, .DE, .EU, and .RU. Symantec is applying for four generic-term gTLDs: .PROTECTION and .SECURITY, which correspond with Symantec’s core competencies, and .CLOUD and .ANTIVIRUS, which correspond to Symantec’s products.
The intended future mission and purpose of the .PROTECTION gTLD is to serve as a trusted, hierarchical, secure, and intuitive namespace provided by Symantec for its consumers. Symantec is committed to moving forward with a .PROTECTION gTLD application; however at the time of filing this application, there has not been enough time, and currently there is not enough market information available, to fully analyze and evaluate all potential use case options.
Symantec will be analyzing and evaluating other gTLD applications as well as general market adoption to determine short- and long-term potential best-in-class use case options to most effectively serve and enhance Symantec’s online strategy as a leading provider of information security and protection. As a company, Symantec’s unique focus is to eliminate risks to information, technology, and processes independent of the device, platform, interaction, or location. Symantec helps individuals, small and medium-sized businesses, and global organizations ensure that their information, technology infrastructures, and related processes are protected and easily managed. Symantec delivers solutions that allow customers to access information when they need it and make it available to all of those who should have access to it. The .PROTECTION gTLD will be in line with the company’s current focus by providing a trusted, hierarchical, secure, and intuitive namespace.
Protection and security are at the core of Symantec’s offerings, and will continue to remain at that core into the future. Symantec will always be in the business of providing protection and security to its consumers. Symantec aims to protect completely; with Symantec, customers can protect more of their information and technology infrastructure, in greater depth, wherever that information is stored or used. Therefore, the .PROTECTION gTLD will become one of Symantec’s core assets. The .PROTECTION gTLD is intended to enhance Symantec’s online presence and identity; expand its marketing and promotion efforts; provide a secure channel for online products and services; and offer a platform through which to consolidate many of the intellectual property activities of Symantec.
Symantec intends to initially limit registration and use of domain names within the .PROTECTION gTLD to Symantec and its qualified subsidiaries and affiliates. This initial limited use will allow Symantec to establish its operations and achieve full sustainability. This limited distribution coupled with the other requirements set forth in Specification 9 of the template Registry Agreement is intended to exempt Symantec from its annual Code of Conduct Compliance requirements."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1573 gTLDresult.ICANN.org] Retrieved 18 Feb 2013</ref>
==References==
==References==
{{reflist}}
{{reflist}}

Revision as of 01:31, 19 February 2013

Status: Proposed
Registry Provider: Verisign
Type: Generic
Category: Technology
Priority #: 590 - Symantec Corporation

More information:

.protection is a proposed TLD in ICANN's New gTLD Program. The applicant is Symantec Corporation.[1]

Application Details

The following is excerpted from the applicant's response to question #18:

"18.1 Mission and Purpose of .PROTECTION

Symantec Corporation (“Symantec”) is a leading global provider of information security and protection, serving the needs of consumers around the world, with more than 18,500 employees and operations in numerous countries. Symantec’s products are available for purchase online to consumers and Symantec’s online content is accessible in the .COM gTLD and in multiple ccTLDs, including .CA, .DE, .EU, and .RU. Symantec is applying for four generic-term gTLDs: .PROTECTION and .SECURITY, which correspond with Symantec’s core competencies, and .CLOUD and .ANTIVIRUS, which correspond to Symantec’s products.

The intended future mission and purpose of the .PROTECTION gTLD is to serve as a trusted, hierarchical, secure, and intuitive namespace provided by Symantec for its consumers. Symantec is committed to moving forward with a .PROTECTION gTLD application; however at the time of filing this application, there has not been enough time, and currently there is not enough market information available, to fully analyze and evaluate all potential use case options.

Symantec will be analyzing and evaluating other gTLD applications as well as general market adoption to determine short- and long-term potential best-in-class use case options to most effectively serve and enhance Symantec’s online strategy as a leading provider of information security and protection. As a company, Symantec’s unique focus is to eliminate risks to information, technology, and processes independent of the device, platform, interaction, or location. Symantec helps individuals, small and medium-sized businesses, and global organizations ensure that their information, technology infrastructures, and related processes are protected and easily managed. Symantec delivers solutions that allow customers to access information when they need it and make it available to all of those who should have access to it. The .PROTECTION gTLD will be in line with the company’s current focus by providing a trusted, hierarchical, secure, and intuitive namespace.

Protection and security are at the core of Symantec’s offerings, and will continue to remain at that core into the future. Symantec will always be in the business of providing protection and security to its consumers. Symantec aims to protect completely; with Symantec, customers can protect more of their information and technology infrastructure, in greater depth, wherever that information is stored or used. Therefore, the .PROTECTION gTLD will become one of Symantec’s core assets. The .PROTECTION gTLD is intended to enhance Symantec’s online presence and identity; expand its marketing and promotion efforts; provide a secure channel for online products and services; and offer a platform through which to consolidate many of the intellectual property activities of Symantec.

Symantec intends to initially limit registration and use of domain names within the .PROTECTION gTLD to Symantec and its qualified subsidiaries and affiliates. This initial limited use will allow Symantec to establish its operations and achieve full sustainability. This limited distribution coupled with the other requirements set forth in Specification 9 of the template Registry Agreement is intended to exempt Symantec from its annual Code of Conduct Compliance requirements."[2]

References