|
|
(36 intermediate revisions by 11 users not shown) |
Line 1: |
Line 1: |
| | {{Template:Articles needing attention}} |
| | |
| A '''Country Code Top-Level Domain''' ('''ccTLD''') is a two-letter Internet top-level domains ([[TLD]]s) specifically designated for a particular country, sovereign state or autonomous territory for use to service their community. ccTLDs are derived from [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 ISO 3166-1 alpha-2] country codes.<ref>[http://www.icann.org/en/cctlds/ ICANN ccTLDs]</ref> | | A '''Country Code Top-Level Domain''' ('''ccTLD''') is a two-letter Internet top-level domains ([[TLD]]s) specifically designated for a particular country, sovereign state or autonomous territory for use to service their community. ccTLDs are derived from [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 ISO 3166-1 alpha-2] country codes.<ref>[http://www.icann.org/en/cctlds/ ICANN ccTLDs]</ref> |
|
| |
|
| ==Implementation== | | ==Implementation== |
| The implementation of ccTLDs was started by [[IANA]]. The delegation and creation of ccTLDs is presented within [https://www.ietf.org/rfc/rfc1591.txt RFC 1591]. 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]], which is not a physical organization or an individual but it is part of [[ICANN]].<ref>[https://www.nominus.com/en/dm/blog/country-domains/january-2022/what-are-country-code-top-level-domains-and-why-do-they-matter Who created ccTLDs?]</ref> The delegation and creation of ccTLDs is presented within [https://www.ietf.org/rfc/rfc1591.txt RFC 1591]. In order to determine whether new ccTLDs should be added or not, the IANA follows the provisions of ISO 3166 - Maintenance Agency. Briefly, "our policy is to create new country-code top-level domains when the country or territory is listed on the ISO 3166-1 standard." |
| | |
| | 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=== |
| 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 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 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> | | The process through which the designated manager, or managers, is changed is known as ''redelegation''. The redelegation process follows the provisions of [https://archive.icann.org/en/policies/icp-1-archived.htm 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. 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.
| |
|
| |
|
| 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>
| | 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. |
|
| |
|
| 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 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> |
|
| |
|
| ==Open ccTLDs==
| | 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> |
| 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 opportunity 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=== | | ==Pseudo-ccTLD== |
| [[Verisign]] is the registry operator of both .cc and .tv open ccTLDs. [[eNIC]], a subsidiary company of Verisign, manages the operation and marketing of .cc. The company promotes the ccTLD as a good alternative for the .com and .net domain name spaces. The target users for the .cc include entities that who want to develop website representing a Chinese company, country club, consulting company, chat community, church community, community center, chamber of commerce, or community college.<ref>[http://www.verisigninc.com/en_US/products-and-services/domain-name-services/registry-services/cc-domain-names/index.xhtml .CC Domain Names - Unique Names for Niche Markets]</ref>
| |
|
| |
|
| [[TodayISP.com]], one of the registrars offering .cc, describes the ccTLD as a new international domain name having the same features of the [[.com]] and [[.net]], as it is understood by users as an acronym for commercial company, it offers potential business value, and is becoming the latest fashion in domain names, making its value increase.<ref>[http://www.todayisp.com/domain/intro_cc.net What Is .CC Domain?]</ref>
| | A pseudo-ccTLD mimics an official country code domain without formal recognition, often used for branding or to suggest geographical affiliation. |
|
| |
|
| The .tv ccTLD is currently operated by [[dotTV]], another subsidiary company of Verisign. Domain names using the .tv ccTLD are registered by entities involved in the television, film, and animation industries, as well as individuals providing video contents in their blogs or websites.<ref>[http://watch.tv/about-tv/index.html About .tv]</ref> Internet users understand that a .tv domain name offers video content. In 2006, [[Demand Media]] and Verisign partnered to promote the .tv TLD as a preferred web address for media rich content. [[Richard Rosenblatt]], Chairman and CEO of Demand Media, explained that the landscape of Internet media is changing quickly, and many users want to publish and share their own video materials. According to Rosenblatt, "By registering a .tv domain name and adding video content of their choosing, users can program their own channel."<ref>[http://www.webhosting.info/news/1/verisign-and-demand-media--to-promote-.tv-domain-names-_1214066304.htm VeriSign and Demand Media to Promote .tv Domain Names]</ref>
| | ==Open ccTLDs== |
|
| |
|
| ===.co===
| | ''Related Article - [[Open Use ccTLD]]''<br> |
| The Colombian Ministry of Information Technology and Communication assigned the management of the .co ccTLD registry to the [[.co Internet|.CO Internet SAS]], a joint venture between [[Arcelandia SA]] and [[Neustar]], Inc. Since its launch in February 2010, the .co ccTLD has been marketed by .co Internet as a "new, flexible, and safe global extension" for internet users worldwide.<ref>[http://www.cointernet.co/sites/default/files/documents/World-Trademark-Review-Update-.co-extension-is-launched.pdf '.co' extension is launched]</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 opportunity 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> |
|
| |
|
| According to [[Juan Diego Calle]], CEO of .co Internet, the [[.co]] TLD will serve as a good alternative for users who are looking for a credible, global and recognizable domain name that is affordable and critical to achieving their online success. He explained that .co is well-known worldwide by Internet users as a short term for corporation or company, and the .co domain name space will provide millions of users the opportunity register their desired domain names to establish their online presence. Calle said that his company is targeting Internet users around the world who have dreams, ideas or contents to share.<ref>[http://www.thedomains.com/2010/05/16/everything-you-ever-wanted-to-know-about-co-our-exclusive-interview-with-the-ceo-juan-calle/ Everything You Ever Wanted To Know About .CO; Our Exclusive Interview With The CEO Juan Calle]</ref>
| | ==Current ccTLDs== |
| | |
| .CO Internet SAS is promoting the .co TLD as an easy to remember top level domain representing companies, corporations, communities, content, etc. and searchable, secure, committed, confident, flexible, networked with a growing community.<ref>[http://www.cointernet.co/domain About .co]</ref> <ref>[http://www.opportunity.co/about/#/benefits Benefits of .Co]</ref>
| |
| | |
| Some companies use the .co domain space as a branded shortener or in [[Domain Hack|domain hacks]], such as with [[Overstock.com]] (O.co), [[Twitter]] (T.co), Politico (politi.co), Venture Hacks (vh.co), [[Google]] (g.co), etc.<ref> [http://www.cointernet.co/domain/many-uses Many uses of .co]</ref> Others use it as a [[URL]] shortener, such as [[GoDaddy]]'s x.co.<ref>[http://app.x.co/ URL Shortener]</ref>
| |
|
| |
|
| ===.fm and .am===
| |
| The [[.fm]] and [[.am]] ccTLDs are marketed by [[BRS Media Inc.]] for use by music, radio, and social media websites. A percentage of the income from .fm registrations goes back to the government and people of the Federated States of Micronesia.<ref>[http://en.wikipedia.org/wiki/.fm Wikipedia .fm]</ref> .am has also been used in the [[Domain Hack|domain hack]] instagr.am.<ref>[http://en.wikipedia.org/wiki/.am Wikipedia .am]</ref>
| |
|
| |
| ===.ws===
| |
| The .ws ccTLD is managed and operated by [[SamoaNIC]],<ref>[http://samoanic.ws/index.dhtml samoanic.ws]</ref> and it is promoting the TLD as a shortened form of Web Site or World Site.<ref>[http://nuvi.be/allabouttlds All About TLD]</ref> The marketing strategy provides users global presence. The marketing program for .ws is carried out by [[Global Domains International Incorporated]].<ref>[http://worldsite.ws/?sponsor=idntraffic Worldsite.ws]</ref>
| |
|
| |
| ===.me===
| |
| The ccTLD of Montenegro, [[.me]], has been marketed by [[DoMEn]] for use by bloggers, social media users, and socially inclined websites and companies.<ref>[http://kozmedia.com/for-countries-that-own-shorter-web-site-suffixes-extra-cash-from-abroad/222400/ For Countries That own Shorter Web Site Suffixes Extra Cash, Kozmedia.com]</ref>
| |
|
| |
| ==Current ccTLDs==
| |
| The following is a list of the current ccTLDs, including their [[registry]] operators and any special notes about registration of the domains.<ref>[http://www.iana.org/domains/root/db/ IANA Root Zone Database]</ref><ref>[http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Internationalized_country_code_top-level_domains Wikipedia: List of Internet to-level domains]</ref> | | The following is a list of the current ccTLDs, including their [[registry]] operators and any special notes about registration of the domains.<ref>[http://www.iana.org/domains/root/db/ IANA Root Zone Database]</ref><ref>[http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Internationalized_country_code_top-level_domains Wikipedia: List of Internet to-level domains]</ref> |
|
| |
|
| <table border="1" style="border-style: solid; border-color: darkgray; border-collapse: collapse" width="63%" cellpadding="6" width="900px"><tr><td>'''ccTLD'''</td><td>'''Entity'''</td><td>'''Registry Operator'''</td><td width="150px">'''Notes'''</td></tr>
| | <table border="1" style="border-style: solid; border-color: darkgray; border-collapse: collapse" cellpadding="6"> |
| <tr><td>[[.ac]]</td><td>Ascension Island</td><td>[[Nic.ac]]</td><td></td></tr>
| | <tr> |
| <tr><td>[[.ad]]</td><td>Andorra</td><td>[[Andorra Telecom]]</td><td></td></tr>
| | <td>'''ccTLD'''</td> |
| <tr><td>[[.ae]]</td><td>United Arab Emirates</td><td>[[UAEnic]]</td><td
| | <td>'''Entity'''</td> |
| | <td>'''Manager'''</td> |
| | <td>'''Registry Operator'''</td> |
| | </tr> |
| | <tr><td>[[.ac]]</td><td>Ascension Island</td><td></td><td>[[NIC.ac|NIC.AC]]</td></tr> |
| | <tr><td>[[.ad]]</td><td>Andorra</td><td></td><td>[[Andorra Telecom]]</td></tr> |
| | <tr><td>[[.ae]]</td><td>United Arab Emirates</td><td></td><td>[[.aeDA]]</td></tr |
| </table> | | </table> |
|
| |
|
Line 311: |
Line 307: |
| {{reflist}}</div> | | {{reflist}}</div> |
|
| |
|
| [[Category: Glossary]] | | [[Category:TLD]] |
| [[Category: Acronym]]
| |