ICM Registry: Difference between revisions
removing text that seems non-neutral |
internal linking |
||
Line 30: | Line 30: | ||
== Services offered by ICM Registry == | == Services offered by ICM Registry == | ||
ICM Registry intends to provide the registry service for both .XXX and .KIDS through the Internet's | ICM Registry intends to provide the registry service for both .XXX and .KIDS through two of the Internet's registry-service providers: dotTV Corporation and [[VeriSign]] Global Registry Services. Primary registry application functions will be performed by dotTV. [[VeriSign]] will provide a supporting role for all registration functions, ensuring the registry is reliable and stable. | ||
ICM Registry and its partners will offer superior quality and reliable services based on their track records, expertise and experience. In particular, ICM Registry's proposal is predicated on: | ICM Registry and its partners will offer superior quality and reliable services based on their track records, expertise and experience. In particular, ICM Registry's proposal is predicated on: |
Revision as of 20:02, 14 November 2010
Type: | Private |
Industry: | Internet, Registry |
Founded: | Delware, USA (2000) |
Headquarters: | Suite 2500 130, Adelaide Street West, |
Website: | http://www.icmregistry.com/ |
Key People | |
Jason Hendeles, Vice President – Strategic Business Development Stuart Lawley, Chairman and President |
ICM Registry is the registry operator behind the .xxx registry. The International Foundation for Online Responsibility (IFFOR) is the sponsoring organization[1].
History[edit | edit source]
ICM Registry was founded in the year 2000 by Jason Hendeles. It was founded in Delaware, USA.
ICM Registry, a private company, submitted a proposal in ICANN’s 2000 Proof of Concept round, proposing two unsponsored gTLD strings - .KIDS and .XXX [2]. The evaluators in the Proof of Concept round recommended against the inclusion of either the .KIDS or the .XXX TLD strings in the Proof of Concept round[3].
After this, ICM Registry's proposal was accepted and later revoked many times.
On January 6, 2007, ICANN put up for public comment a revised proposal [4] following changes to the policy of the ICM registry including the policing of any site that signs up to use the .xxx registry. On March 30, 2007, ICANN rejected the .xxx proposal for the third time, citing that the board did not want to get in the business of content regulation, especially when the definition of "pornography" varies by jurisdiction.
On February 19, 2010 ICANN's Independent Review Panel issued a declaration in its review of ICM Registry's appeal[5]. 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"[6]. A 45 day public comment was opened on March 26, 2010, and on June 25, 2010, the ICANN board approved the proposal[7].
Services offered by ICM Registry[edit | edit source]
ICM Registry intends to provide the registry service for both .XXX and .KIDS through two of the Internet's registry-service providers: dotTV Corporation and VeriSign Global Registry Services. Primary registry application functions will be performed by dotTV. VeriSign will provide a supporting role for all registration functions, ensuring the registry is reliable and stable.
ICM Registry and its partners will offer superior quality and reliable services based on their track records, expertise and experience. In particular, ICM Registry's proposal is predicated on:
- verifiable service-level agreements to protect customers from liability and service interruption;
- providing registrars with a fast, ultra-reliable service to meet registrant expectations;
- back up and escrow services to safeguard data and information;
- an advanced registration software system to facilitate integration of registration services.
ICM Registry also offers:
- a complete suite of value added services to meet the specialized and different needs of registrars, registrants, and trademark holders;
- optimal security, firewall, anti-virus and intrusion detection;
- strategically located service nodes worldwide[8].
References[edit | edit source]
- ↑ About ICM Registry
- ↑ ICANN.org
- ↑ ICANN.org
- ↑ "ICANN Publishes Revision to Proposed ICM (.XXX) Registry Agreement for Public Comment"
- ↑ "Public Comment: Report of Possible Process Options for Further Consideration of the ICM Application for the .XXX sTLD"
- ↑ "ICANN Options Following the IRP Declaration on ICM's .XXX Application"
- ↑ Miguel Helft (June 25, 2010). "For X-Rated, a Domain of Their Own"
- ↑ ICANN.org