Jump to content

.corp: Difference between revisions

From ICANNWiki
No edit summary
JP (talk | contribs)
No edit summary
Line 1: Line 1:
{{TLD|
{{TLD|
|logo  =
|logo  =
|status = Proposed
|status = Cancelled
|manager  =
|manager  =
|country  =
|country  =
Line 16: Line 16:
|keypeople  =
|keypeople  =
}}
}}
'''.corp''' is a proposed new gTLD in [[ICANN]]'s [[New gTLD Program]].
'''.corp''' was a proposed new gTLD in [[ICANN]]'s [[New gTLD Program]].


==Applicants==
==Applicants==
Line 32: Line 32:
Jeff Bullock, the Secretary of State for Delaware, has raised concerns about new gTLD applications for [[.inc]], .corp, and [[.ltd]]. He believed that the applications do not adequately safeguard consumers, businesses, the public at large, state regulators, or the internet itself from the gTLDs being potentially used for fraudulent or misleading purposes.<ref>[http://domainincite.com/10553-delaware-secretary-of-state-opposes-any-corporate-themed-new-gtlds Delaware secretary of state opposes any corporate-themed new gTLDs]. Published 2012 September 21. Retrieved 2012 November 13.</ref> Delaware's lenient company laws make it the state US corporations are most registered in.
Jeff Bullock, the Secretary of State for Delaware, has raised concerns about new gTLD applications for [[.inc]], .corp, and [[.ltd]]. He believed that the applications do not adequately safeguard consumers, businesses, the public at large, state regulators, or the internet itself from the gTLDs being potentially used for fraudulent or misleading purposes.<ref>[http://domainincite.com/10553-delaware-secretary-of-state-opposes-any-corporate-themed-new-gtlds Delaware secretary of state opposes any corporate-themed new gTLDs]. Published 2012 September 21. Retrieved 2012 November 13.</ref> Delaware's lenient company laws make it the state US corporations are most registered in.


==Name Collision Concerns Impede Delegation==
==Name Collision Concerns and Cancellation==
[[ICANN]] hired firm [[Interisle Consulting]] to carry out an independent investigation on the issues that may arise from new gTLDs that are identical to TLDs being used on internal networks. The publishing of the report sparked a community-wide debate that later became known as the [[Name Collision]] issue. The firm reported at [[ICANN 47]] that [[.home]] and .corp gTLDs were cause for serious concern since those strings are widely in use by internal naming systems. In response to the report, [[ICANN]] labeled the .home and .corp strings as "high risk" and proposed that neither of the strings be delegated until it could be proven that risk is low.<ref>[http://domainincite.com/13994-new-gtlds-are-the-new-y2k-corp-and-home-are-doomed-and-everything-else-is-delayed New gTLDs are the New Y2K, Domain Incite] Retrieved 12 Sept 2013</ref> These two strings are currently severely delayed and some community members guess they may never be delegated.
[[ICANN]] hired firm [[Interisle Consulting]] to carry out an independent investigation on the issues that may arise from new gTLDs that are identical to TLDs being used on internal networks. The publishing of the report sparked a community-wide debate that later became known as the [[Name Collision]] issue. The firm reported at [[ICANN 47]] that the .corp, [[.home]], and [[.mail]] gTLDs were cause for serious concern since those strings are widely in use by internal naming systems. In response to the report, [[ICANN]] labeled the three strings as "high risk" and proposed that none of the strings be delegated until it could be proven that risk is low.<ref>[http://domainincite.com/13994-new-gtlds-are-the-new-y2k-corp-and-home-are-doomed-and-everything-else-is-delayed New gTLDs are the New Y2K, Domain Incite] Retrieved 12 Sept 2013</ref>  
 
In 2015, the IETF's DNS Operations committee began drafting an [[RFC]] with the intention of setting a standard of reserving .corp, .home, and .mail from general use, in deference to the exceedingly common use in intranets.<ref name="boardres">[https://www.icann.org/resources/board-material/resolutions-2018-02-04-en#2.c Board Resolution regarding .mail, .home, and .corp strings], Feb. 4, 2018</ref>
 
On February 4, 2018, the [[ICANN Board]] issued a resolution to cease processing of all applications for the three strings. Applicants were provided a full refund of their application fee.<ref name="boardres" />


==References==
==References==

Revision as of 18:03, 12 May 2021

Status: Cancelled
Type: Generic
Category: Commerce
Priority #: 348 - Dot Registry LLC
926 - STRAAT Investments (NU DOT CO LLC)
1014 - Donuts (Cotton Fields, LLC)
1393 - DotCorp Ltd.
1906 - Google (Charleston Road Registry Inc.)

More information:

.corp was a proposed new gTLD in ICANN's New gTLD Program.

Applicants[edit | edit source]

There are five applicants for the .corp TLD including: [1]

  1. DotCorp Ltd., a Hong Kong-based company that intends to offer .corp internationally.[2]
  2. Dot Registry LLC, an American company that is also applying for .inc, .llc, .llp. Dot Registry LLC intends to limit registration of their strings to only verifiable American companies that qualify for the respective designation; this initiative has already received some support from U.S. Secretaries of State. The company is using Neustar for their backend registry services.[3]
  3. STRAAT Investments, the parent company of .co Internet is applying for 13 domain name strings including .corp. [4]
  4. Donuts(Cotton Fields, LLC), a new registry company that filed for 307 new gTLD applications. Each gTLD application was submitted to ICANN under different company names. [5]This applicant submitted a Public Interest Commitment, which can be downloaded here.
  5. Google (Charleston Road Registry Inc.), applied for 101 TLDs. Sarah Falvey, Senior Policy Analyst of Google is the main contact person in the application. [6]

Former Applicants[edit | edit source]

  1. PROC Registry, LLC, Joshua Bourne, Managing Partner of FairWinds Partners is the main contact person in the application. This application was WITHDRAWN.

Objections[edit | edit source]

Jeff Bullock, the Secretary of State for Delaware, has raised concerns about new gTLD applications for .inc, .corp, and .ltd. He believed that the applications do not adequately safeguard consumers, businesses, the public at large, state regulators, or the internet itself from the gTLDs being potentially used for fraudulent or misleading purposes.[7] Delaware's lenient company laws make it the state US corporations are most registered in.

Name Collision Concerns and Cancellation[edit | edit source]

ICANN hired firm Interisle Consulting to carry out an independent investigation on the issues that may arise from new gTLDs that are identical to TLDs being used on internal networks. The publishing of the report sparked a community-wide debate that later became known as the Name Collision issue. The firm reported at ICANN 47 that the .corp, .home, and .mail gTLDs were cause for serious concern since those strings are widely in use by internal naming systems. In response to the report, ICANN labeled the three strings as "high risk" and proposed that none of the strings be delegated until it could be proven that risk is low.[8]

In 2015, the IETF's DNS Operations committee began drafting an RFC with the intention of setting a standard of reserving .corp, .home, and .mail from general use, in deference to the exceedingly common use in intranets.[9]

On February 4, 2018, the ICANN Board issued a resolution to cease processing of all applications for the three strings. Applicants were provided a full refund of their application fee.[9]

References[edit | edit source]