Iron Mountain: Difference between revisions

← Older edit Newer edit →

VisualWikitext

Revision as of 16:30, 31 October 2013 view source Dmmkdoyle (talk \| contribs) 132 edits No edit summary ← Older edit		Revision as of 16:31, 31 October 2013 view source Dmmkdoyle (talk \| contribs) 132 edits No edit summary Newer edit →
Line 57:		Line 57:

	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.		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 has developed the Information Guide “Data Escrow for the New gTLDs: Safeguarding Your Future.” Download it for more information.[4]		Iron Mountain has developed the Information Guide “Data Escrow for the New gTLDs: Safeguarding Your Future.” Download it for more information.[4]