Begin forwarded message:

> From: David Olive <[log in to unmask]>
> Subject: [Soac-infoalert] NGPC Resolution for Addressing the Consequences of Name Collisions | ICANN
> Date: October 14, 2013 9:49:14 AM PDT
> To: "[log in to unmask]" <[log in to unmask]>
> 
> http://www.icann.org/en/news/announcements/announcement-08oct13-en.htm
> 
> 8 October 2013
> At its 18 May 2013 meeting, the ICANN Board adopted a resolution to commission a study to identify the levels of potential impact posed by each applied-for new gTLD on the use of TLDs that are not currently delegated at the root level of the public DNS.
> The study, "Name Collision in the DNS," together with a proposal to manage the risks identified in the study, was published for public comment from 5 August 2013 to 17 September 2013. During the public comment period, 75 comments were received. Based on the public comments, staff updated the proposal to manage the risks identified in the study. The report of these public comments is available at: http://forum.icann.org/lists/comments-name-collision-05aug13/.
> The ICANN Board New gTLD Program Committee (NGPC) met on 28 September 2013 to review and discuss a proposal on how to deal with name collisions. On 7 October 2013, the NGPC met again and approved an updated proposal, titled "New gTLD Collision Occurrence Management Plan," [PDF, 840 KB] to mitigate the risks of potential name collisions caused by the introduction of new gTLDs.
> 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.
> An additional feature of the plan requires establishment of a process by each TLD operator to enable an affected party(ies) to report and request the blocking of an SLD that causes demonstrably severe harm as a consequence of name collision occurrences. This process is intended to mitigate the risk that collision occurrences from additional SLDs not observed in the study dataset could have severe impact.
> The plan also includes an outreach campaign targeted to potentially affected parties to help them identify and manage the origins (causes) of name collision occurrences in their networks. As part of the outreach campaign, ICANN, under the direction of the President and CEO, will invite and collaborate with relevant parties and members of the community that share the same interest in making progress in this issue.
> 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.
> For more information about the NGPC, please visit: http://www.icann.org/en/groups/board/new-gtld.
> 
> 
> --
> David A. Olive
> Vice President, Policy Development Support
> Internet Corporation for Assigned Names and Numbers (ICANN)
> General Manager, ICANN Regional Headquarters -Istanbul
> Hakki Yeten Cad. Selenium Plaza No:10/C K:5&6
> 34349 Fulya, Besiktas, Istanbul, Turkey 
> Tel: +90.212.381.8727
> Fax: +90.212.381.8731 
> Mobile: +1. 202.341.3611
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> soac-infoalert mailing list
> [log in to unmask]
> https://mm.icann.org/mailman/listinfo/soac-infoalert




--Apple-Mail=_F5D943AA-AE9D-4888-A5F4-980985F09781
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJSXDd6AAoJEHyDX9QJnOXdwXIH/03K9rsRVlWYDWly4/PLf4S0
Zr/+H/OYnkiNZ+yfRRxRkL9WxhRX7ITHc3nU9wKGkEHcFnsiNhJcq3Tg8WeVJx8E
hcpMm9Zrp5tn422AM6JCdk/lLsuoI5nDLb1Ix3iMwKI0Kkozun85fVAZXIs+xo9w
T4Zv6ntuQeiJddyf6ZHhfLVLZKYXhKe2ROwGzvLN2uWeOUSJ9Js8Pt4G2ttL8szC
CutACCSS89ZoZUL50AG7+QRLVXTRVnDCRlz+6hR5/oXAwPH5V1Cr4KejxWTNHl1z
e0oyr07jOT0I69x9Rx8BqTXEfmo2D5GWQ6B5dJhUgw0nMfTPLBQ5nM/FDBZYS5s=
=zd9A
-----END PGP SIGNATURE-----

--Apple-Mail=_F5D943AA-AE9D-4888-A5F4-980985F09781--