Line 40: |
Line 40: |
| Iron Mountain has a long history with [[ICANN]], protecting registry data, registrar data, and new gTLD client data. Iron Mountain has also been selected to manage data escrow for boutique and forward thinking ccTLDs in the market, such as .me, .cat, etc. | | Iron Mountain has a long history with [[ICANN]], protecting registry data, registrar data, and new gTLD client data. Iron Mountain has also been selected to manage data escrow for boutique and forward thinking ccTLDs in the market, such as .me, .cat, etc. |
| | | |
− | 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 ([[RAA]]). | + | 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]]). |
| | | |
− | In 2013, Iron Mountain was approved by ICANN to provide data escrow services to [[new gTLD]] clients<ref name="icann> [http://newgtlds.icann.org/en/announcements-and-media/announcement-31may13-en], ICANN.org. Published 2013 May 31.</ref> as the domain name space expands. To date, Iron Mountain has been selected by over 800 new gTLDs to provide escrow services for their registry data. | + | In 2013, Iron Mountain was approved by ICANN to provide '''data escrow services to [[new gTLD]] clients'''<ref name="icann> [http://newgtlds.icann.org/en/announcements-and-media/announcement-31may13-en], ICANN.org. Published 2013 May 31.</ref> as the domain name space expands. To date, Iron Mountain has been selected by over 800 new gTLDs to provide escrow services for their registry data. |
| | | |
| The company is a regular exhibitor and sponsor at [[ICANN Meetings]]. | | The company is a regular exhibitor and sponsor at [[ICANN Meetings]]. |