Country code top-level domain: Difference between revisions

+Template:Articles needing attention
mNo edit summary
Line 7: Line 7:


===IANA's Procedures for ccTLDs===
===IANA's Procedures for ccTLDs===
Within its database, [[IANA]] contains authoritative information related to ccTLDs, referring to sponsoring organizations, technical and administrative contacts, name servers, registration [[URL]]s and other such information. This type of information provides extra details regarding the [[IANA]]'s procedures for maintaining the ccTLD database.
Within its database, [[IANA]] maintains authoritative information related to ccTLDs.  This includes sponsoring organizations, technical and administrative contacts, name servers, registration [[URL]]s and other such information. This type of information provides extra details regarding the [[IANA]]'s procedures for maintaining the ccTLD database.


==Delegation and Redelegation==
==Delegation and Redelegation==
The process through which the designated manager, or managers, is changed is known as ''redelegation''. The latter 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 name="guide">[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 known as ''redelegation''. The redelegation 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.  The request, accompanied by the IANA analysis, is 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 name="guide">[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 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 name="guide">[http://www.iana.org/domains/root/delegation-guide/ Delegation and Redelegation Guide]</ref>
Conceptually speaking, the delegation and redelegation processes are simple.  However, they 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 have been met by the initial request. All the information supplied is used by IANA to analyze the request received.<ref name="guide">[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.
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]]).<ref>[https://www.icann.org/resources/unthemed-pages/white-paper-2012-02-25-en White Paper, 2/25/2012, ICANN Resources]</ref>
In 2000, [[ICANN]] started cooperating with ccTLD managers to document their relationship. The relationships between [[ICANN]] and ccTLD mangers are often complex.  Complexities arise due to various circumstances, including the type of organization, cultural issues, economics, the legal environment, etc. 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>[https://www.icann.org/resources/unthemed-pages/white-paper-2012-02-25-en White Paper, 2/25/2012, ICANN Resources]</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>