Changes

==Implementation==

==Implementation==

The implementation of ccTLDs was started by [[IANA]]. The delegation and creation of ccTLDs is presented within [[RFC 1951]]. In order to determine whether new ccTLDs should be added or not, the IANA follows the provisions of [[ISO 3166]] - Maintenance Agency. More information related to the development of new ccTLDs can be found in [http://www.iana.org/procedures/cctld-establishment.html IANA's Procedures for Establishing ccTLDs]. <ref>[http://www.iana.org/domains/root/cctld/ IANA ccTLD]</ref>

The implementation of ccTLDs was started by [[IANA]]. The delegation and creation of ccTLDs is presented within RFC 1951. In order to determine whether new ccTLDs should be added or not, the IANA follows the provisions of ISO 3166 - Maintenance Agency. More information related to the development of new ccTLDs can be found in [http://www.iana.org/procedures/cctld-establishment.html IANA's Procedures for Establishing ccTLDs]. <ref>[http://www.iana.org/domains/root/cctld/ IANA ccTLD]</ref>

===IANA's Procedures for ccTLDs===

===IANA's Procedures for ccTLDs===

==Delegation and Redelegation==

==Delegation and Redelegation==

The process through which the designated manager, or managers, is changed is know as ''redelegation''. The process follows the provisions of [[ICP-1]] and [[RFC 1591]]. [[IANA]] receives all requests of a sponsoring organization related to delegation and redelegation for the ccTLDs. The requests are then analyzed by [[IANA]] based on various technical and public criterion, and finally sent to the [[ICANN Board|ICANN Board of Directors]] for approval or refusal. If approved, [[IANA]] is also responsible for the implementation of the request.<ref>[http://www.iana.org/domains/root/delegation-guide/ Delegation and Redelegation Guide]</ref>

The process through which the designated manager, or managers, is changed is know as ''redelegation''. The process follows the provisions of ICP-1 and RFC 1591. [[IANA]] receives all requests of a sponsoring organization related to delegation and redelegation for the ccTLDs. The requests are then analyzed by [[IANA]] based on various technical and public criterion, and finally sent to the [[ICANN Board|ICANN Board of Directors]] for approval or refusal. If approved, IANA is also responsible for the implementation of the request.<ref>[http://www.iana.org/domains/root/delegation-guide/ Delegation and Redelegation Guide]</ref>

Conceptually speaking, the delegation and redelegation processes are simple, but can easily become complex if there are many organizations and individuals involved in the process. There is a set of steps which must be followed before sending the request for delegation or redelegation. An initial request should be developed based on ''The Change Request Template'' and supplementary information to prove that the eligibility criteria has been met by the initial request. All the information supplied is used by [[IANA]] to fortify the request received.

Conceptually speaking, the delegation and redelegation processes are simple, but can easily become complex if there are many organizations and individuals involved in the process. There is a set of steps that must be followed before sending the request for delegation or redelegation. An initial request should be developed based on ''The Change Request Template'' and supplementary information to prove that the eligibility criteria has been met by the initial request. All the information supplied is used by IANA to fortify the request received.<ref>[http://www.iana.org/domains/root/delegation-guide/ Delegation and Redelegation Guide]</ref>

==ccTLDs and ICANN==  

==ccTLDs and ICANN==  

The policies developed by [[ICANN]] are implemented by [[gTLD]] [[registry]] operators, ccTLD managers, root-nameserver operators and regional Internet registries. One of the main activities of [[ICANN]] is to work with other organizations involved in the technical coordination of the Internet with the purpose of formally documenting their participatory role within the [[ICANN]] process. These organizations are committed to the [[ICANN]] policies that result from their work.<ref>[http://www.icann.org/en/cctlds/ ICANN ccTLDs]</ref>

The policies developed by [[ICANN]] are implemented by [[gTLD]] [[registry]] operators, ccTLD managers, root-nameserver operators and regional Internet registries. One of the main activities of [[ICANN]] is to work with other organizations involved in the technical coordination of the Internet with the purpose of formally documenting their participatory role within the [[ICANN]] process. These organizations are committed to the [[ICANN]] policies that result from their work.

Starting in 2000, [[ICANN]] started cooperating with ccTLD managers to document their relationship. Due to various circumstances such as: the type of organization, cultural issues, economics, the legal environment, etc., the relationships between [[ICANN]] and ccTLD mangers are often complex. Another consideration is the role of the national government in "managing or establishing policy for their own ccTLD" (role recognized in the June 1998, U.S. Government [[White Paper]]).

Starting in 2000, [[ICANN]] started cooperating with ccTLD managers to document their relationship. Due to various circumstances such as: the type of organization, cultural issues, economics, the legal environment, etc., the relationships between [[ICANN]] and ccTLD mangers are often complex. Another consideration is the role of the national government in "managing or establishing policy for their own ccTLD" (role recognized in the June 1998, U.S. Government [[White Paper]]).<ref>[http://www.icann.org/en/cctlds/ ICANN ccTLDs]</ref>

In 2009, [[ICANN]] began the implementation of an [[IDN]] ccTLD Fast Track Process,<ref>[http://www.idnnews.com/?p=9433 IDN News]</ref> whereby countries that use non-Latin script are able to claim ccTLDs in their native script and the corresponding Latin version. As of early 2011, 33 requests have been received, representing 22 languages.<ref>[http://www.icann.org/en/topics/idn/fast-track/ ICANN]</ref> More than half have already been approved.<ref>[http://www.ausregistry.com/blog/?p=342 AUSRegistry]</ref>

In 2009, [[ICANN]] began the implementation of an [[IDN]] ccTLD Fast Track Process,<ref>[http://www.idnnews.com/?p=9433 IDN News]</ref> whereby countries that use non-Latin script are able to claim ccTLDs in their native script and the corresponding Latin version. As of early 2011, 33 requests have been received, representing 22 languages.<ref>[http://www.icann.org/en/topics/idn/fast-track/ ICANN]</ref> More than half have already been approved.<ref>[http://www.ausregistry.com/blog/?p=342 AUSRegistry]</ref>

==Open ccTLDs==

==Open ccTLDs==

An '''open ccTLD''' refers to a country code top level domain name that can be registered by anyone, regardless of which country the person resides in. These ccTLDs generally  represent a particular branding aside from the name of the country or territory it represents. Examples include [[.cc]] (Cocos Island) for consulting companies, [[.tv]] (Tuvalu) for television, [[.ws]] (Western Samoa) for websites, and [[.co]] (Colombia) as an alternative to [[.com]] for companies.<ref>[http://cyber.law.harvard.edu/archived_content/people/edelman/open-cctlds/ Registrations in Open ccTLDs]</ref>

An '''open ccTLD''' refers to a country code top level domain name that can be registered by anyone, regardless of which country the person resides in. These ccTLDs generally  represent a particular branding aside from the name of the country or territory it represents. Examples include [[.cc]] (Cocos Island) for consulting companies, [[.tv]] (Tuvalu) for television, [[.ws]] (Western Samoa) for websites, and [[.co]] (Colombia) as an alternative to [[.com]] for companies.<ref>[http://cyber.law.harvard.edu/archived_content/people/edelman/open-cctlds/ Registrations in Open ccTLDs]</ref>

===.cc and .tv===

===.cc and .tv===