Changes

2,073 bytes added ,  12 years ago
Line 18: Line 18:  
<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>
 
   
 
   
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 Independent Review Panel evaluated the ICM's application and reported 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>
+
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>
 +
 
 +
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>
 +
 
 +
On June 1, 2005, the ICANN Board tasked the 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 August 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>
    
==References==
 
==References==
9,082

edits