Iron Mountain: Difference between revisions

Line 42:

In 2001, Iron Mountain was the first company ever selected by ICANN to protect [[registry]] data via escrow agreements. Each Registry Operator must comply with provisions contained within a [[Registry Data Escrow Agreement]] as part of its Registry Agreement with ICANN. This agreement requires registries to periodically transfer registry data for their generic Top-Level Domains ([[gTLD]]s) to a reputable escrow agent to be held in escrow, in order to protect registrant interests in the case of a registry's failure.

In 2007, Iron Mountain was selected by ICANN to function as its [[Registrar Data Escrow]] agent.<ref name="icann">[http://www.icann.org/en/announcements/announcement-2-13feb08.htm ICANN announcement], ICANN.org. Published 2008 February 13.</ref> Today, there are nearly 1,000 registrars, and ICANN now requires these registrars to escrow critical registration data that could then be released to ICANN in case there is a termination of the [[registrar]]'s [[~~accreditation agreement~~]].

In 2007, Iron Mountain was selected by ICANN to function as its [[Registrar Data Escrow]] agent.<ref name="icann">[http://www.icann.org/en/announcements/announcement-2-13feb08.htm ICANN announcement], ICANN.org. Published 2008 February 13.</ref> Today, there are nearly 1,000 registrars, and ICANN now requires these registrars to escrow critical registration data that could then be released to ICANN in case there is a termination of the [[registrar]]'s accreditation agreement ([[RAA]]).

Revision as of 15:42, 30 October 2013 view source Dmmkdoyle (talk \| contribs) 132 edits No edit summary ← Older edit		Revision as of 15:43, 30 October 2013 view source Dmmkdoyle (talk \| contribs) 132 edits No edit summary Newer edit →
Line 42:		Line 42:
	In 2001, Iron Mountain was the first company ever selected by ICANN to protect [[registry]] data via escrow agreements. Each Registry Operator must comply with provisions contained within a [[Registry Data Escrow Agreement]] as part of its Registry Agreement with ICANN. This agreement requires registries to periodically transfer registry data for their generic Top-Level Domains ([[gTLD]]s) to a reputable escrow agent to be held in escrow, in order to protect registrant interests in the case of a registry's failure.		In 2001, Iron Mountain was the first company ever selected by ICANN to protect [[registry]] data via escrow agreements. Each Registry Operator must comply with provisions contained within a [[Registry Data Escrow Agreement]] as part of its Registry Agreement with ICANN. This agreement requires registries to periodically transfer registry data for their generic Top-Level Domains ([[gTLD]]s) to a reputable escrow agent to be held in escrow, in order to protect registrant interests in the case of a registry's failure.

	In 2007, Iron Mountain was selected by ICANN to function as its [[Registrar Data Escrow]] agent.<ref name="icann">[http://www.icann.org/en/announcements/announcement-2-13feb08.htm ICANN announcement], ICANN.org. Published 2008 February 13.</ref> Today, there are nearly 1,000 registrars, and ICANN now requires these registrars to escrow critical registration data that could then be released to ICANN in case there is a termination of the [[registrar]]'s [[~~accreditation agreement~~]].		In 2007, Iron Mountain was selected by ICANN to function as its [[Registrar Data Escrow]] agent.<ref name="icann">[http://www.icann.org/en/announcements/announcement-2-13feb08.htm ICANN announcement], ICANN.org. Published 2008 February 13.</ref> Today, there are nearly 1,000 registrars, and ICANN now requires these registrars to escrow critical registration data that could then be released to ICANN in case there is a termination of the [[registrar]]'s accreditation agreement ([[RAA]]).