Changes

: “Users can accumulate equity in a particular identifier, which becomes closely associated with them and expensive to change. Changing a telephone number or e-mail address that has been used for many years can be burdensome because of the large number of personal contacts and records that contain the number. Thus, equity in an identifier raises switching costs for consumers, making them more likely to stay with the provider of that identifier.” <ref>[https://www.nap.edu/read/11258/chapter/4#62 Signposts in Cyberspace: The Domain Name System and Internet Navigation, pg. 62]</ref>

: “Users can accumulate equity in a particular identifier, which becomes closely associated with them and expensive to change. Changing a telephone number or e-mail address that has been used for many years can be burdensome because of the large number of personal contacts and records that contain the number. Thus, equity in an identifier raises switching costs for consumers, making them more likely to stay with the provider of that identifier.” <ref>[https://www.nap.edu/read/11258/chapter/4#62 Signposts in Cyberspace: The Domain Name System and Internet Navigation, pg. 62]</ref>

* '''2008-2012''': '''Emphasis on maintaining technical stability in the lead up to the New gTLD Program'''

* '''2008-2012''': '''Emphasis on maintaining technical stability in the lead up to the New gTLD Program'''

:* 02/06/2008: ICANN Staff and SSAC consider the possibility of instability in executing the GNSO’s recommendation to add new gTLDs. "Conformity to existing standards and syntax rules will be a requirement for any new TLD," including RFC 952 (“DOD Internet Host Table Specification); liberalized by RFC 1123; RFC 2181 (label number limit); and RFC 3696: labels must consist of only the ASCII [ASCII] alphabetic and numeric characters, plus the hyphen. ICANN also expected to disallow any TLDs containing only numeric characters and allow hyphens in both the third and fourth positions of a label only in a valid Punycode string, where the currently approved IDNA prefix (currently xn) is used.<ref>[http://gnso.icann.org/issues/new-gtlds/final-report-rn-wg-23may07.htm New gTLDs WG Final Report May 2007, GNSO, ICANN]</ref>

:* 02/06/2008: ICANN Staff and SSAC consider the possibility of instability in executing the GNSO’s recommendation to add new gTLDs.  

::*"Conformity to existing standards and syntax rules will be a requirement for any new TLD," including RFC 952 (“DOD Internet Host Table Specification); liberalized by RFC 1123; RFC 2181 (label number limit); and RFC 3696: labels must consist of only the ASCII [ASCII] alphabetic and numeric characters, plus the hyphen. ICANN also expected to disallow any TLDs containing only numeric characters and allow hyphens in both the third and fourth positions of a label only in a valid Punycode string, where the currently approved IDNA prefix (currently xn) is used.<ref>[http://gnso.icann.org/issues/new-gtlds/final-report-rn-wg-23may07.htm New gTLDs WG Final Report May 2007, GNSO, ICANN]</ref>

::* ICANN was concerned that commonly-used file extensions as TLDs in the root might result in users or applications confusing URLs with filenames. SSAC explored the issue and reported that such collisions would result in user confusion but would not break the DNS

::* ICANN was concerned that commonly-used file extensions as TLDs in the root might result in users or applications confusing URLs with filenames. SSAC explored the issue and reported that such collisions would result in user confusion but would not break the DNS

::* the DNS should be able to function at its current level with at least 60 million TLDs. This allows significant room for large-scale expansion without concerns about a negative effect on stability.<ref>[https://archive.icann.org/en/topics/dns-stability-draft-paper-06feb08.pdf DNS Stability, 2008, ICANN Archives]</ref>  

::* the DNS should be able to function at its current level with at least 60 million TLDs. This allows significant room for large-scale expansion without concerns about a negative effect on stability.<ref>[https://archive.icann.org/en/topics/dns-stability-draft-paper-06feb08.pdf DNS Stability, 2008, ICANN Archives]</ref>