1. Text #ICANN51

2. Text #ICANN51 Potential GNSO Policy Work on gTLD Name Collision Mitigation 12 October 2014 Francisco Arias Director, Technical Services Global Domains Division

3. Text #ICANN51 Introduction & Background

4. Text Name Collision Basics Private network configured in such a way that could “leak” the request to the public Domain Name System, when using a name in a private network that does not exist in the public DNS User tries to access a service on a private network when connected to the Internet outside of that network. company.example.example does not exist www.company.example

5. Text Name Collision Basics Private network configured in such a way that could “leak” the request to the public Domain Name System, when using a name in a private network matching a name in the public DNS User tries to access a service on a private network when connected to the Internet outside of that network. company.example.example exists www.company.example

6. Text #ICANN51 Background 7 October 2013: NGPC adopted the New gTLD Collision Occurrence Management plan 30 July 2014: ICANN NGPC approved the New gTLD Name Collision Occurrence Framework

7. Text #ICANN51 30 July NGPC Resolution 1. Adopts the Framework and directs its implementation 2. Directs undertaking a consultation re: RPM requirements for SLDs in block list, recorded in the TMCH, that were withheld from allocation during Sunrise or Claims 3. Consider policy work within GNSO re: long-term plan to manage name collisions 4. Share information and best practices with ccTLDs

8. Text #ICANN51 Potential GNSO Policy Work

9. Text #ICANN51 Limitations of Current Mitigations Measures Current work is focus only on 2012-round gTLDs Most measures cease two years after delegation No measures for gTLDs delegated before the 2012 round JAS report recommended to explore “domain drop catching” and the associated data feeds that may be leveraged by attackers when attempting to exploit collisions

10. Text #ICANN51 Questions for GNSO Council to Consider (1/3) What measures, if any, should be taken to manage the name collision risks for: o future rounds of new gTLDs? o 2012-round gTLDs beyond their 2-year anniversary of delegation? o gTLDs delegated before the 2012 round?

11. Text #ICANN51 Questions for GNSO Council to Consider (2/3) Should there be any safeguards regarding the practice of "domain drop catching" and similar services in gTLDs? Is any further data needed on the effectiveness of the current mitigation measures or other aspects of name collision before policy development could start?

12. Text #ICANN51 Questions for GNSO Council to Consider (3/3) If there is policy work, should SSAC be invited to provide its advice given the nature of the issues? Is policy development the best approach to develop such measures and/or safeguards, or are there other methods by which this work could be undertaken?

13. Text #ICANN51 Questions & Answers

14. Text Engage with ICANN on Web & Social Media twitter.com/icann facebook.com/icannorg linkedin.com/company/icann gplus.to/icann weibo.com/icannorg flickr.com/photos/icann icann.org youtube.com/user/ICANNnews