Iron Mountain: Difference between revisions
No edit summary |
|||
| Line 48: | Line 48: | ||
[[ICANN]] selected Iron Mountain to be the digital escrow agent for its [[Registrar Data Escrow]] program.<ref>[http://www.icann.org/en/announcements/announcement-2-13feb08.htm ICANN announcement]</ref> This program is designed to secure the Internet's [[DNS|domain name system]] by protecting important data through Iron Mountain's digital department.<ref>[[ICANN 40]] Interview</ref> | [[ICANN]] selected Iron Mountain to be the digital escrow agent for its [[Registrar Data Escrow]] program.<ref>[http://www.icann.org/en/announcements/announcement-2-13feb08.htm ICANN announcement]</ref> This program is designed to secure the Internet's [[DNS|domain name system]] by protecting important data through Iron Mountain's digital department.<ref>[[ICANN 40]] Interview</ref> | ||
At the time of the agreement in 2007, Iron Mountain immediately made itself available to the more than 900 [[ICANN]]-accredited domain name registrars, though any registrar could also choose to use a different third party provider as the escrow agent.<ref>[http://www.ironmountain.com/news/2007/impr11282007.asp Iron Mountain News]</ref> [[ICANN]] now requires 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.<ref>[[ICANN 40]] Interview</ref> | At the time of the agreement in 2007, Iron Mountain immediately made itself available to the more than 900 [[ICANN]]-accredited domain name registrars, though any registrar could also choose to use a different third party provider as the escrow agent.<ref>[http://www.ironmountain.com/news/2007/impr11282007.asp Iron Mountain News]</ref> [[ICANN]] now requires registrars to escrow critical registration data that could then be released to [[ICANN]] in case there is a termination of the [[registrar]]'s [[RAA|accreditation agreement]].<ref>[[ICANN 40]] Interview</ref> | ||
===Highlights of Iron Mountain Registry and Registrar Escrow Services=== | ===Highlights of Iron Mountain Registry and Registrar Escrow Services=== | ||
| Line 58: | Line 58: | ||
===Registry Data Escrow=== | ===Registry Data Escrow=== | ||
Registry data escrow is one of the essential stakeholder protection mechanisms for gTLDs. 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. The 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), to be accessed and released only under pre-defined and controlled conditions. 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 is one of the essential stakeholder protection mechanisms for gTLDs. 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. The 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), to be accessed and released only under pre-defined and controlled conditions. 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.<ref>[http://www.ironmountain.com/Knowledge-Center/Reference-Library/View-by-Document-Type/Data-Sheets-Brochures/R/Registry-Data-Escrow-Data-Sheet.aspx Registry Data Escrow Service, ironmountain.com] | ||
[http://www.ironmountain.com/Knowledge-Center/Reference-Library/View-by-Document-Type/Data-Sheets-Brochures/R/Registry-Data-Escrow-Data-Sheet.aspx | |||
===Registrar Data Escrow=== | ===Registrar Data Escrow=== | ||
ICANN began implementation of its Registrar Data Escrow program in 2007. This program is designed to help ensure the stability and security of the Internet's domain name system through escrow of critical gTLD registration data, ensuring that the information associated with registered domain names is never at risk. | ICANN began implementation of its Registrar Data Escrow program in 2007. This program is designed to help ensure the stability and security of the Internet's domain name system through escrow of critical gTLD registration data, ensuring that the information associated with registered domain names is never at risk. | ||
In accordance with the Registrar Accreditation Agreement (RAA), this data can be used by ICANN to allow continuity of registrar operations in the event a registrar's RAA is terminated or expires without renewal. Iron Mountain was selected by ICANN as its designated escrow agent for the Registrar Data Escrow program through a competitive RFP bidding process. | In accordance with the Registrar Accreditation Agreement (RAA), this data can be used by ICANN to allow continuity of registrar operations in the event a registrar's RAA is terminated or expires without renewal. Iron Mountain was selected by ICANN as its designated escrow agent for the Registrar Data Escrow program through a competitive RFP bidding process. | ||
Through their participation in the Registry Data Escrow program, registrars can assure their customers that their domain name registration information is safe, and will be accessible by ICANN in the unlikely event that the registrar's operations are disrupted. There is no additional cost to registrars who escrow their registration data with Iron Mountain, as ICANN's selected escrow agent. Registrars who elect to use a third-party provider must do so at their own expense. | Through their participation in the Registry Data Escrow program, registrars can assure their customers that their domain name registration information is safe, and will be accessible by ICANN in the unlikely event that the registrar's operations are disrupted. There is no additional cost to registrars who escrow their registration data with Iron Mountain, as ICANN's selected escrow agent. Registrars who elect to use a third-party provider must do so at their own expense.<ref>[http://www.ironmountain.com/Knowledge-Center/Reference-Library/View-by-Document-Type/Data-Sheets-Brochures/R/Registrar-Data-Escrow-Data-Sheet.aspx Registrar Data Escrow Service, ironmountain.com]</ref> | ||
[http://www.ironmountain.com/Knowledge-Center/Reference-Library/View-by-Document-Type/Data-Sheets-Brochures/R/Registrar-Data-Escrow-Data-Sheet.aspx | |||
===Data Escrow and the new gTLDs=== | ===Data Escrow and the new gTLDs=== | ||
As the new generic Top-Level Domains (gTLDs) become a reality, ICANN is carefully preparing applicants for their new role as Registry Operators. | As the new generic Top-Level Domains (gTLDs) become a reality, ICANN is carefully preparing applicants for their new role as Registry Operators. | ||
One of the requirements of operating a new gTLD is to engage an independent entity to act as a data escrow agent. This neutral, trusted third party (such as Iron Mountain) will provision your data escrow services as specified by the Registry Agreement. | One of the requirements of operating a new gTLD is to engage an independent entity to act as a data escrow agent. This neutral, trusted third party (such as Iron Mountain) will provision your data escrow services as specified by the Registry Agreement. Data escrow is one of the five critical registry functions and is a requirement for all new gTLDs. It is covered in question #38 of the application, and details are given in Specification 2 of the Registry Agreement. New gTLD applicants need to articulate that a plan is in place to escrow gTLD data. Iron Mountain offers the most comprehensive and trusted Domain Name Registry Data Escrow Services in the industry, making it as simple as possible to comply with ICANN’s escrow requirements.<ref>[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]</ref> | ||
Data escrow is one of the five critical registry functions and is a requirement for all new gTLDs. It is covered in question #38 of the application, and details are given in Specification 2 of the Registry Agreement. New gTLD applicants need to articulate that a plan is in place to escrow gTLD data. | |||
Iron Mountain offers the most comprehensive and trusted Domain Name Registry Data Escrow Services in the industry, making it as simple as possible to comply with ICANN’s escrow requirements. | |||
[http://www.ironmountain.com/Knowledge-Center/Reference-Library/View-by-Document-Type/White-Papers-Briefs/D/Data-Escrow-for-the-New-gTLDs.aspx | |||
==Awards & Recognition== | ==Awards & Recognition== | ||