Name Collision: Difference between revisions
Appearance
mNo edit summary |
|||
Line 12: | Line 12: | ||
===Reception by New gTLD Applicants=== | ===Reception by New gTLD Applicants=== | ||
==Alternative Path to Delegation | ==Alternative Path to Delegation== | ||
==Research== | ==Research== |
Revision as of 00:33, 4 February 2014
Currently building this page.
A Name Collision is a term used to describe the circumstance in which a term is used to try and reach a private Domain Name that results in resolving to a public Domain Name unintentionally. Private domain names are used in Intranets and in many corporations and organizations throughout the world. A domain name on a private network that matches a name in the public Internet can create security risks in which private information is obtained or private networks are hacked.
History
New gTLD Program
A renewed interest in the name collision issue came about as ICANN's New gTLD Program was preparing to delegate hundreds of New domain names to the Root.
Interisle Consulting Report
Reception by New gTLD Applicants
Alternative Path to Delegation
Research
- ANA and verisign
- Name Collisions
- Collisions summit
- .club solution
- responses
- Australian Bank
- announcement
- looking at it wrong way?
- Neustar analysis
- Resolution
- Domain Incite response to resolution from ICANN
- Domain Name wire response
- Blocked Trademarks still Eligible for Donuts Sunrises
References