Changes

* 2007, January - ICM had posted another iteration of the registry agreement for public comments,<ref>[http://www.webcitation.org/5gAwFTjYy "ICANN Publishes Revision to Proposed ICM (.xxx) Registry Agreement for Public Comment"]</ref> while, in March, the [[GAC]] noted that it did not believe that the ICANN Board sufficiently answered its questions regarding ICM and the sponsorship criteria. Subsequently, still at [[ICANN 28]] in Lisbon, the board voted down the ICM's application for .xxx. They noted that their decision was made based on the following findings: ICM does not meet the sponsorship requirements; the GAC believes that this lack of clear sponsorship will create public policy issues; the application raises significant law enforcement issues that it does not seek to rectify; the Board and GAC agree that the implementation would involve ICANN overseeing a significant amount of Internet content, which oversteps the organization's technical mandate.<ref>[http://www.icann.org/en/minutes/draft-icm-rationale-18mar11-en.pdf Draft ICM Rationale 18Mar11, ICANN.org]</ref>

* 2007, January - ICM had posted another iteration of the registry agreement for public comments,<ref>[http://www.webcitation.org/5gAwFTjYy "ICANN Publishes Revision to Proposed ICM (.xxx) Registry Agreement for Public Comment"]</ref> while, in March, the [[GAC]] noted that it did not believe that the ICANN Board sufficiently answered its questions regarding ICM and the sponsorship criteria. Subsequently, still at [[ICANN 28]] in Lisbon, the board voted down the ICM's application for .xxx. They noted that their decision was made based on the following findings: ICM does not meet the sponsorship requirements; the GAC believes that this lack of clear sponsorship will create public policy issues; the application raises significant law enforcement issues that it does not seek to rectify; the Board and GAC agree that the implementation would involve ICANN overseeing a significant amount of Internet content, which oversteps the organization's technical mandate.<ref>[http://www.icann.org/en/minutes/draft-icm-rationale-18mar11-en.pdf Draft ICM Rationale 18Mar11, ICANN.org]</ref>

* 2010- February 19th, [[ICANN]]'s [[IRP]] (Independent Review Panel) issued a declaration in its review of ICM Registry's appeal.<ref>[http://www.icann.org/en/announcements/announcement-2-26mar10-en.htm "Public Comment: Report of Possible Process Options for Further Consideration of the ICM Application for the .xxx sTLD"]</ref> The Panel found that the application for the ".xxx [[sTLD]] met the required sponsorship criteria," and that "the Board’s reconsideration of that finding was not consistent with the application of neutral, objective and fair documented policy."<ref>[http://www.icann.org/en/irp/icm-v-icann/draft-options-post-irp-declaration-26mar10-en.pdf "ICANN Options Following the IRP Declaration on ICM's .xxx Application"]</ref> A 45 day public comment was opened on March 26, 2010.

* 2010- February 19th, [[ICANN]]'s [[IRP]] (Independent Review Panel) issued a declaration in its review of ICM Registry's appeal.<ref>[http://www.icann.org/en/announcements/announcement-2-26mar10-en.htm "Public Comment: Report of Possible Process Options for Further Consideration of the ICM Application for the .xxx sTLD"]</ref> The Panel found that the application for the ".xxx [[sTLD]] met the required sponsorship criteria," and that "the Board’s reconsideration of that finding was not consistent with the application of neutral, objective and fair documented policy."<ref>[http://www.icann.org/en/irp/icm-v-icann/draft-options-post-irp-declaration-26mar10-en.pdf "ICANN Options Following the IRP Declaration on ICM's .xxx Application"]</ref> A 45 day public comment was opened on March 26, 2010.

* 2010- June 25th, [[ICANN]]'s board approved the proposal at [[ICANN 40]] in San Francisco, USA, thereby authorizing the implementation of .xxx in the [[Root Zone|root zone]].<ref>[http://www.nytimes.com/glogin?URI=http://www.nytimes.com/2010/06/26/technology/26domain.html&OQ=_rQ3D1Q26srcQ3Dbusln&OP=10b995d5Q2Fzq@yzQ7E!Q5Do6!!DXzXCjCzCQ51zXQ51zD@Q5DQ2F_!5!Q7BQ26zXQ51Q7E!uiQ20_,Q2FDu5 Miguel Helft (June 25, 2010). "For X-Rated, a Domain of Their Own"]</ref>

* 2011- June 25th, [[ICANN]]'s board approved the proposal at [[ICANN 40]] in San Francisco, USA, thereby authorizing the implementation of .xxx in the [[Root Zone|root zone]].<ref>[http://www.nytimes.com/glogin?URI=http://www.nytimes.com/2010/06/26/technology/26domain.html&OQ=_rQ3D1Q26srcQ3Dbusln&OP=10b995d5Q2Fzq@yzQ7E!Q5Do6!!DXzXCjCzCQ51zXQ51zD@Q5DQ2F_!5!Q7BQ26zXQ51Q7E!uiQ20_,Q2FDu5 Miguel Helft (June 25, 2010). "For X-Rated, a Domain of Their Own"]</ref>

== Services offered by ICM Registry ==

== Services offered by ICM Registry ==