19
edits
Changes
Jump to navigation
Jump to search
Line 73:
Line 73: + + + + + + + + + + +
added info for controlled interruption period
The final draft of the report, "Mitigating the Risk of DNS Namespace Collisions Phase One", was published on June 10th. Important changes that were made because of a Public Comment Period for the document include a change of the Controlled Interruption Zone period from 120 to 90 days.<ref>[https://www.icann.org/en/system/files/files/name-collision-mitigation-study-06jun14-en.pdf Name Collision Mitigation Study Phase One] (6 June 2014) JAS Advisors ''ICANN.org'; Retrieved 11 June 2014 (PDF)</ref>
The final draft of the report, "Mitigating the Risk of DNS Namespace Collisions Phase One", was published on June 10th. Important changes that were made because of a Public Comment Period for the document include a change of the Controlled Interruption Zone period from 120 to 90 days.<ref>[https://www.icann.org/en/system/files/files/name-collision-mitigation-study-06jun14-en.pdf Name Collision Mitigation Study Phase One] (6 June 2014) JAS Advisors ''ICANN.org'; Retrieved 11 June 2014 (PDF)</ref>
==Name Collision Occurrence Management Framework==
On July 30, 2014, the New gTLD Program Committee (NGPC) approved resolutions<ref>[https://www.icann.org/resources/board-material/resolutions-new-gtld-2014-07-30-en Approved Resolutions | Meeting of the New gTLD Program Committee] Retrieved 29 September 2014</ref> for the Name Collision Occurrence Management Framework<ref>[https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf Name Collision Occurrence Management Framework] (PDF, 634 KB) Retrieved 29 September 2014</ref> to continue to manage the occurrence of collisions between new gTLDs and existing private uses of the same strings. As part of implementation, registry operators will be provided with a Name Collision Occurrence Assessment (see Registry Agreement, Specification 6, Section 6), which will address, among other things, procedures to remove second level domains from the block list including measures to protect rights holders.
The announcement highlighted two general requirements for registries<ref>[https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf Name Collision Occurrence Management Framework] (PDF, 634 KB) Retrieved 29 September 2014</ref>:
* Required to act on name collision reports from ICANN within two hours of the report during the first two years of the life of the TLD measured from the time of delegation of the TLD.
* Required to implement "controlled interruption" as the notification measure to alert parties that they may be leaking queries intended from private namespaces to the public DNS. Controlled interruption is required to be continuous interruption (i.e. not intermittent), and lasting for a 90-day period. Generally, if a TLD was delegated prior to a defined cut-off date, the registry operator would implement controlled interruption using MX, SRV, TXT, and A records for second level domains included in the block list. For TLDs delegated after a defined cut-off date, the registry operator would implement controlled interruption using a wildcard method. Controlled interruption (for IPv4) will use a loopback address (127.0.53.53). The 'cutoff date' is 18 August 2014.<ref>[https://www.icann.org/resources/pages/name-collision-ro-faqs-2014-08-01-en Frequently Asked Questions: Name Collision Occurrence Management Framework for Registries] Retrieved 29 September 2014</ref>
For additional details, refer to the ICANN website, Name Collision Resources & Information at [http://icann.org/namecollision icann.org/namecollision].
==References==
==References==