The Collision Occurrence Management Plan directs staff to undertake an additional study to develop a name collision occurrence management framework. The framework will include appropriate parameters and processes to assess both probability and severity of harm resulting from the occurrence of name collisions. Examples of the parameters might include number of DNS requests, type of DNS requests, type of queries, diversity of query source and appearances in internal name certificates. The framework will specify a set of collision occurrence assessments and corresponding mitigation measures, if any, that ICANN or TLD applicants may need to implement per second level domain name (SLD) seen in the "day in the life of the Internet" (DITL) dataset.

　　Additionally, the plan provides a registry operator with the option to proceed to delegation prior to receiving its SLD collision occurrence assessment report (subject to established processes and procedures). If the registry operator chooses this alternative path to delegation, it must initially block all SLDs that appear in the DITL dataset while the assessment is conducted.

　　At its 7 October meeting, the NGPC also recommended to the ICANN Board that the issue of name collisions be monitored by the Board's Risk Committee and reviewed periodically, and that ICANN work with the community in developing a long-term plan to retain and measure root-server data.