Jump to content

.mail: 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  = International
|country  = International
Line 17: Line 17:
}}
}}


'''.mail''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]].  
'''.mail''' was a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]].  


==Applicants==
==Applicants==
Line 33: Line 33:
The warning states that the applicant is "seeking exclusive access to a common generic string .. that relates to a broad market sector," which Ms. Dryden notes could have unintended consequences and a negative impact on competition.<ref>[https://gacweb.icann.org/download/attachments/22938690/Mail-AU-50020.pdf?version=1&modificationDate=1353429319000 Mail AU, GACweb.ICANN.org] Retrieved 25 Nov 2012</ref>
The warning states that the applicant is "seeking exclusive access to a common generic string .. that relates to a broad market sector," which Ms. Dryden notes could have unintended consequences and a negative impact on competition.<ref>[https://gacweb.icann.org/download/attachments/22938690/Mail-AU-50020.pdf?version=1&modificationDate=1353429319000 Mail AU, GACweb.ICANN.org] Retrieved 25 Nov 2012</ref>


==Name Collision Issues==
==Name Collision Concerns and Cancellation==
In October 2013 [[ICANN]] released their final assessment and mitigation plan for the [[Name Collision]] issue that was facing the New gTLD program. On 18 November 2013, ICANN announced the applied-for strings that were eligible for an alternative path towards delegation that would allow applicants to proceed without waiting for further mitigation research and plans to be published. 25 strings, including .mail, were not eligible for the alternative path, and will have to wait for more plans to be published before continuing towards delegation.<ref>[https://newgtlds.icann.org/en/announcements-and-media/announcement-2-17nov13-en Announcement 17 Nov 13, ICANN.org] Retrieved 20 Feb 2014</ref>
[[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 .mail, [[.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 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==

Latest revision as of 18:05, 12 May 2021

Status: Cancelled
country: International
Type: Generic
Category: Technology
Priority #: 819 - Amazon
911 - Donuts (Victor Dale, LLC)
982 - GMO Registry
1075 - WhitePages TLD LLC
1787 - Google (Charleston Road Registry Inc.)

More information:

.mail was a proposed TLD in ICANN's New gTLD Program.

Applicants[edit | edit source]

  1. Amazon - The Universal Postal Union filed a Community Objection against this application.[1]
  2. Donuts (Victor Dale, LLC) - This applicant submitted a Public Interest Commitment, which can be downloaded here. The Universal Postal Union filed a Community Objection against this application.[2]
  3. GMO Registry
  4. Google (Charleston Road Registry Inc.) - The Universal Postal Union filed a Community Objection against this application.[3]
  5. WhitePages TLD LLC[4] The Universal Postal Union filed a Community Objection against this application, as did GMO Registry, Inc.[5]

Former Applicants[edit | edit source]

  1. 1&1 Mail & Media GmbH - This applicant submitted a Public Interest Commitment, which can be downloaded here. It was subsequently WITHDRAWN, however the Universal Postal Union still filed a Community Objection against this application.[6] It was the first applicant to leave the contention set.
  2. Afilias - The second applicant to leave the contention set; May 2013.[7]

GAC Early Warning[edit | edit source]

The applications from Amazon and 1&1 Mail & Media GmbH was issued a GAC Early Warning from the representative of Australia and GAC Chair, Heather Dryden. The warning system is noted as a strong recommendation on behalf of national governments to the ICANN Board that a given TLD application should be denied as it stands. Applicants are encouraged to work with objecting GAC members.[8]

The warning states that the applicant is "seeking exclusive access to a common generic string .. that relates to a broad market sector," which Ms. Dryden notes could have unintended consequences and a negative impact on competition.[9]

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 .mail, .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 three strings as "high risk" and proposed that none of the strings be delegated until it could be proven that risk is low.[10]

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.[11]

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.[11]

References[edit | edit source]