NAME COLLISION OCCURRENCE ASSESSMENT
4 August 2014
RE: .[TLD] Name Collision Occurrence Management
Dear Applicant/Registry Operator:
In accordance with Section 6.2 of Specification 6 of the Registry Agreement (“Registry Agreement”), and as contemplated by the ICANN New gTLD Collision Occurrence Management plan and established by the Name Collision Occurrence Management Framework (adopted by the ICANN Board New gTLD Program Committee on 30 July 2014 and available at https://www.icann.org/resources/board-material/resolutions-new-gtld-2014-07-30-en), please identify below the appropriate Name Collision Occurrence Assessment measures to be implemented for the top-level domain identified above (the “TLD”):
I. TLD DELEGATED ON OR AFTER 18 AUGUST 2014
Any TLD delegated on or after 18 August 2014 (00:00 UTC) must implement the following measures:
A. Wildcarded Controlled Interruption. For a period of at least 90 days, the registry must implement continuous controlled interruption inserting the following records into the TLD zone file (substituting "<TLD>" with the respective TLD):
<TLD>. 3600 IN MX 10 your-dns-needs-immediate-attention.<TLD>.
* 3600 IN MX 10 your-dns-needs-immediate-attention.<TLD>.
<TLD>. 3600 IN SRV 10 10 0 your-dns-needs-immediate-attention.<TLD>.
* 3600 IN SRV 10 10 0 your-dns-needs-immediate-attention.<TLD>.
<TLD>. 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"
<TLD>. 3600 IN A 127.0.53.53
* 3600 IN A 127.0.53.53
ICANN will monitor and time the implementation of the measure, primarily using the zone files that are transferred to ICANN from the registry upon delegation (per Specification 4 of the Registry Agreement).
Per the Registry Agreement, Registry Operator is required, among other things, to offer RDDS services at "whois.nic.<TLD>" (where "<TLD>" is the respective TLD). Registry Operator must delegate the second level domain name "nic" during the controlled interruption period. The Registry Operator must not activate any other names under the TLD until after the 90-day controlled interruption period has been completed.
B. Temporary Waiver. During this period, Registry Operator is afforded a temporary waiver as to the provisions of: (1) Section 2.2 of Specification 6 (e.g., to allow the use of wildcard records); and (2) Section 1 of Exhibit A (e.g., to allow the use of A, TXT, SRV, and MX records in the zone apex). The waivers are only for purposes of implementing the controlled interruption measure and will immediately cease upon termination of the controlled interruption measure in the TLD.
II. TLD DELEGATED PRIOR TO 18 AUGUST 2014 and ACTIVATED NAMES
Any TLD delegated prior to 18 August 2014 (00:00 UTC) that has activated names (other than “nic”) must implement the following measures:
A. Controlled Interruption. For any names the registry wishes to release from its SLD Block List (as provided in its Alternative Path to Delegation), for a period of at least 90 days the registry must first implement controlled interruption by inserting A, MX, TXT and SRV records for each of the names on its SLD block list. Specifically, the registry must insert the following records in the TLD zone file for each label on the List of SLDs to Block (substituting "<TLD>" with its respective TLD and "<label>" appropriately):
<label>.<TLD>. 3600 IN A 127.0.53.53
<label>.<TLD>. 3600 IN SRV 10 10 0 your-dns-needs-immediate-attention.<TLD>.
<label>.<TLD>. 3600 IN MX 10 your-dns-needs-immediate-attention.<TLD>.
<label>.<TLD>. 3600 IN TXT "Your DNS configuration needs immediate attention see https://icann.org/namecollision"
your-dns-needs-immediate-attention.<TLD>. 3600 IN A 127.0.53.53
B. Temporary Waiver. During this period, Registry Operator is afforded a temporary waiver with respect to the provisions of Section 1 of Exhibit A of the Registry Agreement (e.g., to allow the use of SRV, TXT, and MX records for names on the List of SLDs to Block). The waiver is only for purposes of implementing the controlled interruption measure and will cease upon termination of the controlled interruption measure.
C. Rights Protection Mechanisms. The registry must ensure that names desired to be activated from its SLD Block List after the 90-day controlled interruption period have been subject to applicable Rights Protection Mechanisms as required under Specification 7 of the Registry Agreement, including, for example:
i. For names included on the block list of the registry’s Alternate Path to Delegation Report and recorded in the Trademark Clearinghouse that the registry withheld from allocation during its Sunrise Period or Claims Period, the registry must continue to withhold the names from allocation while ICANN consults with the community about concerns expressed regarding appropriate rights protection mechanisms for this category of names. As appropriate, the registry will be provided an updated Name Collision Occurrence Assessment with details about how to activate these names after the period of community consultation.
ii. For names included on the block list of the registry’s Alternate Path to Delegation Report and recorded in the Trademark Clearinghouse that the registry allocated or made available for allocation during its Sunrise Period and Claims Period, the registry may activate the names after implementing the 90 days of Controlled Interruption required of its TLD as specified in Section II (A) above.
iii. For names included on the block list of the registry’s Alternate Path to Delegation Report and recorded in the Trademark Clearinghouse that the registry allocated or made available for allocation during its Sunrise Period, but withheld from allocation during its Claims Period, the registry may activate the names after implementing the 90 days of Controlled Interruption required of its TLD as specified in Section II (A) above, provided that the registry provides Claims Services for the applicable names for at least 90 calendar days.
III. TLD DELEGATED PRIOR TO 18 AUGUST 2014 and NO ACTIVATED NAMES
Any TLD delegated before 18 August 2014 (00:00 UTC) that has not activated names (other than “nic”) must implement the measures set forth in either Section I or Section II of this Assessment (i.e., must select one or the other only to complete). If names other than “nic” have been activated, the Registry Operator must implement the measures set forth in Section II of this Name Collision Occurrence Assessment for the TLD.
For the avoidance of doubt, Registry Operators are no longer eligible for the Alternate Path to Delegation, and, as required by Section 6.1 of Specification 6, must now only activate names in the DNS zone strictly as outlined above based on the circumstances specific to the TLD. The controlled interruption measures outlined in this Name Collision Occurrence Assessment must not be implemented by any registry prior to 12:00 UTC on 18 August 2014.
Additionally, with respect to name collision report handling as described in Section 6.3 of Specification 6 of the Registry Agreement, all Registry Operators must act on all requests from ICANN (e.g., place a domain name in serverHold status, remove wildcard records from DNS, etc.) within 2 hours of receipt for the first two years of the TLD’s life, which begins at the date of delegation. Registry Operator further agrees that ICANN may designate an interim emergency back-end registry operator for its TLD in case the Registry Operator is unable or unwilling to comply with a measure to avoid harm from name collision in a timely manner as described above.
Except as specifically set forth in this Name Collision Occurrence Assessment, the terms and conditions of the Registry Agreement shall remain in full force and binding effect. For additional information regarding the requirements a registry must implement as part of this Name Collision Occurrence Assessment, please reference the Name Collision Occurrence Framework, which may be found at
https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf.
Regards,
Akram Atallah
President, Global Domains Division
ICANN