Changes

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 [[Intranet]]s 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.<ref>[http://www.icann.org/en/help/name-collision Name Collision, ICANN.org] Retrieved 18 Feb 2014</ref>

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 [[Intranet]]s 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.<ref>[http://www.icann.org/en/help/name-collision Name Collision, ICANN.org] Retrieved 18 Feb 2014</ref>

==New gTLD Program==

==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]].  

Although the Name Collision issue is not new, a renewed interest in the issue came about in 2013 as [[ICANN]]'s [[New gTLD Program]] was preparing to delegate hundreds of New domain names to the [[Root]]. The topic was debated and fiercely within the ICANN community when a report by [[Interisle Consulting]] was prepared for and released by ICANN.

===Interisle Consulting Report===

===Interisle Consulting Report===

===Proposed Solutions===

===Proposed Solutions===

 

==Research==

==Research==