Changes

==History==

==History==

===.xxx Application during the 2000 ICANN Proof of Concept===

===.xxx Application during the 2000 ICANN Proof of Concept===

[[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>

===.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 sTLDs after conducting public comments and 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, which will be responsible in developing policies for the proposed TLD. On 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 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 additional information to resolve the concerns raised by IRP in the report. On 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>

Following the presentation, a special meeting was conducted by the ICANN Board on May 3, 2005 and discussed whether the sponsored community baseline criteria was met or not by ICM Registry. The Board decided to further discuss the issue on another meeting. <ref>[http://www.icann.org/en/groups/board/documents/minutes-03may05-en.htm Minutes-Special Meeting of the Board May 3, 2005]</ref>

Following the presentation, a special meeting was conducted by the [[ICANN Board]] on May 3, 2005, where it discussed whether the sponsored community baseline criteria was met or not by ICM Registry. The Board decided to further discuss the issue at another meeting.<ref>[http://www.icann.org/en/groups/board/documents/minutes-03may05-en.htm Minutes-Special Meeting of the Board May 3, 2005]</ref>

On June 1, 2005, the ICANN Board tasked ICANN President [[Paul Twomey]] and General Counsel [[Jon Jeffrey]] to negotiate the proposed commercial and technical terms for a contractual agreement in connection with the delegation of .xxx sTLD.<ref>[http://www.icann.org/en/groups/board/documents/minutes-01jun05-en.htm Minutes Special Meeting of the Board, June 1, 2005]</ref>

On June 1, 2005, the ICANN Board charged [[ICANN CEO]] [[Paul Twomey]] and General Counsel [[Jon Jeffrey]] to negotiate the proposed commercial and technical terms for a contractual agreement in connection with the delegation of the [[.xxx]] sTLD.<ref>[http://www.icann.org/en/groups/board/documents/minutes-01jun05-en.htm Minutes Special Meeting of the Board, June 1, 2005]</ref>

On September 5, 2005, the proposed contractual agreement for .xxx sTLD was submitted to the ICANN Board for approval. It was also posted on ICANN's website. Significant number of comments, correspondences and inquiries from the internet and community were received by the Board relating to the contract. The Board directed the ICANN President and the General Counsel to discuss the possible additional contractual provisions or modifications for the .xxx Registry Agreemet to ensure the development and implementation of policies consistent with the principles of ICM Registry application.<ref>[https://community.icann.org/display/tap/2005-09-15+-+Review+of+Proposed+.XXX+Sponsored+Top-Level+Domain+Registry+Agreement 2005-09-15 - Review of Proposed .XXX Sponsored Top-Level Domain Registry Agreement]</ref>

On September 5, 2005, the proposed contractual agreement for .xxx sTLD was submitted to the ICANN Board for approval. It was also posted on ICANN's website. A significant number of comments and inquiries from the Internet community were received by the Board relating to the contract. The Board directed the ICANN CEO and the General Counsel to discuss the possible additional contractual provisions or modifications for the .xxx Registry Agreemet to ensure the development and implementation of policies consistent with the principles of ICM Registry application.<ref>[https://community.icann.org/display/tap/2005-09-15+-+Review+of+Proposed+.XXX+Sponsored+Top-Level+Domain+Registry+Agreement 2005-09-15 - Review of Proposed .XXX Sponsored Top-Level Domain Registry Agreement]</ref>

Several revisions were submitted and negotiations were made on the .xxx Registry Agreement between September 15, 2005 until January 5, 2007. Extensive comments and advice were also received from global internet community and from the [[GAC|Governmental Advisory Committee]], which were evaluated by the ICANN Board. On March 30, 2007, the ICANN Board denied the ICM Registry application citing that the company failed to meet the Sponsored Community criteria set forth in the RFP, the .xxx sTLD raised public policy, approval of the Registry Agreement will not resolve the issue raised by GAC such as offensive content and protection of vulnerable members of the community, the application raises significant law enforcement issues in different countries and the application poses a possibility that ICANN might be forced to assume an ongoing management and oversight role regarding Internet content, which is inconsistent with its technical mandate.<ref>[http://www.icann.org/en/groups/board/documents/resolutions-30mar07-en.htm#_Toc36876524 Adopted Resolutions from ICANN Board Meeting, 30 March 2007]</ref>

Several revisions were submitted and negotiations were made on the .xxx Registry Agreement between September 15, 2005 until January 5, 2007. Extensive comments and advice were also received from the global internet community and from the [[GAC|Governmental Advisory Committee]], which were evaluated by the ICANN Board. On March 30, 2007, the ICANN Board denied the ICM Registry application citing that the company failed to meet the Sponsored Community criteria set forth in the RFP, issues raised by GAC such as offensive content and protection of vulnerable members of the community were not properly adressed, the application raised significant law enforcement issues in different countries, and the application posed a possibility that ICANN might be forced to assume an ongoing management and oversight role regarding Internet content, which is inconsistent with its technical mandate.<ref>[http://www.icann.org/en/groups/board/documents/resolutions-30mar07-en.htm#_Toc36876524 Adopted Resolutions from ICANN Board Meeting, 30 March 2007]</ref>

==Independent Review Proceedings==

==Independent Review Proceedings==