Jump to content

Community TLD: Difference between revisions

From ICANNWiki
Marie Cabural (talk | contribs)
No edit summary
Marie Cabural (talk | contribs)
No edit summary
Line 3: Line 3:
'''Community gTLD''' is one of the different categories of generic top level domain names ([[gTLD]]s) created by the [[ICANN|Internet Corporation for Assigned Names and Numbers]], which is primarily intended for community groups that are interested in operating their own TLD Registry. Community gTLDs should represent and receive strong support from a clearly defined group of people who will benefit from the TLD such as cities, cultural, regional, geographical, religious and social groups as well as industry sectors.<ref>[http://www.newgtldsite.com/community-gtlds/ Community gTLDs]</ref> A good example of community group that represents a clearly defined group of people that maybe qualified to apply for a community gTLD is the American Association of Retired Persons (AARP). This group is well-established and it can demonstrate that it has a continuous relationship with its members. <ref>$http://www.mindsandmachines.com/2011/07/will-anyone-qualify-as-a-community-tld/ Will Anyone Qualify as a Community TLD?]</ref>
'''Community gTLD''' is one of the different categories of generic top level domain names ([[gTLD]]s) created by the [[ICANN|Internet Corporation for Assigned Names and Numbers]], which is primarily intended for community groups that are interested in operating their own TLD Registry. Community gTLDs should represent and receive strong support from a clearly defined group of people who will benefit from the TLD such as cities, cultural, regional, geographical, religious and social groups as well as industry sectors.<ref>[http://www.newgtldsite.com/community-gtlds/ Community gTLDs]</ref> A good example of community group that represents a clearly defined group of people that maybe qualified to apply for a community gTLD is the American Association of Retired Persons (AARP). This group is well-established and it can demonstrate that it has a continuous relationship with its members. <ref>$http://www.mindsandmachines.com/2011/07/will-anyone-qualify-as-a-community-tld/ Will Anyone Qualify as a Community TLD?]</ref>


==Requirements of Community gTLD Applicants==
==Requirements for Community gTLD Applicants==
Based on the gTLD Applicant Guidebook, applicants for community based gTLDs should:<ref>[http://www.icann.org/en/topics/new-gtlds/rfp-clean-19sep11-en.pdf gTLD Applicant Guidebook, Version 2011-09-19]</ref>
Based on the gTLD Applicant Guidebook, applicants for community based gTLDs should:<ref>[http://www.icann.org/en/topics/new-gtlds/rfp-clean-19sep11-en.pdf gTLD Applicant Guidebook, Version 2011-09-19]</ref>
# Demonstrate an ongoing relationship with a clearly delineated community.  
# Demonstrate an ongoing relationship with a clearly delineated community.  

Revision as of 19:03, 23 January 2012

Community gTLD is one of the different categories of generic top level domain names (gTLDs) created by the Internet Corporation for Assigned Names and Numbers, which is primarily intended for community groups that are interested in operating their own TLD Registry. Community gTLDs should represent and receive strong support from a clearly defined group of people who will benefit from the TLD such as cities, cultural, regional, geographical, religious and social groups as well as industry sectors.[1] A good example of community group that represents a clearly defined group of people that maybe qualified to apply for a community gTLD is the American Association of Retired Persons (AARP). This group is well-established and it can demonstrate that it has a continuous relationship with its members. [2]

Requirements for Community gTLD Applicants[edit | edit source]

Based on the gTLD Applicant Guidebook, applicants for community based gTLDs should:[3]

  1. Demonstrate an ongoing relationship with a clearly delineated community.
  2. Have applied for a gTLD string strongly and specifically related to the community named in the application.
  3. Have proposed dedicated registration and use policies or registrants in its proposed gTLD, including appropriate security verification procedures, commensurate with the community-based purpose it has named.
  4. Have its application endorsed in writing by one or more established institutions representing the community it has named.