Difference between revisions of ".security"

From ICANNWiki
Jump to navigation Jump to search
Line 21: Line 21:
 
==Applicants==
 
==Applicants==
 
# [[Defender Security Company]]
 
# [[Defender Security Company]]
# [[Donuts]] (Fern Trail, LLC)
+
# [[Donuts]] (Fern Trail, LLC) This applicant submitted a [[PIC|Public Interest Commitment]], which can be downloaded [https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/593 here].
 
# [[Symantec Corporation]]<ref>[http://gtldresult.icann.org/application-result/applicationstatus/viewstatus Security Status, ICANN.org]</ref>
 
# [[Symantec Corporation]]<ref>[http://gtldresult.icann.org/application-result/applicationstatus/viewstatus Security Status, ICANN.org]</ref>
  

Revision as of 19:12, 13 March 2013

Status: Proposed
country: International
Registry: XYZ.COM LLC
Registry Backend: CentralNic
Type: Generic
Category: Commerce
Priority #: 728 - Symantec Corporation
1139 - Defender Security Company
1600 - Donuts (Fern Trail, LLC)

More information: NTLDStatsLogo.png

.security is a proposed TLD in ICANN's New gTLD Program.

Applicants

  1. Defender Security Company
  2. Donuts (Fern Trail, LLC) This applicant submitted a Public Interest Commitment, which can be downloaded here.
  3. Symantec Corporation[1]

European Commission Communiqué

The European Commission flagged all applications for .security outside of ICANN's defined remediation processes.

Just after ICANN's GAC issued its Early Warnings, which are advice given from one GAC member country to an applicant warning it of potential issues within its application, the European Commission issued a letter to all applicants within the new gTLD program. The letter highlights 58 applications that "could raise issues of compatibility with the existing legislation .. and/or with policy positions and objectives of the European Union." It notes a desire to open a dialogue with each offending applicant.

The Commission specifically notes that this objection is not a part of the GAC Early Warning process, and goes on to note that "the Commission does not consider itself legally bound to [ICANN] processes," given that there is not legal agreement between the two bodies.[2][3]

References