Changes

Jump to navigation Jump to search
1,959 bytes added ,  6 years ago
Grafted GAC advice from GAC article.
Line 18: Line 18:  
[[ICM Registry]] proposed the .xxx as non-sponsored [[gTLD|generic top-level domain name]] (gTLD) during the ICANN Proof of Concept round in 2000. ICANN's evaluation team did not recommend the string because of the "controversy surrounding it and the poor
 definition 
of 
the
 hope for 
benefits
 of .xxx." On December 15, 2000, ICM Registry filed a Reconsideration Request with ICANN but no action was rendered. The [[ICANN Board]] cited that "no new TLD proposal has been rejected, rather a small set of potentially successful applicants had been selected with the aim of testing a diversity of approaches to the creation of new TLDs."
 
[[ICM Registry]] proposed the .xxx as non-sponsored [[gTLD|generic top-level domain name]] (gTLD) during the ICANN Proof of Concept round in 2000. ICANN's evaluation team did not recommend the string because of the "controversy surrounding it and the poor
 definition 
of 
the
 hope for 
benefits
 of .xxx." On December 15, 2000, ICM Registry filed a Reconsideration Request with ICANN but no action was rendered. The [[ICANN Board]] cited that "no new TLD proposal has been rejected, rather a small set of potentially successful applicants had been selected with the aim of testing a diversity of approaches to the creation of new TLDs."
 
<ref>[http://cyber.law.harvard.edu/pubrelease/icann/pdfs/AppendixD_xxx.pdf Accountability
 and
 Transparency 
at ICANN
: An
 Independent
 Review]</ref>
 
<ref>[http://cyber.law.harvard.edu/pubrelease/icann/pdfs/AppendixD_xxx.pdf Accountability
 and
 Transparency 
at ICANN
: An
 Independent
 Review]</ref>
 
+
===GAC Advice on the .xxx sTLD===
 +
On March 17, 2011, the GAC, via its Chairman [[Heather Dryden]], reiterated to ICANN Chairman [[Peter Dengate Thrush]] that the Committee has no active support for the implementation of the [[.xxx]] [[sTLD]]. The GAC also informed ICANN that some governments might prevent access to the TLD, which could harm the global interoperability and stability of the internet. Furthermore, the Committee also pointed out the possibility that ICANN may have to assume a management and oversight role regarding .xxx content.<ref>[http://news.dot-nxt.com/2011/03/17/gac-statement-dot-xxx GAC Statement on .xxx]</ref> Despite GAC's position, the [[ICANN Board]] approved the .xxx sTLD during the [[ICANN 41]] Meeting in San Francisco, on March 18, 2011.<ref>[http://news.dot-nxt.com/2011/04/03/summary-icann-san-francisco#xxx Conference summary: ICANN San Francisco]</ref> The disregard for the GAC's advice in this instance provided for a number of other international entities to question ICANN's ability to successfully manage the [[DNS]].
 
===.xxx during the 2003 sTLD Application Process===  
 
===.xxx during the 2003 sTLD Application Process===  
 
On December 15, 2003, the ICANN Board published a Request For Proposal (RFP) for new [[sTLD]]s after extensive discussions within the different stakeholders within the ICANN community. [[ICM Registry]] submitted a proposal for.xxx on March 16 2004. IFFOR was named as the sponsoring organization, responsible for developing policies for the proposed TLD. In August, 2004, the [[IRP|Independent Review Panel]] evaluated ICM's application and reported to the [[ICANN Board]] that the the company failed to meet the baseline sponsorship criteria for a [[sTLD]].<ref>[http://www.iana.org/reports/2011/xxx-report-20110407.pdf Delegation of the .XXX top-level domain]</ref> Following the report, the ICANN Board approved a resolution allowing sTLD applicants to add additional information to resolve the concerns raised by IRP in the report. In October, 2004, ICM Registry started submitting additional documents to strengthen its application. ICM Registry was invited to make a presentation on April 3, 2005.<ref>[http://archive.icann.org/en/tlds/stld-apps-19mar04/stld-status-report.pdf Status Report on the sTLD Evaluation Process]</ref>
 
On December 15, 2003, the ICANN Board published a Request For Proposal (RFP) for new [[sTLD]]s after extensive discussions within the different stakeholders within the ICANN community. [[ICM Registry]] submitted a proposal for.xxx on March 16 2004. IFFOR was named as the sponsoring organization, responsible for developing policies for the proposed TLD. In August, 2004, the [[IRP|Independent Review Panel]] evaluated ICM's application and reported to the [[ICANN Board]] that the the company failed to meet the baseline sponsorship criteria for a [[sTLD]].<ref>[http://www.iana.org/reports/2011/xxx-report-20110407.pdf Delegation of the .XXX top-level domain]</ref> Following the report, the ICANN Board approved a resolution allowing sTLD applicants to add additional information to resolve the concerns raised by IRP in the report. In October, 2004, ICM Registry started submitting additional documents to strengthen its application. ICM Registry was invited to make a presentation on April 3, 2005.<ref>[http://archive.icann.org/en/tlds/stld-apps-19mar04/stld-status-report.pdf Status Report on the sTLD Evaluation Process]</ref>
Line 42: Line 43:  
During the [[ICANN 40]] meeting in San Francisco in March, 2011, the ICANN Board approved the ICM application.<ref>[http://www.above.com/blog/2011/03/xxx-approved-at-icann-40.html .XXX Approved at ICANN 40]</ref> The .xxx string was delegated to the [[Root Zone|root zone]] of the [[DNS]] in June, 2011.<ref>[http://www.computerworld.com/s/article/9178518/ICANN_board_approves_dot_XXX_top_level_domain_for_porn?taxonomyId=18&pageNumber=2 ICANN board approves dot-XXX top-level domain for porn]</ref>
 
During the [[ICANN 40]] meeting in San Francisco in March, 2011, the ICANN Board approved the ICM application.<ref>[http://www.above.com/blog/2011/03/xxx-approved-at-icann-40.html .XXX Approved at ICANN 40]</ref> The .xxx string was delegated to the [[Root Zone|root zone]] of the [[DNS]] in June, 2011.<ref>[http://www.computerworld.com/s/article/9178518/ICANN_board_approves_dot_XXX_top_level_domain_for_porn?taxonomyId=18&pageNumber=2 ICANN board approves dot-XXX top-level domain for porn]</ref>
   −
==.xxx Sponsoring Community==
+
==.xxx Policies==
 
The sponsoring community of the .xxx includes individuals, companies, organizations, providers of adult entertainment. Some of these entities include adult website administrators, club owners, performers, agents, lawyers, distributors and manufacturers or adult  products. All entities interested in registering a .xxx domain need to become a member of the community. Individuals must provide correct date of birth, address, phone number, confirm membership to the community, and accept the Registry-Registrant Agreement. <ref>[http://www.icmregistry.com/about/sponsored-community/ Who Qualifies for the Sponsored Community]</ref>
 
The sponsoring community of the .xxx includes individuals, companies, organizations, providers of adult entertainment. Some of these entities include adult website administrators, club owners, performers, agents, lawyers, distributors and manufacturers or adult  products. All entities interested in registering a .xxx domain need to become a member of the community. Individuals must provide correct date of birth, address, phone number, confirm membership to the community, and accept the Registry-Registrant Agreement. <ref>[http://www.icmregistry.com/about/sponsored-community/ Who Qualifies for the Sponsored Community]</ref>
   −
===Policies===
   
The [[IFFOR]] implements policies to comply with its agreements; to protect the privacy, security and consumer rights of consenting adults; to help user choice and parental control with regards to access to online adult content; and to fight child abuse images. Its' baseline policies include:<ref>[http://www.icmregistry.com/policies/iffor/ IFFOR Baseline Policies]</ref>
 
The [[IFFOR]] implements policies to comply with its agreements; to protect the privacy, security and consumer rights of consenting adults; to help user choice and parental control with regards to access to online adult content; and to fight child abuse images. Its' baseline policies include:<ref>[http://www.icmregistry.com/policies/iffor/ IFFOR Baseline Policies]</ref>
 
* Registration is restricted to the sponsoring community
 
* Registration is restricted to the sponsoring community
Line 63: Line 63:     
==Domain Statistics==
 
==Domain Statistics==
As of June 7, 2012, .xxx had 137,000 active registrations, and 220,000 total registrations, including approximately 83,000 domain names that were blocked by trademark holders paying a one time fee.
+
As of June 2, 2013, .xxx had 122,000 active registrations, after a peak at 142,000 in December 2012. During May 2013, [[ICM Registry]] cut the prices for .xxx names down to .com-level prices, resulting in a large number of registrations during that month.<ref>[http://domainincite.com/13245-icm-price-cut-sees-10-times-more-xxx-sales ICM Price Cut sees 10 times more xxx sales, Domain Incite] Retrieved 19 Sept 2013</ref>
    
The following are the top 10 .xxx registrars as of February 2012:<ref>[http://domainnamewire.com/2012/06/07/xxx-up-to-137k-active-registrations-220k-total-and-new-630k-premium-sale/ .XXX up to 137k active registrations, 220k total, and new $630k premium sale, domainnamewire]</ref>
 
The following are the top 10 .xxx registrars as of February 2012:<ref>[http://domainnamewire.com/2012/06/07/xxx-up-to-137k-active-registrations-220k-total-and-new-630k-premium-sale/ .XXX up to 137k active registrations, 220k total, and new $630k premium sale, domainnamewire]</ref>
Line 91: Line 91:  
===Search.xxx===
 
===Search.xxx===
 
In September, 2012, the .xxx centric search engine at search.xxx was launched by ICM Registry. The search engine does not have a direct revenue model, but is instead a means of directing greater traffic to .xxx sites. Touted benefits of the search engine include: a pornographic focused search rather than a search that could result in non-pornographic sexual material, a safe and focused search for adults, the ability to search via sexual orientation, and not saving or recording searches to one's Google search history. The long-term goal is to increase the market-share of .xxx.<ref>[http://www.cnbc.com/id/49212131/ CNBC.com]</ref>
 
In September, 2012, the .xxx centric search engine at search.xxx was launched by ICM Registry. The search engine does not have a direct revenue model, but is instead a means of directing greater traffic to .xxx sites. Touted benefits of the search engine include: a pornographic focused search rather than a search that could result in non-pornographic sexual material, a safe and focused search for adults, the ability to search via sexual orientation, and not saving or recording searches to one's Google search history. The long-term goal is to increase the market-share of .xxx.<ref>[http://www.cnbc.com/id/49212131/ CNBC.com]</ref>
 +
==Other==
 +
===Russian iTunes Glitch===
 +
On December 5th 2012, sections of the Russian iTunes store featured out of place banner ads and explicit content from ICM's registry internal search engine, xxx.xxx. Bloggers speculated than an Apple Web Developer may have entered the "xxx.xxx" as a placeholder not realizing that the URL would resolve as a live domain.<ref>[http://domainincite.com/11253-russian-itunes-store-infiltrated-by-xxx-banners-after-snafu-nsfw Russian iTunes Store Infiltrated by XXX Banners after Snafu, DomainIncite.com] Retrieved & Published 5 Dec 2012</ref>
    
==References==
 
==References==
{{reflist}}
+
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
 
+
{{reflist}}</div>
 
  −
 
      
[[Category:TLD]]
 
[[Category:TLD]]
 +
[[Category:TLDs with Registry Agreements|xxx]]

Navigation menu