According to a resolution of the ICANN Board the .Mail has joined .Home and .Corp as extension that will not be delegated as part of the collision report.

.Mail was basically killed off as part of the “ICANN NAME COLLISION OCCURRENCE MANAGEMENT FRAMEWORK” which is putting into place a plan which will start the process of freeing up domain names on the Collision list:

“Registry Operators will implement a period of, at least, 90 days of continuous controlled interruption. ICANN will monitor and time the implementation of the measure, primarily using the zone files that are transferred to ICANN from new gTLD registries once they are delegated (per Specification 4 of the new gTLD Registry Agreement).”

For new gTLDs that are delegated on a day to be specified by ICANN (“the cutoff date”) and later, the Registry Operator will implement controlled interruption for 90 days by inserting the following records in its TLD zone file (substituting “” with its respective TLD):

. 3600 IN MX 10 your-dns-needs-immediate-attention..
* 3600 IN MX 10 your-dns-needs-immediate-attention..
. 3600 IN SRV 10 10 0 your-dns-needs-immediate-attention..
* 3600 IN SRV 10 10 0 your-dns-needs-immediate-attention..
. 3600 IN TXT “Your DNS configuration needs immediate attention see https://icann.org/namecollision”
* 3600 IN TXT “Your DNS configuration needs immediate attention see https://icann.org/namecollision”
. 3600 IN A 127.0.53.53
* 3600 IN A 127.0.53.53

During this period, ICANN hereby extends a temporary waiver to the Registry Operator with respect to Section 2.2 of Specification 6 of the new gTLD Registry Agreement (e.g., to allow the use of wildcard records). ICANN also extends a temporary waiver to the Registry Operator with respect to Section 1 of Exhibit A of the new gTLD Registry Agreement (e.g., to allow the use of TXT, SRV, and MX records). The waivers are only for purposes of implementing the controlled interruption measure and will cease upon termination of the controlled interruption measure in the TLD.

Registry Operator is permitted to delegate the second level domain name “nic” during the controlled interruption period. Per the new gTLD registry agreement, Registry Operator is expected, among other things, to offer RDDS services at “whois.nic.“, where “” is the registry’s TLD. During this period Registry Operator will not activate any other names under the TLD.

Registry Operators for TLDs that have been delegated prior to “the cutoff day” may implement this option only if they have not activated names under the TLD with the exception of “nic”.

Interested Registry Operators that meet these criteria must notify and obtain ICANN consent through the GDD portal before implementing the measure.

3.2. RELEASING NAMES IN THE SLD BLOCK LIST

For new gTLDs that have been delegated prior to “the cutoff day” and have activated names under the TLD other than “nic”, the Registry Operator will implement controlled interruption for 90 days by inserting A, MX, TXT and SRV records for each of the names in its SLD block list that it wishes to release from its SLD Block List. Registry Operator will insert the following records in its TLD zone file for each label in the List of SLDs to Block (substituting “” with its respective TLD and “” appropriately):

.. 3600 IN A 127.0.53.53
.. 3600 IN SRV 10 10 0 your-dns-needs-immediate-attention..
.. 3600 IN MX 10 your-dns-needs-immediate-attention..
.. 3600 IN TXT “Your DNS configuration needs immediate attention see https://icann.org/namecollision”
your-dns-needs-immediate-attention.. 3600 IN A 127.0.53.53

ICANN extends a temporary waiver to the Registry Operator with respect to Section 1 of Exhibit A of the new gTLD Registry Agreement (e.g., to allow the use of SRV, TXT, and MX records). The waivers are only for purposes of implementing the controlled interruption measure and will cease upon termination of the controlled interruption measure in the TLD.

ICANN will limit emergency response for name collision reports to situations where there is a reasonable belief that the name collision presents a clear and present danger to human life.

In the unlikely case that a newly delegated gTLD creates a clear and present danger to human life as a result of colliding use as a dotless name, ICANN would work with the registry operator and ICANN’s root zone management partners to reverse the new delegation. This would only happen during the 90-day wildcarded controlled interruption, during which there would be no names active (except “nic”) under the TLD. Once the harm is mitigated, the gTLD registry operator may request again delegation.

ICANN has scheduled two Webinars on the Name Collision Occurrence Management Framework

Webinar Details

Session 1
Date/Time: 11 August 2014, 1:00 – 2:30 UTC
Adobe Connect: https://icann.adobeconnect.com/gdd
Dial-in Numbers: Download Now [PDF, 70 KB]

Session 2
Date/Time: 12 August 2014, 15:00 – 16:30 UTC
Adobe Connect: https://icann.adobeconnect.com/gdd
Dial-in Numbers: Download Now [PDF, 86 KB]