Changes

Jump to navigation Jump to search
no edit summary
Line 35: Line 35:  
==Iron Mountain's History with ICANN==
 
==Iron Mountain's History with ICANN==
   −
Iron Mountain has a long history with [[ICANN]], protecting [[registry]] data, [[registrar]] data, and new generic Top-Level Domain ([[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]], and others.
+
Iron Mountain has a long history with [[ICANN]], protecting [[registry]] data, [[registrar]] data, and new generic Top-Level Domain ([[gTLD]]) client data. 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 ord er 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 13 February 2008.</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 13 February 2008.</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]]).
Line 52: Line 50:     
Iron Mountain has developed the Information Guide [http://www.ironmountain.com/Knowledge-Center/Reference-Library/View-by-Document-Type/White-Papers-Briefs/D/Data-Escrow-for-the-New-gTLDs.aspx “Data Escrow for the New gTLDs: Safeguarding Your Future”] to provide more information.<ref>[http://www.ironmountain.com/~/media/Files/Iron%20Mountain/Knowledge%20Center/Reference%20Library/White%20Paper/D/Data%20Escrow%20for%20the%20New%20gTLDs Data Escrow for the New gTLDs], Iron Mountain. Published 2011.</ref>
 
Iron Mountain has developed the Information Guide [http://www.ironmountain.com/Knowledge-Center/Reference-Library/View-by-Document-Type/White-Papers-Briefs/D/Data-Escrow-for-the-New-gTLDs.aspx “Data Escrow for the New gTLDs: Safeguarding Your Future”] to provide more information.<ref>[http://www.ironmountain.com/~/media/Files/Iron%20Mountain/Knowledge%20Center/Reference%20Library/White%20Paper/D/Data%20Escrow%20for%20the%20New%20gTLDs Data Escrow for the New gTLDs], Iron Mountain. Published 2011.</ref>
 +
 +
===Summary of Iron Mountain Registry and Registrar Escrow Services===
 +
* More than 70% of all new gTLDs delegated have chosen IRM to fulfill their data escrow requirements to ICANN.
 +
* Iron Mountain has the most experience of any escrow agent and manages over 140 million domain names.
 +
* Since 2001, Iron Mountain has handled over 500,000 data escrow deposits.
 +
* Iron Mountain is the only Fortune 1000 company committed to the data escrow business with over 30 years of know-how in the escrow business.
 +
 +
====Registry Data Escrow====
 +
Registry operators worldwide are recognizing the need for full compliance with data escrow requirements. Registry data escrow is one of the essential stakeholder protection mechanisms for the gTLDs. The purpose of registry data escrow is to help safeguard registrar and registrant interests in the event of a registry’s business or technical failure. Registry data escrow ensures that the data associated with registered domain names is never at risk of being lost or inaccessible. Registry data escrow is a specialized data protection service designed to meet the compliance and “best practice” needs of domain name registrants worldwide. Iron Mountain protects the registry data through use of RAID storage and physical backup tapes stored in secure facilities. This service ensures that up-to-date copies of domain name ownership and contact details are held in escrow by a trusted, neutral third party (such as Iron Mountain), and that this information can be accessed and released only under pre-defined and controlled conditions. Iron Mountain’s Registry Data Escrow service is fully automated and has been enhanced at the request of ICANN and the registry community and per the specifications of the program to ensure customer ease-of-use.<ref>[http://www.ironmountain.com/Services/Technology-Escrow-Services/Registry-Data-Escrow.aspx Technology Escrow Services, Registry Data Escrow] Iron Mountain Retrieved Sept 18 2014</ref>
 +
 +
Review more information in Iron Mountain’s “[http://www.ironmountain.com/Knowledge-Center/Reference-Library/View-by-Document-Type/Data-Sheets-Brochures/R/Registry-Data-Escrow-FAQ.aspx Frequently Asked Questions about Registry Data Escrow.]”
 +
 +
For more technical detail, Iron Mountain has developed “Registry Data Escrow Service: Your Technical Questions Answered.”
 +
 +
Iron Mountain also provides a document on learning how to “Protect the Data Associated with your gTLD.”
    
==Iron Mountain Business Scope and History==
 
==Iron Mountain Business Scope and History==

Navigation menu