RE: [council] From the Meeting of the New gTLD Program Committee on 30 July 2014: Name Collision Occurrence Management Framework

["Jonathan Robinson" <jrobinson@xxxxxxxxxxxx>]

Thanks Bruce,

Clearly there is an issue for us or at least potentially for us i.e.

Resolved (2014.07.30.NG03), the NGPC directs the President and CEO, or his
designee(s) to provide information to, and work with the GNSO to consider
whether policy work on developing a long-term plan to manage gTLD name
collision issues should be undertaken.


Jonathan

-----Original Message-----
From: Bruce Tonkin [mailto:Bruce.Tonkin@xxxxxxxxxxxxxxxxxx] 
Sent: 02 August 2014 23:52
To: council@xxxxxxxxxxxxxx
Subject: [council] From the Meeting of the New gTLD Program Committee on 30
July 2014: Name Collision Occurrence Management Framework

From:
https://www.icann.org/resources/board-material/resolutions-new-gtld-2014-07-
30-en#1.a

Name Collision Occurrence Management Framework

Whereas, on 7 October 2013 the NGPC directed the President, Global Domains
Division to implement the proposal to manage the occurrence of collisions
between new gTLDs and existing private uses of the same strings as presented
in the "New gTLD Collision Occurrence Management Plan" (the "Collision
Occurrence Management Plan"), and in doing so to take into account further
advice that may be offered by Security and Stability Advisory Committee
(SSAC) and other experts and stakeholders.

Whereas, the Collision Occurrence Management Plan called for a follow-up
study that would inform the development of a Name Collision Occurrence
Management Framework.

Whereas, on 26 February 2014, ICANN published the follow-up study called for
in the NGPC's 7 October 2013 resolution, which was prepared by JAS Global
Advisors (JAS) and entitled "Mitigating the Risk of DNS Namespace
Collisions: A Study on Namespace Collisions in the Global Internet DNS
Namespace and a Framework for Risk Mitigation, Phase One Report"
[https://www.icann.org/en/system/files/files/name-collision-mitigation-26feb
14-en.pdf ] (the "JAS Study and Name Collision Framework"). The JAS Study
and Name Collision Framework, which was posted for public comment, provided
a set of recommendations that describe a comprehensive framework to reduce
current and future DNS namespace collisions, alert operators of potential
DNS namespace related issues, and provide emergency response capabilities in
the event that critical (e.g., life safety) systems are adversely impacted.
The JAS Study and Name Collision Framework was revised
[https://www.icann.org/en/system/files/files/name-collision-mitigation-study
-06jun14-en.pdf ] in response to public comments.

Whereas, on 6 June 2014, the ICANN Security and Stability Advisory Committee
(SSAC) published SAC 066
[https://www.icann.org/en/system/files/files/sac-066-en.pdf ]: SSAC Comment
Concerning JAS Phase One Report on Mitigating the Risk of DNS Namespace
Collisions, in which it offered advice and recommendations to the Board on
the framework presented in the JAS Study and Name Collision Framework.

Whereas, the proposed name collision framework being presented to the NGPC
for consideration takes into account advice offered by SSAC in SAC066, and
the advice of other experts and stakeholders, including the recommendations
from JAS, public comments, and community discussions at ICANN meetings.

Whereas, the NGPC acknowledges comments from the community concerning the
need to ensure that all names, which registries blocked under their
Alternate Path to Delegation Report, be subject to the rights protection
mechanisms established by the New gTLD Program.

Whereas, the ICANN Board previously adopted the NGPC's recommendation to
direct the ICANN President and CEO to develop a long-term plan to management
name collision at the root.

Whereas, the NGPC is undertaking this action pursuant to the authority
granted to it by the Board on 10 April 2012, to exercise the ICANN Board's
authority for any and all issues that may arise relating to the New gTLD
Program.

Resolved (2014.07.30.NG01), the NGPC adopts the Name Collision Occurrence
Management Framework
<https://www.icann.org/en/system/files/files/name-collision-framework-30jul1
4-en.pdf> [see attached] to continue to manage the occurrence of collisions
between new gTLDs and existing private uses of the same strings, and directs
the President and CEO, or his designee(s), to take the necessary actions to
implement the Name Collision Occurrence Management Framework. 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.

Resolved (2014.07.30.NG02), the NGPC directs the President and CEO, or his
designee(s), to consult with the community during the next 90 days from the
publication of these resolutions to address appropriate rights protection
mechanisms for names included in a registry operator's Alternate Path to
Delegation Report and recorded in the Trademark Clearinghouse that registry
operator withheld from allocation during its Sunrise period or Claims
period.

Resolved (2014.07.30.NG03), the NGPC directs the President and CEO, or his
designee(s) to provide information to, and work with the GNSO to consider
whether policy work on developing a long-term plan to manage gTLD name
collision issues should be undertaken.

Resolved (2014.07.30.NG04), the NGPC directs the President and CEO, or his
designee(s), to continue to provide briefings and share information and best
practices with ccTLD managers concerning name collision issues in light of
the Name Collision Occurrence Management Framework.