Changes

==A Stable Internet==

==A Stable Internet==

''Timeline of ICANN's changing definitions of Internet stability''<br/>

''Timeline of ICANN's changing definitions of Internet stability''<br/>

* '''1998:''' '''Stability is cast as the foremost fundamental principle of running ICANN and the DNS.'''

* '''1998:''' '''Stability (as security, reliability, and reliance on U.S.-based technical expertise) is cast as the foremost fundamental principle of running ICANN and the DNS.'''

:* 1/30/98: The Green Paper set out four principles to guide the evolution of the domain name system: stability, competition, private bottom-up coordination, and representation. “The Green Paper suggested that the new corporation be incorporated in the United States in order to promote stability and facilitate the continued reliance on technical expertise residing in the United States, including IANA staff at USC/ISI.” <ref>https://www.ntia.doc.gov/federal-register-notice/1998/statement-policy-management-internet-names-and-addresses</ref>

:* 1/30/98: The [[Green Paper]] set out four principles to guide the evolution of the domain name system: stability, competition, private bottom-up coordination, and representation. “The Green Paper suggested that the new corporation be incorporated in the United States in order to promote stability and facilitate the continued reliance on technical expertise residing in the United States, including IANA staff at USC/ISI.” <ref>https://www.ntia.doc.gov/federal-register-notice/1998/statement-policy-management-internet-names-and-addresses</ref>

:* 06/05/1998: the white paper: Stability: The U.S. Government should end its role in the Internet number and name address system in a manner that ensures the stability of the Internet. The introduction of a new management system should not disrupt current operations or create competing root systems. During the transition and thereafter, the stability of the Internet should be the first priority of any DNS management system. Security and reliability of the DNS are important aspects of stability, and as a new DNS management system is introduced, a comprehensive security strategy should be developed. https://cyber.harvard.edu/pressbriefings/icann/briefingbook/WhitePaper-Principles.html  

:* 06/05/1998: the [[White Paper]]: "Stability: The U.S. Government should end its role in the Internet number and name address system in a manner that ensures the stability of the Internet. The introduction of a new management system should not disrupt current operations or create competing root systems. During the transition and thereafter, the stability of the Internet should be the first priority of any DNS management system. Security and reliability of the DNS are important aspects of stability, and as a new DNS management system is introduced, a comprehensive security strategy should be developed. https://cyber.harvard.edu/pressbriefings/icann/briefingbook/WhitePaper-Principles.html  

* '''1999-2001:''' '''Performing stability is central to ICANN’s proof of concept TLDs'''

* '''1999-2001:''' '''Performing stability is central to ICANN’s proof of concept TLDs'''

:*ICANN imposed high threshold requirements new gTLD application consideration and allowed only a select few test cases to ensure that no new TLD registry would fail as that would threaten Internet (ICANN) stability.<ref>[https://arxiv.org/ftp/cs/papers/0109/0109099.pdf Jonathan Weinberg, "ICANN, 'Internet Stability,' and New Top Level Domains,' pg. 30]</ref>

:*ICANN imposed high threshold requirements new gTLD application consideration and allowed only a select few test cases to ensure that no new TLD registry would fail as that would threaten Internet (ICANN) stability.<ref>[https://arxiv.org/ftp/cs/papers/0109/0109099.pdf Jonathan Weinberg, "ICANN, 'Internet Stability,' and New Top Level Domains,' pg. 30]</ref>

::*[[Vint Cerf]], Chairman of ICANN before the House Committee on Energy and Commerce Subcommittee on Telecommunications and the Internet states, ICANN has “achieved [its] accomplishments by hewing to its first and guiding principle -- to maintain a stable, functional DNS -- and within those limits by seeking to increase competitive options and efficient dispute resolution.”<ref>[https://www.icann.org/resources/unthemed-pages/cerf-testimony-2001-02-08-en Cerf Testimony 02/08/01, ICANN]</ref>  

::*[[Vint Cerf]], Chairman of ICANN before the House Committee on Energy and Commerce Subcommittee on Telecommunications and the Internet states, ICANN has “achieved [its] accomplishments by hewing to its first and guiding principle -- to maintain a stable, functional DNS -- and within those limits by seeking to increase competitive options and efficient dispute resolution.”<ref>[https://www.icann.org/resources/unthemed-pages/cerf-testimony-2001-02-08-en Cerf Testimony 02/08/01, ICANN]</ref>  

* '''2002-2004:''' '''Stability as a Value'''  

* '''2002-2004:''' '''Stability as a Value'''  

:* “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>